vacp2p/rfc
1
0
Fork 0
mirror of https://github.com/vacp2p/rfc.git synced 2025-02-18 18:07:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update waku-1.md

Browse Source
This commit is contained in:
Dean Eigenmann 2020-06-11 14:41:33 +02:00 committed by GitHub
parent 7a981510a0
commit 4e50db56db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
specs/waku/waku-1.md
View File

@ -427,14 +427,7 @@ Light nodes are identified by the `light_node` value in the Status packet.
Nodes MAY implement accounting, keeping track of resource usage. It is heavily inspired by Swarm's [SWAP protocol](https://www.bokconsulting.com.au/wp-content/uploads/2016/09/tron-fischer-sw3.pdf), and works by doing pairwise accounting for resources.
Each node keeps track of resource usage with all other nodes. Whenever an envelope is received from a node that is expected (fits bloom filter or topic interest, is legal, etc) this is tracked.
Every epoch (say, every minute or every time an event happens) statistics SHOULD be aggregated and saved by the client:
| peer | sent | received |
|-------|------|----------|
| peer1 | 0 | 123 |
| peer2 | 10 | 40 |
Each node SHOULD keep track of resource usage of all other nodes. Whenever an envelope is received from a node that is expected (fits bloom filter or topic interest, is legal, etc) or sent, it SHOULD be tracked.
In later versions this will be amended by nodes communication thresholds, settlements and disconnect logic.