# Constitutional - Extend Delay on L2Time Lock **URL:** \ **Category:** Finalized AIPs\ **Created:** [August 23, 2024, 3:46pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470 "2024-08-23T15:46:13Z")\ **Posts on this page:** 9\ **Page:** 4
**Author:** ![BlockworksResearch](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/blockworksresearch/32/14962_2.png) [@BlockworksResearch](https://forum.arbitrum.foundation/u/BlockworksResearch)\ **Post date:** [October 9, 2024, 4:41pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/63 "2024-10-09T16:41:09Z")
Blockworks Research will be voting FOR this proposal on Tally. This seems like a clearly needed upgrade for the exit window for Arbitrum. Since the security member review, the timelock delay has been found to be safe and a reasonable upgrade for increasing security. ---
**Author:** ![krst](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/krst/32/1357_2.png) [@krst](https://forum.arbitrum.foundation/u/krst)\ **Post date:** [October 9, 2024, 7:36pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/64 "2024-10-09T19:36:00Z")
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two. We are voting FOR the proposal. As [we pointed out during](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/32) the temp-check vote, if this proposal is successful, Arbitrum’s ‘Exit Window’ slice on [L2BEAT’s Risk Rosette](https://gov.l2beat.com/t/the-risk-rosette-framework/292) will be turned yellow. Additionally, Arbitrum will be one step closer to the 30d exit window required for Stage 2 classification as outlined in [L2BEAT’s stages framework](https://gov.l2beat.com/t/the-stages-framework/291#stage-2-requirements-4). Having reviewed the executable ourselves to confirm that the changes it will bring match the described modifications and also having the [security review from the ARDC](https://forum.arbitrum.foundation/t/arbitrum-l2-time-lock-delay-proposal-security-review/26837/1) as a cross-check, we’re comfortable voting in favor of the proposal onchain. ---
**Author:** ![WinVerse](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/winverse/32/10523_2.png) [@WinVerse](https://forum.arbitrum.foundation/u/WinVerse)\ **Post date:** [October 10, 2024, 10:53am UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/65 "2024-10-10T10:53:32Z")
DAOplomats is voting for this proposal on Tally. We are maintaining [our support of the proposal](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/38) from the temp check ---
**Author:** ![bee926](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/bee926/32/12795_2.png) [@bee926](https://forum.arbitrum.foundation/u/bee926)\ **Post date:** [October 10, 2024, 5:14pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/66 "2024-10-10T17:14:26Z")
gTrade is in favor of the extended delay! While it might slow down the proposal implementation process, it provides added protection against governance attacks, increases overall security for users, and gives the security council more time to respond in case of any malicious actions. ---
**Author:** ![Tane](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/tane/32/3187_2.png) [@Tane](https://forum.arbitrum.foundation/u/Tane)\ **Post date:** [October 10, 2024, 10:24pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/67 "2024-10-10T22:24:58Z")
We vote **FOR** the proposal on Tally. We maintain [our stance](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/35) made in the Snapshot phase and continue to support the change after having reviewed [the report](https://forum.arbitrum.foundation/t/arbitrum-l2-time-lock-delay-proposal-security-review/26837) by the ARDC. ---
**Author:** ![ocandocrypto](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/ocandocrypto/32/5015_2.png) [@ocandocrypto](https://forum.arbitrum.foundation/u/ocandocrypto)\ **Post date:** [October 11, 2024, 2:31am UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/68 "2024-10-11T02:31:30Z")
As I mentioned before this is a huge improvement for the ecosystem. > [@Constitutional - Extend Delay on L2Time Lock](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/36): > > I voted FOR this proposal: It’s a no-brainer for me to provide users and the security council with more time to exit after a constitutional proposal is passed. Also in our way to Stage 2 and understanding importance for stage in rollups next year, this is an important step here. ---
**Author:** ![snowdot](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/snowdot/32/8991_2.png) [@snowdot](https://forum.arbitrum.foundation/u/snowdot)\ **Post date:** [October 11, 2024, 12:21pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/69 "2024-10-11T12:21:25Z")
Gm, gm ✨ The results are in for the **Constitutional AIP - Extend Delay on L2Time Lock** on-chain proposal. See how the community voted and more Arbitrum stats: > **[\# Constitutional AIP - Extend Delay on L2Time Lock](https://dhive.io/proposal/1385)** > > Explore # Constitutional AIP - Extend Delay on L2Time Lock proposal, results, votes, and analytics ---
**Author:** ![raam](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/raam/32/9309_2.png) [@raam](https://forum.arbitrum.foundation/u/raam)\ **Post date:** [October 25, 2024, 2:03pm UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/70 "2024-10-25T14:03:29Z")
> As a result of this proposal being executed, Arbitrum One is now closer to being a ‘Stage 2 Rollup’ ---
**Author:** ![AlexLumley](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/alexlumley/32/3790_2.png) [@AlexLumley](https://forum.arbitrum.foundation/u/AlexLumley)\ **Post date:** [November 1, 2024, 4:54am UTC](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/71 "2024-11-01T04:54:17Z")
Voted FOR: Extend Delay on L2Time Lock > **[Tally | Arbitrum | Constitutional AIP - Extend Delay on L2Time Lock](https://www.tally.xyz/gov/arbitrum/proposal/27888300053486667232765715922683646778055572080881341292116987136155397805421?govId=eip155:42161:0xf07DeD9dC292157749B6Fd268E37DF6EA38395B9)** > > Constitutional AIP - Extend Delay on L2Time Lock Voting Rationale: [Alex Lumley (Savvy DAO) Delegate Communication Thread - #37 by AlexLumley](https://forum.arbitrum.foundation/t/alex-lumley-savvy-dao-delegate-communication-thread/26147/37) As stated in my previous Commenting Rationale ([Constitutional - Extend Delay on L2Time Lock - #41 by AlexLumley](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470/41)) , I hoped this proposal would include the points below. While these have not been included I do hope future iterations will include them: • **Consider Emergency Scenarios:** • Define specific emergency situations where a shorter time lock could be justified. • This ensures flexibility to respond swiftly in rare but urgent cases, balancing speed and security. • **Continuous Evaluation of Delay’s Impact:** • Regularly assess how the delay affects user confidence and operational efficiency. • Use data-driven insights from these evaluations to inform future adjustments if needed. • **Incorporate Periodic Reviews:** • Schedule periodic reviews to assess the time lock’s relevance and effectiveness. • Keeps the system responsive and aligned with the evolving needs of the Arbitrum ecosystem, promoting agility and adaptability. [Previous page](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470.md?page=3)