## 2023-7-3 TODOs: 1. Ryan: Implement CorrectChord feature 2. Magine: Fix headless browser test failing https://github.com/RingsNetwork/rings-node/issues/445 Agenda: * Browser Client initial with config * Allow user sign locally without builder, and define it in Config * Browser Client should only have two API: - new - request ## 2023-6-27 TODOs: 1. Ryan: Implement CorrectChord feature 2. Ryan: Upgrade rings-node in frontend 3. Magine: Fix headless browser test failing https://github.com/RingsNetwork/rings-node/issues/445 4. Magine: Fix API signature bug https://github.com/RingsNetwork/rings-node/issues/447 5. Magine: WASM exportable Result https://github.com/RingsNetwork/rings-node/issues/446 Agenda: * Initial Concept of the Resolve Protocol (working title) - A node can commit to its stable or non-malicious behavior. - The commitment can be challenged and verified. A challenge can result in external slashing/reward. - In a set of committed nodes, which are chained as a committed path, a node can be challenged by its message sender. - The committed path can function without knowledge of the origin and destination (Onion Router). * UDP/TCP backend * Standardize the Display and Serialize of Did as a string starts with "0x". ## 2023-6-19 TODOs: 1. Ryan: Implement json rpc server in browser. 2. Ryan: Fix handshake problem of Transport between native and browser. 3. Magine: Tidy and refactor SessionManager, also add tests and docs. 4. Magine: Find the configuration method of ChromeDriver. Try to fix the unstable testing in ChromeDriver. Agenda: * WASM first - Improve the interaction with frontend by minimizing the use of ambiguous JSON strings and error types such as "anyhow". - Prevent separate implementation for WASM and native in node. - All tests in the core should also run and pass in WASM. * WASM headless browser testing is unstable. - Need to find the configuration method of ChromeDriver * WebRTC Transport may have issues. - In certain environments, developers cannot connect to node exposed on the public network through browser node. * The minimized user-friendly version - The native node should function as a reverse proxy, with the source data originating from RingsNetwork. - The browser node should be an extension that can intercept requests for RingsNetwork.