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.
3429 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: 196f8410ba
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '196f8410ba'
${ noResults }
tendermint/consensus
Jae Kwon 196f8410ba WIP commit; Fix types/results_test 7 years ago
..
test_data update consensus/test_data/many_blocks.cswal 7 years ago
types WIP commit; Fix types/results_test 7 years ago
README.md some comments 8 years ago
byzantine_test.go add a todo 7 years ago
common_test.go WIP commit; Fix types/results_test 7 years ago
mempool_test.go update for sdk2 libs. need to fix kv test 7 years ago
reactor.go add a todo 7 years ago
reactor_test.go rename dummy to kvstore (#1223) 7 years ago
replay.go Add app_state from genesis file in InitChain message 7 years ago
replay_file.go Add app_state from genesis file in InitChain message 7 years ago
replay_test.go Add app_state from genesis file in InitChain message 7 years ago
state.go WIP commit; Fix types/results_test 7 years ago
state_test.go consensus: rename test funcs 7 years ago
ticker.go fixes from Jae's review 7 years ago
version.go all: no more anonymous imports 7 years ago
wal.go p2p: peer.Key -> peer.ID 7 years ago
wal_fuzz.go add gofuzz test for consensus wal 7 years ago
wal_generator.go Add app_state from genesis file in InitChain message 7 years ago
wal_test.go consensus: rename test funcs 7 years ago

README.md

The core consensus algorithm.

  • state.go - The state machine as detailed in the whitepaper
  • reactor.go - A reactor that connects the state machine to the gossip network

Go-routine summary

The reactor runs 2 go-routines for each added peer: gossipDataRoutine and gossipVotesRoutine.

The consensus state runs two persistent go-routines: timeoutRoutine and receiveRoutine. Go-routines are also started to trigger timeouts and to avoid blocking when the internalMsgQueue is really backed up.

Replay/WAL

A write-ahead log is used to record all messages processed by the receiveRoutine, which amounts to all inputs to the consensus state machine: messages from peers, messages from ourselves, and timeouts. They can be played back deterministically at startup or using the replay console.