You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Callum Waters
255942e8c7
|
4 years ago | |
|---|---|---|
| .. | ||
| README.md | 4 years ago | |
| block-sync.md | 4 years ago | |
| consensus.md | 4 years ago | |
| evidence.md | 4 years ago | |
| mempool.md | 4 years ago | |
| pex.md | 4 years ago | |
| state-sync.md | 4 years ago | |
README.md
| order | parent |
|---|---|
| 1 | [{title Messages} {order 1}] |
Messages
An implementation of the spec consists of many components. While many parts of these components are implementation specific, the p2p messages are not. In this section we will be covering all the p2p messages of components.
There are two parts to the P2P messages, the message and the channel. The channel is message specific and messages are specific to components of Tendermint. When a node connect to a peer it will tell the other node which channels are available. This notifies the peer what services the connecting node offers. You can read more on channels in connection.md