-
Notifications
You must be signed in to change notification settings - Fork 15
Waku 0: Handshake #37
Comments
For the reference, here is the implementation: https://github.com/status-im/whisper/blob/master/whisperv6/peer.go#L93 |
Is this enough covered now here: https://github.com/vacp2p/specs/blob/master/waku.md#packet-usage ? Or do we need a better description? Any additional field such as the |
I don't see any explanation what should be sent in a handshake in https://github.com/vacp2p/specs/blob/master/waku.md#packet-usage. There is this:
but status code is a handshake from what I understand from the implementation. We need to describe that a handshake is a status packet followed by protocol version, PoW, bloom, mode (currently true/false but I think we need to send here either a light node or waku mode or whatever else; it might be a bit map). Regarding the message confirmation, here is an issue: #30. Let's figure out that one first and if needed we can extend the handshake definition. |
yeah @kdeme I'd like to see a more explicit explanation. As mentioned by @adambabik |
@kdeme whats the state of this? |
I've added this under the explanation of the Status message, see: https://github.com/vacp2p/specs/blob/master/waku.md#packet-usage I'll close, please reopen if it is not sufficient. |
Problem
There is currently no part of the specification that clearly outlines the handshake and how it occurs.
Acceptance criteria
The text was updated successfully, but these errors were encountered: