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.
 
 
 
 
 
 
Anton Kaliaev bb9aa85d22
copy events and pubsub packages from tmlibs
7 years ago
..
test_data update consensus/test_data/many_blocks.cswal 7 years ago
types Add more comments for Valid* 7 years ago
README.md some comments 8 years ago
byzantine_test.go WIP consensus 7 years ago
common_test.go use channels to send votes, ... from consensus state to reactor 7 years ago
mempool_test.go Merge branch 'develop' into jae/aminoify 7 years ago
reactor.go copy events and pubsub packages from tmlibs 7 years ago
reactor_test.go fix tests 7 years ago
replay.go Comment tweaks 7 years ago
replay_file.go use MarshalJSONIndent for init files. closes #1506 7 years ago
replay_test.go consensus: only fsync wal after internal msgs 7 years ago
state.go copy events and pubsub packages from tmlibs 7 years ago
state_test.go copy events and pubsub packages from tmlibs 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 update comments 7 years ago
wal_fuzz.go add gofuzz test for consensus wal 7 years ago
wal_generator.go consensus: only fsync wal after internal msgs 7 years ago
wal_test.go remove wal_light setting 7 years ago
wire.go WIP consensus 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.