# 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:** 1\ **Showing post:** 64
**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. --- _[View the full topic](https://forum.arbitrum.foundation/t/constitutional-extend-delay-on-l2time-lock/26470)._