Avalanche Bridge

This review rejects the Avalanche Bridge because a four-party committee, smaller than every other multi-party bridge this registry has reviewed, controls it. The Avalanche Bridge is Avalanche’s original Ethereum-to-C-Chain canonical bridge, accessed through the Core wallet. It secures transfers with only four ”Wardens” through an Intel SGX secure enclave; three of the four must report identical transaction data before the enclave mints or releases funds. That group is smaller than the already-rejected Gnosis Chain xDAI Stake Bridge’s 4-of-7 validators. One of the four Wardens is Ava Labs itself, the same organization that built and operates the underlying network. None of this registry’s other reviewed bridges has the same form of related-party concentration. The bridge also depends on Intel SGX attestation, a separate hardware risk on top of Warden honesty.

Review triggers: events that reopen the verdict
• The Warden committee expands materially, for example to seven or more independent parties, with no single approving party also operating the underlying network
• An independent, dated security audit of the current SGX enclave configuration and Warden software is published with no unresolved high-severity findings
• The bridge migrates to a design backed by an Ethereum-native fraud-proof or validity-proof system, removing dependence on Warden honesty and SGX hardware attestation
• Twelve consecutive months with no Warden-collusion, SGX side-channel, or enclave-compromise incident

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-17.

The research file

Mechanism

This is Avalanche’s original Ethereum-to-C-Chain bridge. It is distinct from Avalanche’s newer Interchain Messaging tool, which was built for its own subnet ecosystem. Four Wardens, each running an indexing server plus AvalancheGo and Geth nodes, monitor both chains and send transaction data to an Intel SGX secure enclave. Shamir Secret Sharing splits the enclave’s private key across the four Wardens, so no single Warden holds it outright. Still, agreement among only three of the four is enough to act.

Control and governance

The four Wardens are Avascan, BwareLabs, Halborn, and Ava Labs itself. One of the four parties securing the bridge is therefore the same organization that built and operates the underlying network, a related-party concentration this review flags directly. Before the enclave mints or releases funds, three of the four Wardens, a 75% threshold in a four-member committee, must report identical transaction data. The total committee is smaller than the already-rejected Gnosis Chain xDAI Stake Bridge’s 4-of-7 validator set. The design also adds a second trust assumption, separate from Warden honesty: the integrity of Intel SGX hardware attestation. That technology has a documented industry history of side-channel flaws. No such exploit has been confirmed against this specific bridge, but the bridge still depends on the hardware.

Incident record

This review found no confirmed exploit of this specific Avalanche Bridge. That includes a targeted check of the major 2026 bridge-hack wave already covered elsewhere in this registry, such as the Kelp DAO and Drift Protocol exploits, neither of which named this bridge. The lack of an incident is a narrow negative finding, not proof that the bridge will last, given the committee’s small size.

Exit

Transfers take roughly 10 to 15 minutes, with Ethereum finality rather than any Avalanche-side delay accounting for most of that time. This is fast under normal conditions, but there is no fraud-proof or validity-proof backstop like the ones used by rollup bridges. Correct transfers depend entirely on three of four Wardens acting properly and the SGX enclave attestation holding, not on a separate cryptographic or economic guarantee.

Comparison

Base, Arbitrum, and Optimism are all approved with limits in this registry, and all inherit Ethereum-native fraud-proof or validity-proof security. The Avalanche Bridge has no rollup-style proof system. Its 3-of-4 committee is even smaller than the already-rejected Gnosis Chain xDAI Stake Bridge’s committee, and its SGX hardware trust adds a separate risk that Gnosis’s bridge does not bear. One of the four approving parties is also the network’s own operator. Neither Gnosis’s nor the already-rejected Wormhole’s validator sets share that related-party fact in the same way.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• LI.FI — Avalanche Bridge: a deep dive · secondary · accessed 2026-08-17
  Supports: Warden architecture, 3-of-4 threshold, Shamir Secret Sharing, withdrawal timing
• Avalanche — Avalanche Bridge: secure cross-chain asset transfers using Intel SGX · primary · accessed 2026-08-17
  Supports: Warden identities, SGX enclave design
• Avalanche Builder Hub — bridge architecture · primary · accessed 2026-08-17
  Supports: distinction from Interchain Messaging
• Avalanche Builder Hub — bridge hacks · primary · accessed 2026-08-17
  Supports: incident-pattern context
• CCN — biggest DeFi hacks and exploits of 2026 · secondary · accessed 2026-08-17
  Supports: confirms this bridge not named among major 2026 incidents

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.