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.
2457 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: 7b8ffc9981
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '7b8ffc9981'
${ noResults }
tendermint/consensus
Anton Kaliaev 7b8ffc9981
add checksum and msg size to TimedWALMessage 		7 years ago
..
test_data add checksum and msg size to TimedWALMessage 7 years ago
types extract some of the consensus types into ./types 7 years ago
README.md some comments 9 years ago
byzantine_test.go all: no more anonymous imports 7 years ago
common.go fixes from review 8 years ago
common_test.go update cswal test 7 years ago
mempool_test.go all: no more anonymous imports 7 years ago
reactor.go extract some of the consensus types into ./types 7 years ago
reactor_test.go PrivValidatorFS is like old PrivValidator, for now 7 years ago
replay.go add checksum and msg size to TimedWALMessage 7 years ago
replay_file.go node: NewNode takes DBProvider and GenDocProvider 7 years ago
replay_test.go add checksum and msg size to TimedWALMessage 7 years ago
state.go [state] expose ChainID and Params 7 years ago
state_test.go [state] expose ChainID and Params 7 years ago
ticker.go consensus: more comments 8 years ago
version.go all: no more anonymous imports 7 years ago
wal.go add checksum and msg size to TimedWALMessage 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.