rfc
rfc copied to clipboard
vacp2p
Modular p2p messaging stack, with a focus on secure messaging.
This issue is part of the Waku ambient discovery roadmap (new roadmap issue to be opened in the research repo; will edit/update this description once the roadmap issue is open)...
Adds API functions to expose filter, store and lightpush protocols via C bindings
# Problem We need to disseminate the initial work on Logos blockchain consensus protocol in a manner that somehow introduces the "framing" that induced it, the progress that has been...
# Problem Within the Logos Consensus model (c.f. #509), a "pluggable" behavior for node reputation may be specified. Such a "Reputation RFC" needs to be abstracted, reviewed, and written. #...
# Problem In the waku-rln-relay spec, circuit parameters are not clearly specified. This will affect the power-of-tau and circuit-dependent ceremonies hence the generated prover/verifier keys. # Acceptance Criteria - [...
## Problem In RLN using Semaphore and SSS, the number of signals per registered user per epoch is limited and guaranteed to be one (otherwise the user gets slashed) however,...
# Problem There might be ways to link a message to a specific application, or worse user, because of the way the message is formed. One specific case is for...
# Problem Currently in spec it says: > Waku is a privacy-preserving peer-to-peer messaging protocol for resource restricted devices. as well as: > Resource restricted.These applications often run in constrained...
The `get_waku_v2_debug_v1_info` json RPC method returns an object with a unique field: - `listenStr`: Address that the node is listening for (e.g. `/ip4/127.0.0.1/tcp/60000/p2p/16Uiu2HAkyzsXzENw5XBDYEQQAeQTCYjBJpMLgBmEXuwbtcrgxBJ4`) It would be great if it could...
# Problem There are some inconsistencies between the RFC and the main implementation in [nwaku](https://github.com/status-im/nwaku/tree/master/waku/v2/node/jsonrpc). - The [KeyPair](https://rfc.vac.dev/spec/16/#keypair) fields are called in `privateKey` and `publicKey` in the RFC, but `seckey`...
