mirror of
https://github.com/luxfi/consensus.git
synced 2026-09-24 00:26:58 +00:00
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]>