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		3 years ago
..
v0	modify Reactor priorities (#5826) (#5830)	3 years ago
v1	blockchain/v1: omit incoming message bytes from log	4 years ago
v2	modify Reactor priorities (#5826) (#5830)	3 years ago
msgs.go	proto: change type + a cleanup (#5107)	4 years ago
msgs_test.go	backport block size fixes (#5492)	4 years ago