Cross-chain bridges: what governance gap are teams missing?

TL;DR: Cross-chain bridges keep losing funds when destination-side checks accept fabricated, replayed, or reinterpreted source events, according to Blockaid's H1 2026 Onchain Security Report, which also highlighted at least seven notable bridge incidents in the first half of the year. The controlling assumption is that a verified message proves a real deposit, and that assumption breaks whenever the bridge trusts representation instead of observable source-chain state.

Editorial analysis by NHI Mgmt Group, based on content published by Blockaid: “Cross-Chain Verification Failures: How Bridges Lost Another $24.6M and How Onchain Teams Stay Protected”.

By the numbers:

• Blockaid's H1 2026 Onchain Security Report flagged at least seven noteworthy bridge incidents led by the $292 million KelpDAO exploit.
• July and August produced 10 more bridge-verification incidents totaling roughly $24.6 million, with about $2.7 million recovered.
• Across Protocol lost roughly $4.5 million to forged deposits, Wanchain lost about $9.3 million to a reused signature, and Verus lost $7.54 million to an unbound payout.

Key questions

Q: What breaks when a bridge verifies a message instead of the source-chain event itself?

A: The bridge can release real value for a deposit that never happened.

Q: Why do offchain relayers and indexers create bridge risk?

A: They sit inside the trust boundary and can turn failed or fabricated activity into an apparently valid withdrawal request.

Q: What are the signs that cross-chain verification is failing?

A: Look for payouts triggered by reconstructed events, reused signatures, inconsistent parsing between components, and destination releases that cannot be tied cleanly to funded source-chain activity.

Practitioner guidance

• Bind payouts to source-chain state Require every destination release to match a real, funded source event before any value leaves the bridge path.
• Canonicalize signed payloads Define one parseable message format for every signed bridge request and reject any encoding that could produce two different meanings from the same signature.
• Bring relayers into control scope Assign ownership, monitoring, and approval rules to relayers and indexers because they can transform failed source events into accepted destination-side requests.

Bottom line: Cross-chain bridge losses keep recurring because destination systems accept proofs that do not sufficiently bind to real source-chain state.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →