mirror of
https://github.com/vacp2p/research.logos.co.git
synced 2026-04-03 03:01:03 -04:00
Update _posts/2020-02-10-waku-current-state.md
Co-Authored-By: Dean Eigenmann <dean.eigenmann@icloud.com>
This commit is contained in:
@@ -60,7 +60,7 @@ This is our current understanding of how many users a network running the Waku p
|
||||
|
||||
As far as we know right now, there is one immediate bottleneck, a very likely bottleneck after that, and a third bottleneck that is still conjecture but not unlikely to appear. These are:
|
||||
|
||||
- Bottleneck 1 - Receive bandwidth for end user clients (aka ‘Fixing Whisper with Waku’)
|
||||
- Immediate bottleneck - Receive bandwidth for end user clients (aka ‘Fixing Whisper with Waku’)
|
||||
- Bottleneck 2 - Nodes and cluster capacity (aka ‘DNS based node discovery’)
|
||||
- Bottleneck 3 - Full node traffic (aka ‘the routing / partition problem’)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user