Franck R.
Franck R.
From the p2p WebRTC exploration, a requirement has [emerged](https://github.com/status-im/js-waku/issues/20#issuecomment-1090973059) to design a protocol that enables two peers to communicate over Waku using their peer id as identifier. In a first...
## Description Peer exchange tl;dr: remote node include alternative peer when sending a `PRUNE` message as part of gossip sub mesh maintenance. While it does not make sense for js-waku...
## Problem The Waku Filter protocol allow light clients to save bandwidth but only receiving messages of the target content topic, and not relaying/forwarding messages. See https://rfc.vac.dev/spec/12/ for details. ##...
## Problem 1. We use `rollup` for production bundling but use `webpack` to bundle for `karma` 2. We use `tsc` for code transpilation, other tools such as `parcel` and `vite`...
## Problem js-waku library is meant for dApp, meaning web apps. Hence browser support is primordial. Most of the testing is currently done via NodeJS, which is not ideal especially...
Waku can be a great communication layer solution for state channels protocols. We should provide DappConnect guides and possible white label solutions to demonstrate how to use Waku and a...
# Problem When a dApp using js-waku is offline, relay messages are not received. Same for filter messages. # Solution To ensure that no message were missed, a store query...
See https://github.com/status-im/infra-waku-connect/issues/1 We are setting up some nodes to enable Waku Connect (ie, js-waku) users to test out the js-waku library without having to deploy their own nodes. Once they...
# Problem Keep alive implemented in js-waku Waku Relay: See https://github.com/status-im/js-waku/pull/243 It is not documented # DoD - [ ] Check it still needed (see #751) - [ ] Open...
## Problem js-waku targets the browser. NodeJS user should use nim-waku and JSON RPC API. There are a number of issues when using js-waku in the browser: - Node/browser switches...