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

Topic added to Status handshake

Browse Source
This commit is contained in:
Oskar Thoren 2020-01-22 11:57:24 +08:00
parent 86e053e34c
commit 72a60e1737
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
waku/waku.md
View File

@ -96,11 +96,14 @@ status = "["
version pow-requirement version pow-requirement
[ bloom-filter ] [ light-node ] [ bloom-filter ] [ light-node ]
[ confirmations-enabled ] [ rate-limits ] [ confirmations-enabled ] [ rate-limits ]
[ topic-node-enabled topic-interest ]
"]" "]"
; version is "an integer (as specified in RLP)" ; version is "an integer (as specified in RLP)"
version = DIGIT version = DIGIT
topic-node-enabled = BIT
confirmations-enabled = BIT confirmations-enabled = BIT
; pow is "a single floating point value of PoW. ; pow is "a single floating point value of PoW.
@ -198,8 +201,6 @@ A Waku node MUST await the Status message from a peer before engaging in other W
When a node does not receive the Status message from a peer, before a configurable timeout, it SHOULD disconnect from that peer. When a node does not receive the Status message from a peer, before a configurable timeout, it SHOULD disconnect from that peer.
Upon retrieval of the Status message, the node SHOULD validate the message Upon retrieval of the Status message, the node SHOULD validate the message
content and decide whether it is compatible with the Waku version and mode
its peer is advertising. The handshake is completed when the node has sent,
received and validated the Status message. Note that its peer might not be in received and validated the Status message. Note that its peer might not be in
the same state. the same state.
@ -210,6 +211,8 @@ Status messages received after the handshake is completed MUST also be ignored.
The fields `bloom-filter`, `light-node`, `confirmations-enabled` and `rate-limits` are OPTIONAL. However if an optional field is specified, all subsequent fields MUST be specified in order to be unambiguous. The fields `bloom-filter`, `light-node`, `confirmations-enabled` and `rate-limits` are OPTIONAL. However if an optional field is specified, all subsequent fields MUST be specified in order to be unambiguous.
The tuple `[ topic-node-enabled topic-interest ]` is also OPTIONAL. If `topics-node-enabled` is set to 1, `topic-interest` setting takes precedence over `bloom-filter`. By default, `topic-node-enabled` MUST be 0.
**Messages** **Messages**
This packet is used for sending the standard Waku envelopes. This packet is used for sending the standard Waku envelopes.
@ -510,6 +513,7 @@ Known static nodes MAY also be used.
Features considered for waku/1: Features considered for waku/1:
- Include topic-interest in Status handshake
- Upgradability policy - Upgradability policy
- `topic-interest` packet code - `topic-interest` packet code