Closed oskarth closed 4 years ago
Rough initial draft https://notes.status.im/waku-libp2p#
Brief update: nim-waku code here with experimental v2 https://github.com/status-im/nim-waku/
Quite a bit to go. Will split up above issues into separate GHIs
While we could do more work here, I'd consider this done for now https://discuss.status.im/t/waku-version-2-pitch/1776
Waku libp2p routing feasibility study
Background
Currently the the Status app is using Waku (and/or Whisper) in the app. This is running on devp2p with gossip/flooding routing based on Whisper.
Problem
Current routing scales poorly between full nodes due to excessive amplification factors (every node receives every message, often more than once)
Running on devp2p as opposed to libp2p limits us in several ways:
Lack of incentive to route, leading to unsustainablity (modulo altruism / higher-order incentives) and centralization (Status cluster)
Solution
We want a routing mechanism that is decentralized, incentivized and scales.
The goal of this specific issue is to understand options and limitations for moving Waku to libp2p. We do this by studying the feasibility of two promising candidates:
Optionally, a pub/sub interface on top of Kademlia to have more harmony with existing app requirements.
We want to understand and isolate properties and constraints such as:
Acceptance criteria
Notes
Related reading: