Arbitrum Bridge
Approved for: positions on Ethereum, Arbitrum One. The limits are in the memo below.
We approve Arbitrum’s canonical Nitro-based optimistic-rollup bridge with limits. The bridge contracts themselves have a clean exploit record, and the bridge has a documented emergency-response power that has been used. On 2026-04-20, the 12-member Security Council froze about $71M in ETH linked to the Kelp DAO/LayerZero exploit, recovering roughly a quarter of the stolen value. It later released the funds through a governance vote and federal court order after the legal process ended. Non-emergency contract changes face a real delay, roughly eleven days across an 8-day L2 and 3-day L1 window. That is a stronger check than Base’s zero-delay upgrade path, reviewed separately in this registry. The freeze protected users, but it also confirms that 9 of 12 council members can lock funds without prior governance approval. This known and bounded concentration risk requires the advisor to assess the fit for the client.
- Any confirmed exploit of the native bridge contracts (Delayed Inbox, Outbox, Bridge.sol) as distinct from third-party bridges or DEXs built on Arbitrum
- Security Council threshold or membership changes without the required public transparency report
- An emergency action freezes funds without a subsequent governance vote and transparency report within a reasonable published window
- The seven-day withdrawal challenge period is shortened or bypassed for a class of users without equivalent public availability
- A second Security Council emergency freeze occurs without law-enforcement or judicial involvement comparable to the April 2026 precedent
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
Arbitrum uses a standard Nitro optimistic-rollup design. Deposits from Ethereum to Arbitrum are fast. Withdrawals face a seven-day challenge period. The system accepts a withdrawal on a provisional basis while any party can submit a fraud proof, and a user can claim the funds on Ethereum only after the window closes without a successful challenge. This delay comes from the rollup design. Arbitrum could not shorten it without changing its security model.
Control and governance
The Security Council is a 12-member multisig with two modes. Emergency Actions require 9-of-12 approval and can take any action to protect chain integrity with no delay. Non-Emergency Actions also require 9-of-12 approval, but they must pass through the DAO’s AIP process. This creates an 8-day L2 delay plus a 3-day L1 delay before deployment. The Council must publish a transparency report after every emergency action, and the DAO can remove Council members. This differs from Base’s nested 2-of-2 operator-plus-council model, which has no delay on any upgrade path.
The April 2026 freeze: power exercised, not just documented
After the 2026-04-18 Kelp DAO/LayerZero exploit, reviewed separately in this registry’s `layerzero-v2` entry, the attacker used unbacked rsETH as Aave collateral to borrow about $230M in ETH. On 2026-04-20, the Security Council froze 30,766 ETH, about $71M, tied to the exploit after consulting law enforcement. It moved the funds beyond reach without a full governance vote. That recovered roughly a quarter of the total loss and ranks among the fastest such interventions on record. The funds also became part of a US federal court case after parties tied to North Korea-related judgments sought a claim over them. Arbitrum delegates voted about 91% to approve release to an Aave-controlled recovery wallet, and a federal judge authorized the transfer on 2026-05-09. No one exploited the native bridge contracts in this or any other identified incident. Two July 2026 incidents sometimes linked to Arbitrum, the AFX Trade bridge hack and the Ostium oracle-key exploit, were confirmed third-party protocol failures unrelated to the canonical bridge.
Exit under stress
The seven-day challenge window applies to every withdrawal, with no official faster path. Third-party liquidity bridges can advance funds against a pending withdrawal, but they carry a separate trust model and fall outside the scope of this canonical-bridge entry. A client relying on this bridge should plan for the full seven days needed for a guaranteed canonical exit and should not assume same-day liquidity.
Comparison
Compared with Base’s canonical bridge, which this registry approved with limits, Base has zero delay on any upgrade once its 2-of-2 threshold is met. Arbitrum’s non-emergency path has a real delay of roughly eleven days. Both have a delay-free emergency path that gives a small elected group real power to act on its own, and Arbitrum’s April 2026 freeze proves that it uses this power in practice. Neither bridge is an outright better choice. Both carry the same type of concentrated governance risk, which remains relevant to client-specific selection and sizing.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Arbitrum Docs — bridge quickstart · primary · accessed 2026-08-17
Supports: mechanism - Arbitrum Foundation Support — why wait 7 days to claim funds · primary · accessed 2026-08-17
Supports: challenge period rationale - Arbitrum DAO Governance Docs — Security Council overview · primary · accessed 2026-08-17
Supports: 9-of-12 emergency and non-emergency structure - Arbitrum DAO Governance Docs — lifecycle and anatomy of an AIP · primary · accessed 2026-08-17
Supports: AIP phases, upgrade delay - CoinDesk — Arbitrum freezes $71 million in ether tied to Kelp DAO exploit · secondary · accessed 2026-08-17
Supports: freeze event - CoinDesk — Arbitrum delegates back $71M ETH recovery plan despite U.S. seizure fight · secondary · accessed 2026-08-17
Supports: governance vote, legal dispute - Crowdfund Insider — federal court authorizes Aave transfer of $71M ETH from Arbitrum · secondary · accessed 2026-08-17
Supports: judicial resolution - The Defiant — attacker drains $24M in USDC from AFX bridge on Arbitrum · secondary · accessed 2026-08-17
Supports: native bridge unaffected
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.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |
| Arbitrum One | Approved with limits | Mixed control | a single sequencer orders >99% of transactions and admin keys can upgrade bridge contracts on a ~7-day timelock. |