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

chore: minor change px proto as per linter (#570)

Browse Source
This commit is contained in:
Alvaro Revuelta 2023-02-08 08:26:24 +01:00 committed by GitHub
parent 23025b1593
commit ab661c8276
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/docs/rfcs/34/README.md
View File

@ -65,15 +65,15 @@ While any node could technically act as a requester, using the peer exchange pro
syntax = "proto3"; syntax = "proto3";
message PeerInfo { message PeerInfo {
bytes ENR = 1; bytes enr = 1;
} }
message PeerExchangeQuery { message PeerExchangeQuery {
int numPeers; // number of peers requested uint64 num_peers = 1;
} }
message PeerExchangeResponse { message PeerExchangeResponse {
repeated PeerInfo peerInfos = 1; repeated PeerInfo peer_infos = 1;
} }
message PeerExchangeRPC { message PeerExchangeRPC {
@ -83,10 +83,10 @@ message PeerExchangeRPC {
``` ```
The `ENR` field contains a Waku ENR as specified in [31/WAKU2-ENR](/spec/31/). The `enr` field contains a Waku ENR as specified in [31/WAKU2-ENR](/spec/31/).
Requesters send a `PeerExchangeQuery` to a peer. Requesters send a `PeerExchangeQuery` to a peer.
Responders SHOULD include a maximum of `numPeers` `PeerInfo` instances into a response. Responders SHOULD include a maximum of `num_peers` `PeerInfo` instances into a response.
Responders send a `PeerExchangeResponse` to requesters containing a list of `PeerInfo` instances, which in turn hold an ENR. Responders send a `PeerExchangeResponse` to requesters containing a list of `PeerInfo` instances, which in turn hold an ENR.
# Implementation Suggestions # Implementation Suggestions