This AIP combines and puts forward three separate proposals for the ArbitrumDAO to consider: Remove Cost Cap on Arbitrum Nova, Update the Upgrade Executors, and Disable Legacy Tether Bridge. All of the aforementioned proposals have previously passed a Snapshot vote, reaching a quorum of 3% votable $ARB.
The first proposal will remove the Amortized Cost Cap, which is expected to result in higher gas fees for users on Arbitrum Nova. This increase is necessary to ensure the long-term sustainability of the network and reduce the financial burden on the Arbitrum Foundation.
The second proposal will replace the Upgrade Executor contracts on Arbitrum One, Arbitrum Nova, and Ethereum mainnet with upgraded versions. The modernized version introduces an additional function that enables the Upgrade Executor to execute an upgrade by directly calling the target contract, rather than indirectly delegate calling an upgrade contract.
The third proposal seeks to disable the legacy USDT bridge for Arbitrum One, given the activation of the new USDT0 bridge in January 2025. This proposal seeks to disable the legacy bridge entirely, rather than continue with the current configuration, which subjects depositors to a week-long delay and risks loss of funds if the depositor is a smart contract.
Arbitrum Nova was initially positioned as a cost-efficient alternative to Arbitrum One, offering 30-50x cheaper transaction fees at launch. However, several developments have significantly reduced Nova’s competitive advantage:
Given the now-minimal cost advantage over Arbitrum One and the rise of Orbit chains, maintaining an amortized cost cap on Nova — which currently prevents batch posters from recovering full L1 costs — is no longer justifiable. Removing the cap will stop the Arbitrum Foundation from providing subsidies and align cost recovery with actual usage.
Accordingly, removing the cap (i.e., setting it to 0 bips) would:
Historical data on Arbitrum Nova batch poster deficits can be seen here. This data highlights the ongoing inefficiencies and justifies the removal of the amortized cost cap.
The Upgrade Executors controlled by the DAO are responsible for carrying out critical upgrades on Arbitrum One, Arbitrum Nova, and Ethereum such as protocol contract upgrades, system parameter changes, and more. Currently, the traditional Upgrade Executor contracts in place only support one function for executing an upgrade: execute(). When called by the owner of the Upgrade Executor, the execute() function will perform a delegate call to an upgrade contract, which facilitates subsequent calls to target contracts and ultimately executes the upgrade. This indirect method of calling and execution can complicate upgrades and require additional development and deployments.
The modern version of the Upgrade Executor introduces a new function, executeCall(), which allows the Upgrade Executor to directly call target contracts and execute upgrades, removing the need for delegate calls to upgrade contracts. While the existing execute() call is still supported, the new executeCall() function enables the Upgrade Executor to implement upgrades in a lighter weight fashion. In the future, upgrades that use this method may not require dedicated action contracts, simplifying the process and saving development energy.
Historically, the existing USDT bridge for Arbitrum One was the primary path for bridging Tether to and from Arbitrum One. The new USDT0 standard introduced a modernized alternative that has become the go-to solution. However, the legacy USDT bridge is still technically enabled, which presents several issues.
First, withdrawals from the legacy bridge to L1 are subject to a seven-day delay, which is meaningfully slower than the new USDT0 bridge which can process bridge transactions in seconds or minutes. Also, once this delay has elapsed, deposits are auto-withdrawn on L1. This inconvenience can be addressed by disabling the legacy bridge and directing users exclusively to the new USDT0 bridge.
Second, user funds could be lost if a smart contract deposits to the legacy bridge on their behalf. The legacy bridge is currently configured to auto-withdraw funds as soon as possible back to the depositor; however, this auto-withdraw configuration can cause problems for smart contracts that deposit on behalf of end users but do not have withdrawal or refund functionality. While it’s possible to recover funds in this scenario, it is certainly sub-optimal for smart contract operators and end users that delegate to them. Disabling the legacy bridge prevents smart contracts from encountering this issue and putting funds at risk. Also, once the legacy bridge is disabled, any transaction submitted to it will simply revert; this applies to third party integrations as well as direct user interactions.
... please visit link below to view full proposal
https://tally.xyz/gov/arbitrum/proposal/51852039695020109312343918128899814224888993575448130385109956762385891284115