Arbitrum delegates are considering an additional governance route on Ethereum that is designed to remain available if both the normal Layer 2 governor and the Security Council cannot repair the system.

Offchain Labs published the constitutional proposal on 2 October. A forum update says Entropy submitted it to a Snapshot temperature check on 15 October. NetNapz did not independently verify live vote totals or a final result.

How the recovery path would work

The proposal would deploy an L1ArbitrumGovernor, a new Ethereum timelock, delegate-mapping contracts and state-proof components. Voting power would still come from ARB delegated on Arbitrum One, but participants would prove that state on Ethereum against a confirmed Arbitrum assertion.

Contract-based delegates would register an Ethereum voting address through a mapping on Arbitrum. Externally owned accounts could submit an EIP-712 signature tied to a specific assertion. The proposed governor would use those mappings and proofs to establish proposal eligibility, quorum and voting power.

The design sets a 17-day delay before voting, a 21-day voting period and a 25-day timelock before execution. Offchain Labs says those windows incorporate delegate reaction time, worst-case assertion confirmation and a seven-day censorship allowance. The planned quorum would range from 150 million to 450 million delegated ARB, with a 50% numerator applied to the locked delegated-token total.

Recovery system is not approved or deployed

A temperature check is an early governance signal, not constitutional approval. The proposal still calls for contract finalisation, independent security review, test-environment exercises, publication of verified addresses and executable payloads, and a formal constitutional vote before deployment.

The affected-chain section also remained marked “to be confirmed” in the checked forum text, leaving unresolved whether the final scope would cover Arbitrum One, Nova or both. Delegates have additionally asked whether the mechanism should be limited to recovery actions rather than operate as a parallel governance route at any time.

Stale delegation is the central trade-off

Offchain Labs said on 13 October that the system would have no maximum assertion age and would not pause automatically. If the rollup stalled, the fallback would use the most recent confirmed assertion so that recovery could continue.

That improves availability, but it can separate the voting snapshot from current delegation choices. In a long outage, voting power proven on Ethereum could be weeks or months behind changes made on Arbitrum.

A 21 October response attributed to the GMX Governance Committee supported the recovery objective while recommending that every L1 proposal display the date of the confirmed assertion used for its voter snapshot. Other delegates have requested tests for snapshot completeness and immutability, a permissions map for the L1 and L2 executor roles, and clearer rules for conflicting or stalled proposals.

NetNapz assessment

The proposal addresses a real governance-availability problem without creating new ARB voting power. Its security question is not whether Ethereum can count proofs, but which Arbitrum state is accepted when the system is under stress.

Long delays create review and exit time, yet they do not by themselves make old delegation data current. Displaying assertion age would improve transparency, but it would not prevent a vote based on stale power. A maximum-age rule would reduce that risk while potentially disabling the recovery path during the outage it is meant to survive.

The material milestones are an auditable specification, explicit chain scope, published tests, an independent audit with remediations, final contract addresses and constitutional approval. Until those exist, this is a governance design under review—not an active emergency system, a new ARB utility mechanism or evidence of token demand.

Sources and verification limits

• Arbitrum governance forum: constitutional L1 voting recovery proposal, posted 2 October 2026; updates and delegate discussion checked 21 October.
• Arbitrum Foundation governance overview, checked for the existing governance context.

NetNapz reviewed the published proposal and discussion but did not audit the contracts, reproduce state proofs or independently verify live Snapshot totals. No price, flow or adoption claim is made.