zolfa
/
tendermint
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 221 Wiki Activity
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.
235 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: a75a2c6f00
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'a75a2c6f00'
${ noResults }
tendermint/spec/p2p/messages
M. J. Fromberger e92aa56a75
Clean up lint failures for Markdown files (#367) 		3 years ago
..
README.md spec: remove reactor section (#242) 4 years ago
block-sync.md fix message type for block-sync (#298) 4 years ago
consensus.md rename HasVote to ReceivedVote (#289) 4 years ago
evidence.md spec: remove reactor section (#242) 4 years ago
mempool.md spec: remove reactor section (#242) 4 years ago
pex.md pex: update pex messages (#352) 3 years ago
state-sync.md Clean up lint failures for Markdown files (#367) 3 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