History

Ethan Buchman d71aed309f some minor changes		2017-10-30 22:52:03 -04:00
..
test_data	fixes per Bucky's review	2017-10-24 12:14:21 +04:00
types	do not send whole round state via eventHub	2017-10-30 00:32:23 -05:00
README.md	some comments	2016-08-09 20:31:53 -04:00
byzantine_test.go	new pubsub package	2017-10-30 00:32:22 -05:00
common_test.go	new pubsub package	2017-10-30 00:32:22 -05:00
mempool_test.go	new pubsub package	2017-10-30 00:32:22 -05:00
reactor.go	some minor changes	2017-10-30 22:52:03 -04:00
reactor_test.go	new pubsub package	2017-10-30 00:32:22 -05:00
replay.go	new pubsub package	2017-10-30 00:32:22 -05:00
replay_file.go	fixes from my own review	2017-10-30 00:32:23 -05:00
replay_test.go	new pubsub package	2017-10-30 00:32:22 -05:00
state.go	fixes from Bucky's and Emmanuel's reviews	2017-10-30 11:12:01 -05:00
state_test.go	new pubsub package	2017-10-30 00:32:22 -05:00
ticker.go	consensus: more comments	2017-07-20 00:59:28 -04:00
version.go	all: no more anonymous imports	2017-10-04 16:40:45 -04:00
wal.go	fixes from Bucky's and Emmanuel's reviews	2017-10-30 11:12:01 -05:00
wal_test.go	fixes from review	2017-10-25 21:54:56 -04: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.