# Arbitrum DAO Passes L1 Governance Recovery Temperature Check

Published 2026-10-23 · Crypto.world Team · Crypto.world

> ArbitrumDAO’s proposed Ethereum-based governance recovery system passed its Snapshot temperature check, with 210.6 million ARB voting in favor. The proposal outlines an additional L1 route for governance recovery, subject to technical review, auditing, testing and a constitutional vote.

## 210.6M ARB Vote in Favor

ArbitrumDAO’s proposed Ethereum-based governance recovery system cleared its Snapshot temperature check on October 22, giving the constitutional proposal broad delegate support but not final approval. About 210.7 million ARB participated, equivalent to 68% participation; roughly 210.6 million voted in favor, 9,700 voted against and 846.61 abstained.

Source [forum.arbitrum.foundation](https://forum.arbitrum.foundation/t/constitutional-establish-an-l1-voting-recovery-system/31534)

The vote is an early governance stage, not authorization to deploy the system. The proposal says a formal constitutional on-chain vote would follow technical review, security auditing, testing and publication of the final contracts and executable governance payload.

## An Ethereum Route for Arbitrum’s Failure Case

[Offchain Labs](https://crypto.world/companies/offchain-labs)’ proposal would let ArbitrumDAO create, vote on, queue and execute proposals through governance contracts on Ethereum Layer 1. Voting power would still come from ARB delegated on Arbitrum One, with that delegation state proven on Ethereum against a confirmed Arbitrum assertion. Approved actions would pass through a new L1 timelock to Arbitrum’s existing upgrade executors.

The design targets a narrow failure scenario: the ordinary L2 governance system is broken and the Security Council cannot act. It is presented as an additional DAO-controlled recovery route, not a replacement for the regular Arbitrum One process or a change to the Council’s constitutional powers. The proposal’s draft constitutional text, however, does not expressly restrict use of the L1 procedure to emergencies—a point delegates have asked the authors to clarify.

## Why the Procedure Takes More Than Two Months

The proposed schedule builds time for delegates to respond and for Arbitrum state proofs to be confirmed. Voting would begin 17 days after a proposal: three days for delegate reaction and registration, followed by as much as 14 days for assertion confirmation. The voting period would last 21 days, including a seven-day allowance for censorship delays, with a two-day extension if the constitutional threshold is reached near the end.

A successful proposal would then wait at least 25 days in the L1 timelock before execution. Contract-address delegates would register an L1 voting address through Arbitrum One’s DelegateMapping; individual wallet holders could use an EIP-712 signature bound to the relevant assertion. The proposal sets the minimum quorum at 150 million ARB and the maximum at 450 million ARB.

> “There is no maximum assertion age and nothing pauses: checkpoints fall back to the last confirmed assertion, so the L1 route still works when the rollup stalls.”
>
> Offchain Labs, the proposal’s authors, wrote in a reply on the Arbitrum governance forum.

## Stale Delegation Data Remains a Delegate Concern

That fallback drew questions during forum review. If assertion confirmations stall, the L1 system could rely on old delegation data even as delegations change on Arbitrum One. Members of GMX’s Governance Committee suggested showing the date of the confirmed assertion used for each voting snapshot so voters can judge how current the power distribution is.

Other delegates questioned whether the procedure’s emergency purpose matches constitutional language that would allow it as an additional route, and raised concerns about the new timelock’s reach through both upgrade executors. They also flagged a rule barring simultaneous ordinary and L1 proposals with conflicting actions: a proposal stalled by a governance failure might remain pending and block its own recovery counterpart.

## Steps Proposed Before a Constitutional Vote

The proposal outlines several steps before a constitutional on-chain vote: independent auditing, test-environment validation, publication of audit findings and final contract details, and publication of the executable governance payload. Deployment would depend on that vote passing. The affected-chain scope—Arbitrum One, Arbitrum Nova or both—also remains marked for confirmation in the forum proposal.

The confirmed temperature-check result is that the proposal passed, with 210.7 million ARB participating.

## Sources

1. Original source [Arbitrum Governance Forum](https://forum.arbitrum.foundation/t/constitutional-establish-an-l1-voting-recovery-system/31534) forum.arbitrum.foundation

Other pages read

2. [Arbitrum Proposals App](https://arbitrum.proposals.app/860820e0-ac17-4f3f-96a5-a428323e62ca/vote/1) arbitrum.proposals.app

## Related stories

- [Arbitrum DAO’s USDG Proposal Passes Offchain Vote With 199.5M ARB in Favor](https://crypto.world/news/arbitrum-dao-advances-100m-arb-usdg-plan)
- [Arbitrum DAO Sets Glamsterdam Fee Changes for a Later Vote](https://crypto.world/news/arbitrum-glamsterdam-l1-fee-parameters)
- [Fhenix Takes CoFHE to Ethereum and Arbitrum Mainnet](https://crypto.world/news/fhenix-cofhe-ethereum-arbitrum-mainnet)
- [Arbitrum Proposes Audited Route to Resume Stylus Activations](https://crypto.world/news/arbitrum-proposes-audited-route-resume-stylus-activations)
- [GMX Plans 180-Day Unstaking Wait on Arbitrum and Avalanche](https://crypto.world/news/gmx-180-day-unstaking-wait-arbitrum-avalanche)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/arbitrum-dao-passes-l1-governance-recovery-temperature-check
