Localized slice
Tendermint through the HotStuff lens: locks, unlocks, and evidence
How to read Tendermint through HotStuff: prevote, precommit, LockedValue, ValidRound, proposer rotation, evidence, and slashing.
A lock is memory, not “forever”
When a validator sees enough prevotes for a value it locks and must not vote for conflicting values without stronger evidence. An absolute lock would kill liveness, so Tendermint uses ValidRound and unlock rules that let the protocol progress without opening the door to two histories.
The same drama in another vocabulary
HotStuff keeps a lockedQC and proposes by extending highQC; Tendermint uses LockedValue, LockedRound, and ValidRound. Both negotiate between safety memory and the need for progress, and both must carry evidence when the round or view changes.
- prevote and precommit map to votes and certificates.
- ValidRound plays the role of the evidence that justifies a safe proposal.
Evidence and slashing are part of the protocol too
Proposer rotation lets the round advance when one proposer fails. If a validator signs two incompatible values, that evidence is propagated, stored for a valid window, and punished. The system does not merely assume honesty: it incentivizes it without creating new attack vectors.
References
[1]
Buchman, Kwon and Milosevic, The latest gossip on BFT consensus (2018)Tendermint specification with LockedValue, LockedRound, and ValidRound.
[2]
Yin et al., HotStuff: BFT Consensus in the Lens of Blockchain (2019)lockedQC and highQC as the counterpart of Tendermint locks.
[3]
Kwon, Tendermint: Consensus without Mining (2014)Original paper: propose, prevote, precommit rounds and accountability through evidence.