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.
 
 
 
 
 
 
Ethan Buchman f55135578c state: move methods to funcs 7 years ago
..
test_data update consensus/test_data/many_blocks.cswal 7 years ago
types EvidencePool 7 years ago
README.md some comments 8 years ago
byzantine_test.go int64 height 7 years ago
common_test.go evidence linked with consensus/node. compiles 7 years ago
mempool_test.go excessive logging. update tmlibs for timer fix 7 years ago
reactor.go consensus: remove log stmt. closes #987 7 years ago
reactor_test.go change voting power change, not number of vals 7 years ago
replay.go state: move methods to funcs 7 years ago
replay_file.go evidence linked with consensus/node. compiles 7 years ago
replay_test.go fixes from rebase 7 years ago
state.go state.ApplyBlock takes evpool and calls MarkEvidenceAsCommitted 7 years ago
state_test.go separate block vs state based validation 7 years ago
ticker.go consensus: Fix typo on ticker.go documentation 7 years ago
version.go all: no more anonymous imports 7 years ago
wal.go Updates -> ValidatoSetUpdates 7 years ago
wal_fuzz.go add gofuzz test for consensus wal 7 years ago
wal_generator.go change directory for each call, not only for each test 7 years ago
wal_test.go handle data corruption errors 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.