# \[CONSTITUTIONAL\]: Establish an L1 Voting Recovery System **URL:** \ **Category:** Proposals\ **Tags:** proposal\ **Created:** [October 2, 2026, 11:15pm UTC](https://forum.arbitrum.foundation/t/constitutional-establish-an-l1-voting-recovery-system/31534 "2026-10-02T23:15:40Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![offchain](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/offchain/32/16618_2.png) [@offchain](https://forum.arbitrum.foundation/u/offchain)\ **Post date:** [October 13, 2026, 4:13pm UTC](https://forum.arbitrum.foundation/t/constitutional-establish-an-l1-voting-recovery-system/31534/4 "2026-10-13T16:13:12Z")
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. Each phase is padded for the full 7-day censorship budget: a 17d voting delay (3d + 14d worst-case confirmation), a 21d voting period (14d + 7d) and a 25d L1 timelock (14d + 8d + 3d), which keeps the same exit window as the L2 path. EOA claims are EIP-712 signatures bound to a single assertion hash on the L2StateMirror domain. Contract delegates register through the L2 DelegateMapping (force inclusion takes at most 24h). The new L1 timelock holds the EXECUTOR\_ROLE on both L1 and L2 upgrade executors, which is the same as the existing L1 timelock. --- _[View the full topic](https://forum.arbitrum.foundation/t/constitutional-establish-an-l1-voting-recovery-system/31534)._