status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update specs/networking/rpc-interface.md 

Co-Authored-By: mslipper <me@matthewslipper.com>
This commit is contained in:
Raúl Kripalani 2019-03-13 21:57:29 -07:00 committed by GitHub
parent 22e6212e6f
commit 863f85c45a
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
specs/networking/rpc-interface.md
View File

@ -30,7 +30,7 @@ All referenced data structures can be found in the [0-beacon-chain](https://gith
## `libp2p` Protocol Names ## `libp2p` Protocol Names
A "Protocol Name" in `libp2p` parlance refers to a human-readable identifier `libp2p` uses in order to identify sub-protocols and stream messages of different types over the same connection. A client's supported protocol paths are negotiated by the `libp2p` stack at connection time; as such they are not part of individual message bodies. A "Protocol ID" in `libp2p` parlance refers to a human-readable identifier `libp2p` uses in order to identify sub-protocols and stream messages of different types over the same connection. Peers exchange supported protocol IDs via the `Identify` protocol upon connection. When opening a new stream, peers pin a particular protocol ID to it, and the stream remains contextualised thereafter. Since messages are sent inside a stream, they do not need to bear the protocol ID.
## RPC-Over-`libp2p` ## RPC-Over-`libp2p`