acid-info
/
vac.dev
mirror of https://github.com/acid-info/vac.dev.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update _posts/2020-02-10-waku-current-state.md 

Co-Authored-By: Dean Eigenmann <dean.eigenmann@icloud.com>
This commit is contained in:
Oskar Thorén 2020-02-13 09:59:08 +08:00 committed by GitHub
parent 35f8559a4a
commit 1f0180fe3f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_posts/2020-02-10-waku-current-state.md
View File

@ -61,7 +61,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:
- Immediate bottleneck - Receive bandwidth for end user clients (aka ‘Fixing Whisper with Waku’)
- Bottleneck 2 - Nodes and cluster capacity (aka ‘DNS based node discovery’)
- Very likely bottleneck - Nodes and cluster capacity (aka ‘DNS based node discovery’)
- Bottleneck 3 - Full node traffic (aka ‘the routing / partition problem’)
We've already seen the first bottleneck being discussed in the initial post. Dean wrote a post on [DNS based discovery](https://vac.dev/dns-based-discovery) which explains how we will address the likely second bottleneck. More on the third one in future posts.