mirror of https://github.com/fluencelabs/tendermint synced 2025-05-19 01:51:19 +00:00

History

Fixes:
```
--- FAIL: TestHandshakeReplaySome (12.40s)
        replay_test.go:332: waited too long for tendermint to produce 6 blocks
```

2017-12-11 16:22:27 -06:00

types

int64 height

2017-12-01 19:04:53 -06:00

byzantine_test.go

int64 height

2017-12-01 19:04:53 -06:00

common_test.go

update for new abci int types

2017-12-02 01:47:55 -05:00

mempool_test.go

update for new abci int types

2017-12-02 01:47:55 -05:00

reactor_test.go

update for new abci int types

2017-12-02 01:47:55 -05:00

reactor.go

int64 height

2017-12-01 19:04:53 -06:00

README.md

some comments

2016-08-09 20:31:53 -04:00

replay_file.go

service#Start, service#Stop signatures were changed

2017-11-29 10:38:58 -06:00

replay_test.go

fixes after my own review

2017-12-06 18:28:14 -06:00

replay.go

Merge pull request #918 from tendermint/abci-update

2017-12-03 01:36:59 -05:00

state_test.go

linting: apply errcheck part2

2017-11-27 22:39:11 +00:00

state.go

remove comments for uint64 related to possible underflow [ci skip]

2017-12-01 23:30:08 -06: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_generator.go

wait 5 sec for a block on CircleCI

2017-12-11 16:22:27 -06:00

wal_test.go

fixes after my own review

2017-12-06 18:28:14 -06:00

wal.go

be specific about what type we're encoding

2017-12-07 11:45:50 -06: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.