6afee8f117
|
||
|---|---|---|
| .. | ||
| test_data | ||
| README.md | ||
| byzantine_test.go | ||
| common.go | ||
| common_test.go | ||
| height_vote_set.go | ||
| height_vote_set_test.go | ||
| log.go | ||
| mempool_test.go | ||
| reactor.go | ||
| reactor_test.go | ||
| replay.go | ||
| replay_file.go | ||
| replay_test.go | ||
| state.go | ||
| state_test.go | ||
| ticker.go | ||
| version.go | ||
| wal.go | ||
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.