Files
consensus/engine
zeekayandHanzo Dev 97c8d74e76 summary: the round is generic over the summary type, like the serving half is
A VM's summary interface is declared where the VM is built. Naming one concrete
declaration here meant every VM carrying an identical one under another name
failed the assertion — and a failed assertion is indistinguishable from a VM
that cannot sync at all, so a wired client sat in a shipped build doing nothing.
That is exactly what happened: the node's VM answers with its own StateSummary,
the round demanded this package's, and adoption never ran on any chain.

The serving half took the summary type as a parameter for this reason and did
not have the problem. Now both halves read the same way, and neither cares which
declaration a summary arrives under so long as it answers the two or three
questions being asked of it.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-16 00:38:09 -07:00
..
2025-12-19 08:49:11 -08:00