Hanno Cornelius

16/WAKU2-RPC: Inconsistencies and inaccuracies in RFC spec

1

# 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`...

12/WAKU2-FILTER: Production readiness

2

## Background The [12/WAKU2-FILTER](https://rfc.vac.dev/spec/12/) protocol and specification have a number of outstanding questions that need to be addressed to reach production readiness. 1. We deal badly with failed nodes (on...

27/WAKU2-PEERS: Peer selection recommendations

1

Currently [27/WAKU2-PEERS](https://rfc.vac.dev/spec/27/) recommends a minimal method for peer storage and management in Waku v2, including keeping track of the libp2p protocols supported by each peer. It does not, however, recommend...

## Background In practice, deploying a node running [13/WAKU2-STORE](https://rfc.vac.dev/spec/13/) poses a number of production challenges. Although these could be addressed ad-hoc by different client implementations, a minimal feature set should...

# Problem `libp2p` PubSub, FloodSub and GossipSub define a long list of tweakable parameters that control the underlying behaviour of each protocol (for example, [here](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.0.md#parameters) and [here](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md)). Although most client...

# Problem The Admin API provides a `get_waku_v2_admin_v1_peers` method to query the peers currently registered on a Waku v2 node. [This method currently takes no parameters](https://rfc.vac.dev/spec/16/#get_waku_v2_admin_v1_peers). It will be useful...

[`15/WAKU-BRIDGE`](https://rfc.vac.dev/spec/15/) can be significantly improved and clarified. Some suggestions: - [ ] Add a background that properly explains the rationale of the `bridge` and where it fits into the Waku...

Improve Waku resilience against flooding attacks

12

## Background During the recent Status client offsite, Waku's vulnerability to flooding-type DoS attacks were highlighted to be of particular concern for Status Communities. Since, in general, a pubsub topic...

Milestone: launch Waku operator trial amongst core contributors

2

## Problem We want to push for operators to run and maintain their own Waku v2 nodes, preferably contributing to the default Waku v2 network as described by the default...

Waku v2 benchmarking: load testing

2

## Background The [original plan](https://vac.dev/waku-v2-plan) for Waku v2 suggested scalability and performance at a level necessary for a large, p2p, generalised messaging network. Given that Waku v2 is aimed at...