Files
consensus/engine/chain
zeekayandHanzo Dev 0c8e4f1163 consensus: comments state the contract, not the history behind it
The vote topology, the cert path and the bootstrap accept rule each explained
themselves by describing a failure they had already been changed to prevent,
including one written out in enough detail to be a recipe. What a maintainer
needs is the property being held.

Finality does not depend on any one node's inbound Chits, because a vote that
reaches only the proposer leaves the round resting on what that node hears.
Arrival is not agreement, so a follower Accepts on an α-of-K witness and not
before. A position is recorded before the path that reads it opens, or there is
a window where the path is open and the position absent. The ledger height alone
cannot decide what is already synced.

Behaviour is unchanged; every line here is a comment.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-26 13:18:52 -07:00
..