zolfa/tendermint - tendermint - Gitea: Git with a cup of tea

bft blockchain consensus consistency cryptocurrency cryptography db distributed-systems go

History

Anton Kaliaev b1328db07f modify Reactor priorities (#5826 ) (#5830 ) blockchain/vX reactor priority was decreased because during the normal operation (i.e. when the node is not fast syncing) blockchain priority can't be the same as consensus reactor priority. Otherwise, it's theoretically possible to slow down consensus by constantly requesting blocks from the node. NOTE: ideally blockchain/vX reactor priority would be dynamic. e.g. when the node is fast syncing, the priority is 10 (max), but when it's done fast syncing - the priority gets decreased to 5 (only to serve blocks for other nodes). But it's not possible now, therefore I decided to focus on the normal operation (priority = 5). evidence and consensus critical messages are more important than the mempool ones, hence priorities are bumped by 1 (from 5 to 6). statesync reactor priority was changed from 1 to 5 to be the same as blockchain/vX priority. Refs https://github.com/tendermint/tendermint/issues/5816		4 years ago
..
mocks	rpc/client: take context as first param (#5347)	4 years ago
chunks.go	libs: wrap mutexes for build flag with godeadlock (#5126)	4 years ago
chunks_test.go	add state sync reactor (#4705)	5 years ago
messages.go	test: protobuf vectors for reactors (#5221)	4 years ago
messages_test.go	test: protobuf vectors for reactors (#5221)	4 years ago
reactor.go	modify Reactor priorities (#5826) (#5830)	4 years ago
reactor_test.go	lint: errcheck (#5091)	4 years ago
snapshots.go	rpc/client: take context as first param (#5347)	4 years ago
snapshots_test.go	rpc/client: take context as first param (#5347)	4 years ago
stateprovider.go	statesync: check all necessary heights when adding snapshot to pool (#5516) (#5518)	4 years ago
syncer.go	config: add state sync discovery_time setting (#5399)	4 years ago
syncer_test.go	rpc/client: take context as first param (#5347)	4 years ago