Restrict crypto bridge operations until controls are proven

The Roundtable discussion observed on 2026-07-24 tied multiple reported bridge incidents to the same recovery problem: trusted systems can continue issuing authority after a patch unless keys, signatures, sessions, or validators are revoked or revalidated. The immediate trigger is the packet’s reporting around AFX Trade bridge on Arbitrum, Verus-Ethereum Bridge, and Wanchain Bridge TreasuryCheck / Cardano-side Midnight NIGHT treasury, plus the Roundtable’s conclusion that bridge-signing keys require proof of custody, quorum independence, validation binding, reserve backing, and emergency controls before full reopening.

Affected operators are crypto bridge protocols whose signing, quorum, custody, message-validation, reserve-backing, or emergency controls are under question.

The packet specifically names AFX Trade bridge on Arbitrum, where the public item reports validator signing keys were compromised; Verus-Ethereum Bridge, where the public item reports a second exploit and $19.1M in losses; and Wanchain Bridge TreasuryCheck / Cardano-side Midnight NIGHT treasury, where the public item reports a TreasuryCheck flaw draining the treasury.

Bridge users and liquidity providers are affected because reopening before validated source-event binding, reserve backing, and emergency controls are proven can expose deposits, withdrawals, and destination-chain payouts to authority or validation failures.

Validators and custody teams are affected because they must rotate keys, remove compromised validators, and prove quorum independence before full operations resume.

The Roundtable final synthesis supports the control posture by stating that bridge-signing keys fit the same recovery problem as other trusted authority systems: patching does not revoke trust.

The identity-architecture contribution supports artifact-level recovery by naming bridge validator keys as items that require response beyond patching.

The crypto-fincrime contribution supports the bridge-specific risk model by describing bridge failures as governance failures over who can create cross-chain truth, and by reporting that AFX involved hot-validator signatures meeting quorum, while explicitly treating the incident narrative as reported.

The handoff item for AFX Trade bridge on Arbitrum says it was reportedly drained after validator signing keys were compromised. The handoff item for Verus-Ethereum Bridge says a second exploit reportedly brought losses to $19.1M.

The handoff item for Wanchain Bridge TreasuryCheck says a flaw reportedly drained the Cardano-side Midnight NIGHT treasury.

The evidence review supports pausing or restricting operations until signer custody, quorum independence, transaction validation, reserve backing, and post-incident fixes are proven, while separately flagging that primary postmortems are absent.

The crypto-fincrime contributor framed AFX Trade bridge on Arbitrum, Verus-Ethereum Bridge, and Wanchain Bridge TreasuryCheck / Cardano-side Midnight NIGHT treasury as failures of signing authority, validation discipline, and revocation rather than ordinary patch tickets.

The identity-architecture contributor reinforced that recovery has to happen at the artifact level, including bridge validator keys, not just at the code-patch level.

The evidence review accepted the operational posture to pause or restrict operations, but separated that from unconfirmed incident mechanics and disputed public loss figures.

The linker found no existing bounded Decision Record target, and the arbiter selected a new operational-action record with caveats on authoritative sourcing and wording.