The design uses self-locating boundaries rather than fixed epoch-ending heights. Each block carries source and target epoch information, while a snapshot block determines the next committee. Votes for a transition attempt go to incoming validators, letting each honest member independently form the cross-epoch quorum certificate. That full fanout removes dependence on a single incoming collector and allows consecutive committees to be completely disjoint, although communication rises at the boundary to old-committee size multiplied by new-committee size.
Plasma modifies Fast-HotStuff with epoch-aware quorum-certificate ordering, epoch locking and truncated finality above the snapshot. Those rules aim to prevent an older committee from pulling a newer epoch backward or allowing conflicting first blocks to finalize. The safety argument is mechanized in Lean 4, while the liveness proof still uses a synchronizer assumption the team expects to remove. Torch is presented as a formally reasoned consensus construction rather than a routine validator upgrade, adding another layer to Plasma’s mainnet infrastructure.
The mechanism is not fully deployed. Plasma says its chain uses fixed-length epochs with a snapshot-based handoff window, while the dynamic protocol-placed boundaries described in Torch are forthcoming. The work is undergoing peer review, with a whitepaper and mechanized proofs planned later this year. Torch’s significance lies in its proposed solution to dynamic validator rotation rather than production adoption, an area tied to broader concerns around validator resilience in proof-of-stake networks today.
