certusone
/
tendermint
mirror of https://github.com/certusone/tendermint.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tendermint/consensus
History
Ethan Buchman d34286c421 minor fixes - tests pass 2018-02-03 03:54:49 -05:00
..
test_data rebase fix 2017-12-28 20:49:02 +00:00
types StopPeerForError in blockchain and consensus 2018-01-21 13:32:04 -05:00
README.md some comments 2016-08-09 20:31:53 -04:00
byzantine_test.go minor fixes - tests pass 2018-02-03 03:54:49 -05:00
common_test.go consensus: fix SetLogger in tests 2018-01-24 23:34:57 -05:00
mempool_test.go update for sdk2 libs. need to fix kv test 2018-02-03 03:35:02 -05:00
reactor.go StopPeerForError in blockchain and consensus 2018-01-21 13:32:04 -05:00
reactor_test.go consensus: print go routines in failed test 2018-01-25 01:22:53 -05:00
replay.go update for sdk2 libs. need to fix kv test 2018-02-03 03:35:02 -05:00
replay_file.go it compiles 2018-02-03 03:52:17 -05:00
replay_test.go fix race 2018-01-19 01:36:52 -05:00
state.go consensus: minor cosmetic 2018-01-23 21:41:13 -05:00
state_test.go consensus: rename test funcs 2018-01-19 00:59:09 -05:00
ticker.go consensus: Fix typo on ticker.go documentation 2017-12-09 13:14:53 +01:00
version.go all: no more anonymous imports 2017-10-04 16:40:45 -04:00
wal.go p2p: peer.Key -> peer.ID 2018-01-01 22:39:05 -05:00
wal_fuzz.go add gofuzz test for consensus wal 2017-12-15 11:56:24 -06:00
wal_generator.go fixes from review 2017-12-28 23:15:54 -05:00
wal_test.go consensus: rename test funcs 2018-01-19 00:59:09 -05:00

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.