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.
53 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: eb3a287594
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'eb3a287594'
${ noResults }
tendermint/peer
Jae Kwon eb3a287594 Merge branch 'master' of https://github.com/tendermint/tendermint 11 years ago
..
README.md Merge branch 'master' of https://github.com/tendermint/tendermint 11 years ago
addrbook.go . 11 years ago
client.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
connection.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
connection_test.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
knownaddress.go working draft of peer 11 years ago
listener.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
log.go working draft of peer 11 years ago
msg.go . 11 years ago
netaddress.go working draft of peer 11 years ago
peer.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
server.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
set.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
upnp.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
upnp_test.go Channels do not have integrated filters. They're only for multiplexing. 11 years ago
util.go stripped addrmanager from btcd 11 years ago

README.md

Channels

Each peer connection is multiplexed into channels.

Default channel

The default channel is used to communicate state changes, pings, peer exchange, and other automatic internal messages that all P2P protocols would want implemented.

Channel ""
Messages
  • PingMsg/PongMsg
  • PeerExchangeMsg
  • RefreshFilterMsg

Block channel

The block channel is used to propagate block or header information to new peers or peers catching up with the blockchain.

Channel "block"
Messages
  • RequestMsg
  • BlockMsg
  • HeaderMsg
Notes Nodes should only advertise having a header or block at height 'h' if it also has all the headers or blocks less than 'h'. Thus for each peer we need only keep track of two integers -- one for the most recent header height 'h_h' and one for the most recent block height 'h_b', where 'h_b' <= 'h_h'.

Mempool channel

The mempool channel is used for broadcasting new transactions that haven't yet entered the blockchain. It uses a lossy bloom filter on either end, but with sufficient fanout and filter nonce updates every new block, all transactions will eventually reach every node.

Channel "mempool"
Messages
  • MempoolTxMsg
Notes Instead of keeping a perfect inventory of what peers have, we use a lossy filter.
Bloom filter (n:10k, p:0.02 -> k:6, m:10KB)
Each peer's filter has a random nonce that scrambles the message hashes.
The filter & nonce refreshes every new block.

Consensus channel

The consensus channel broadcasts all information used in the rounds of the Tendermint consensus mechanism.

Channel "consensus"
Messages
  • ProposalMsg
  • VoteMsg
  • NewBlockMsg
Notes How do optimize/balance propagation speed & bandwidth utilization?

Resources