2017-07-07 16:58:16 -04:00
..
2017-06-28 11:12:45 -04:00
2017-05-13 10:24:58 +02:00
2017-05-04 22:46:13 -04:00
2017-07-07 16:58:16 -04:00
2016-08-09 20:31:53 -04:00
2017-05-13 10:24:58 +02:00
2017-06-23 22:12:45 -04:00
2017-06-28 11:12:45 -04:00
2017-07-07 16:58:16 -04:00
2017-05-20 21:43:00 -07:00
2017-04-21 18:12:54 -04:00
2017-05-13 16:22:51 +02:00

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.