# \[Constitutional\] AIP: Update the Upgrade Executors

**URL:** <https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463>\
**Category:** Finalized AIPs\
**Created:** [June 17, 2025, 2:05pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463 "2025-06-17T14:05:44Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![olimpio](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/olimpio/32/11_2.png) [@olimpio](https://forum.arbitrum.foundation/u/olimpio)\
**Post date:** [August 1, 2025, 3:17am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/21 "2025-08-01T03:17:08Z")

</div>

I have voted in favour. It makes the DAO’s upgrade process simpler and smoother, reducing the steps and effort needed for future changes while keeping everything under the DAO’s control, which lowers the chance of mistakes, saves time for developers, and strengthens how the system is managed without adding new costs or risks.

> [@Griff](#):
>
> This kind of proposal should just be optimistically approved

This might be interesting to explore! @Arbitrum

---

<div class="post-metadata">

**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:** [August 14, 2025, 9:48pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/22 "2025-08-14T21:48:42Z")

</div>

In-flight proposals should not be affected by this upgrade because the changes will not be made until this proposal passes a Tally vote and the proposal payload is executed on-chain. Proposals that precede this change to the Upgrade Executors proposal should continue to use the existing Upgrade Executors with the current functionality.

---

<div class="post-metadata">

**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:** [August 14, 2025, 9:49pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/23 "2025-08-14T21:49:56Z")

</div>

A new [third-party audit](https://docs.arbitrum.io/assets/files/2025-07-offchainlabs-upgrade-executor-report-900fbe3a31c6ca81e2949355f6134d33.pdf) of the new UpgradeExecutor contract has been completed. Trail of Bits reviewed the change set that introduces executeCall and in their report, they found no security-relevant issues. This complements the comprehensive January 2023 audit of Governance & Token Bridge, which also covered the UpgradeExecutor.

---

<div class="post-metadata">

**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:** [August 14, 2025, 9:52pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/24 "2025-08-14T21:52:05Z")

</div>

A new [third-party audit](https://docs.arbitrum.io/assets/files/2025-07-offchainlabs-upgrade-executor-report-900fbe3a31c6ca81e2949355f6134d33.pdf) of the new UpgradeExecutor contract has been completed. Trail of Bits reviewed the change set that introduces executeCall and in their report, they found no security-relevant issues.

---

<div class="post-metadata">

**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:** [August 20, 2025, 2:02pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/25 "2025-08-20T14:02:41Z")

</div>

Thanks for raising this, Hawkheik. Since your comment, we commissioned an [audit report](https://docs.arbitrum.io/assets/files/2025-07-offchainlabs-upgrade-executor-report-900fbe3a31c6ca81e2949355f6134d33.pdf) by Trail of Bits on the Upgrade Executor repo. Trail of Bits reviewed the implementation of _executeCall_, assessed it against the proposal’s intent, and checked for unintended side effects. Trail of Bits found no security-relevant issues.

As described in the report, executeCall enables the executor to make a direct external call as opposed to the prior path that used _delegatecalls_ via the _execute_ function. The change is about how an authorized upgrade is executed, not who authorizes it. The Upgrade Executor continues to execute only changes as instructed by the DAO (via the L1 Timelock) or by the Arbitrum security council; the audit also describes this governance scope explicitly. The addition of _executeCall_ does not alter those controls

---

<div class="post-metadata">

**Author:** ![paulofonseca](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/paulofonseca/32/15551_2.png) [@paulofonseca](https://forum.arbitrum.foundation/u/paulofonseca)\
**Post date:** [August 26, 2025, 5:52pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/26 "2025-08-26T17:52:24Z")

</div>

can we get some independent verification that the payload on the [onchain proposal](https://www.tally.xyz/gov/arbitrum/proposal/51852039695020109312343918128899814224888993575448130385109956762385891284115?govId=eip155:42161:0xf07DeD9dC292157749B6Fd268E37DF6EA38395B9) actually does what it says it does?  
@offchain @Frisson @krst @GFXlabs and so on?

ideally, before more people vote on it without verifying it.

---

<div class="post-metadata">

**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:** [August 29, 2025, 10:09am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/27 "2025-08-29T10:09:33Z")

</div>

The following reflects the views of L2BEAT’s governance team, composed of @krst, @Sinkas, and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.

We voted FOR and we’ve posted full rationale [here](https://forum.arbitrum.foundation/t/constitutional-aip-disable-legacy-tether-bridge/29503/34).

---

<div class="post-metadata">

**Author:** ![paulofonseca](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/paulofonseca/32/15551_2.png) [@paulofonseca](https://forum.arbitrum.foundation/u/paulofonseca)\
**Post date:** [October 16, 2025, 5:24pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463/28 "2025-10-16T17:24:04Z")

</div>

voted **Abstain** on this past offchain vote because I haven’t had the time to review this properly.

[Previous page](https://forum.arbitrum.foundation/t/constitutional-aip-update-the-upgrade-executors/29463.md?page=1)
