zolfa
/
tendermint
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 221 Wiki Activity
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.
1340 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: 73502fab0d
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '73502fab0d'
${ noResults }
tendermint/consensus
Ethan Buchman 8df32cd540 test: increase proposal timeout 8 years ago
..
test_data MakePartSet takes partSize from config. fix replay test 8 years ago
README.md some comments 9 years ago
byzantine_test.go test: increase proposal timeout 8 years ago
common.go consensus: test validator set change 8 years ago
common_test.go test: increase proposal timeout 8 years ago
height_vote_set.go Fix BFT issue where VoteSetMaj23Message wasn't being sent where prs.Round == blockStore.Round() 8 years ago
height_vote_set_test.go Fixing issues from review in #229 8 years ago
log.go Make consensus logs use default log handler 9 years ago
mempool_test.go fixes 8 years ago
reactor.go remove privValIndex; Stale->AppHashIsStale 8 years ago
reactor_test.go test: increase proposal timeout 8 years ago
replay.go Fix Merge pull request #319 8 years ago
replay_test.go Fix Merge pull request #319 8 years ago
state.go update grpc broadcast tx 8 years ago
state_test.go MakePartSet takes partSize from config. fix replay test 8 years ago
version.go version bump and release branch 9 years ago
wal.go Use new Group semantics 8 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.