DoT FoR GOoD

Hyperbridge Operational Restoration. How was the $5M TVL freeze resolved? @hyperbridge utilizes the BEEFY (Bridge Efficiency Enabling Finality Yielder) protocol to provide light-client proofs to 12 external networks. When Hyperbridge transitioned to on-demand coretime, it shifted from a fixed parachain slot to a parathread ID. The BEEFY runtime logic was previously scoped to only aggregate state roots from dedicated parachain slots. Consequently, Hyperbridge state transitions became "invisible" to the BEEFY Merkle Mountain Range (MMR) root, preventing external light clients from verifying cross-chain messages. The incident served as a live validation of @Polkadot's safety-first architecture. The protocol did not fail, and it successfully enforced its constraints. The Hyperbridge protocol initiated an automated halt, as in a trustless system, the absence of a cryptographic proof must result in a suspension of operations to protect TVL. BEEFY light clients incorporate a 21-day security cliff that ensures that if the Relay Chain and the client lose synchronization, the client "expires," preventing long-range attacks from decommissioned validators. The solution via PR #1073 modified the BEEFY pallet to explicitly include parathread 3367 in the MMR construction, restoring the chain of trust. The recovery was completed within the 21-day window via the Whitelisted Caller governance track, ensuring rapid deployment while maintaining 100% Relay Chain uptime.