|
| 1 | +--- |
| 2 | +title: Upgrade 16 - Protocol upgrade |
| 3 | +description: Learn how to prepare for the Upgrade 16 protocol changes. |
| 4 | +lang: en-US |
| 5 | +content_type: notice |
| 6 | +topic: upgrade-16-changes |
| 7 | +personas: |
| 8 | + - chain-operator |
| 9 | +categories: |
| 10 | + - security |
| 11 | + - protocol |
| 12 | + - infrastructure |
| 13 | + - interoperability |
| 14 | +is_imported_content: 'false' |
| 15 | +--- |
| 16 | + |
| 17 | +import { Steps, Callout } from 'nextra/components' |
| 18 | + |
| 19 | +# Upgrade 16: Protocol upgrade |
| 20 | + |
| 21 | +This page outlines important changes related to Upgrade 16 for chain operators and users. The upgrade proposal includes modifications to the OP Stack that will set the Superchain up for continued success through the remainder of 2025. |
| 22 | + |
| 23 | +## What's included in Upgrade 16 |
| 24 | + |
| 25 | +Upgrade 16 contains these main changes: |
| 26 | + |
| 27 | +* **Interop-Ready smart contracts**: Interoperability is critical to realizing the Superchain as a unified network of OP Chains. This upgrade begins the rollout of foundational interoperability features by updating the `OptimismPortal` to handle future cross-chain messaging safely and extensibly. This upgrade does not turn on interop yet. |
| 28 | +* **Stage 1 updates**: Modifications to meet [L2Beat's updated Stage 1 requirements](https://forum.l2beat.com/t/stages-update-a-high-level-guiding-principle-for-stage-1/338) from January 2025, including removal of `DeputyGuardianModule` and updates to `DeputyPauseModule`. |
| 29 | +* **Go 1.23 Support in Cannon**: Updates to Cannon to support Go 1.23, allowing OP Stack to benefit from upstream go-ethereum changes. |
| 30 | +* **Max gas limit increase**: Update to `MAX_GAS_LIMIT` from 200m to 500m gas after improvements to OP Stack infrastructure and the Cannon proof system. |
| 31 | +* **Additional safety improvements**: Authentication for critical contract functions and simplification of `DelayedWETH` contract control. |
| 32 | + |
| 33 | +## For chain operators |
| 34 | + |
| 35 | +Upgrade 16 is an L1 smart contracts upgrade for the OP Stack. We do not expect any downtime or changes in performance. |
| 36 | + |
| 37 | +Chain operators should be aware that Upgrade 16 involves a one-time invalidation of all existing withdrawal proofs. Users who have proven withdrawals can either finalize withdrawals prior to the activation of Upgrade 16 or will be required to re-prove these withdrawals after the upgrade activates. |
| 38 | + |
| 39 | +If this proposal is accepted, multisig ceremonies will be coordinated to execute upgrade transactions. The following transactions will be executed on the respective chains: `OP`, `Soneium`, `Ink`, `Base`, `Unichain`, `Mode`, `Zora`, `Arena Z`, `Swell`, `World Chain`, and `Metal ` on both Mainnet and Sepolia. Depending on the current state of the chain the execution times will vary. If your Optimism governed chain is not in this list, please reach out to OP Labs Solutions Engineering to coordinate your upgrade. These upgrade tasks will be prepared in the [superchain-ops repo](https://github.com/ethereum-optimism/superchain-ops/tree/main/src/improvements/tasks). |
| 40 | + |
| 41 | +The tentative execution dates of these upgrades tasks can be tracked in our [release board](https://github.com/orgs/ethereum-optimism/projects/117/views/12). |
| 42 | + |
| 43 | +### For permissionless fault proof enabled chains |
| 44 | + |
| 45 | +Chains running permissionless fault proofs will need to deploy new dispute game contracts with new absolute prestates. |
| 46 | + |
| 47 | +<Steps> |
| 48 | + ### Verify the new absolute prestate |
| 49 | + |
| 50 | + <Callout type="info"> |
| 51 | + As of upgrade 14, the 64 bit multi-threaded version of cannon is utilized. |
| 52 | + </Callout> |
| 53 | + |
| 54 | + The absolute prestate is generated with the [op-program/v1.6.1-rc.1](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.6.1-rc.1). You can use this new absolute prestate `0x03eb07101fbdeaf3f04d9fb76526362c1eea2824e4c6e970bdb19675b72e4fc8` for the following chains: |
| 55 | + |
| 56 | + * Mainnet and Sepolia: `OP`, `Soneium`, `Ink`, `Base`, `Unichain`, `Mode`, `Zora`, `Arena Z`, `Swell`, `World Chain`, and `Metal` |
| 57 | + |
| 58 | + You can verify this absolute prestate by running the following [command](https://github.com/ethereum-optimism/optimism/blob/d6fb90dd489e39efa206b55200766ccc075c1d9b/Makefile#L130-L132) in the root of the monorepo on the `op-program/v1.6.1-rc.1` tag: |
| 59 | + |
| 60 | + ```shell |
| 61 | + make reproducible-prestate |
| 62 | + ``` |
| 63 | + |
| 64 | + This will output the calculated prestates, which will look something like: |
| 65 | + |
| 66 | + ```shell |
| 67 | +-------------------- Production Prestates -------------------- |
| 68 | + |
| 69 | + |
| 70 | +Cannon64 Absolute prestate hash: |
| 71 | +0x03eb07101fbdeaf3f04d9fb76526362c1eea2824e4c6e970bdb19675b72e4fc8 |
| 72 | + |
| 73 | +-------------------- Experimental Prestates -------------------- |
| 74 | + |
| 75 | +CannonInterop Absolute prestate hash: |
| 76 | +0x03fc3b4d091527d53f1ff369ea8ed65e5e17cc7fc98ebf75380238151cdc949c |
| 77 | + |
| 78 | +Cannon64Next Absolute prestate hash: |
| 79 | +0x03eb07101fbdeaf3f04d9fb76526362c1eea2824e4c6e970bdb19675b72e4fc8 |
| 80 | + ``` |
| 81 | + |
| 82 | + * The "Cannon64" hash is the 64-bit prestate. |
| 83 | + |
| 84 | + Verify that your target prestate was calculated as expected and matches the corresponding entry in |
| 85 | + [standard-prestates.toml](https://github.com/ethereum-optimism/superchain-registry/blob/main/validation/standard/standard-prestates.toml). |
| 86 | + |
| 87 | + ### Upload your new preimage file |
| 88 | + |
| 89 | + During the previous step, you also generated the preimage of the absolute prestate, which is the op-program serialized into a binary file. You'll find that new file at `optimism/op-program/bin/prestate-mt64.bin.gz`. Rename that file to have the absolute prestate hash as the filename so it looks like `PRESTATEHASH.bin.gz`. |
| 90 | + |
| 91 | + Upload that file to where you're storing your other absolute preimage files. This should be the location where you're pointing your `--cannon-prestates-url` at. The `op-challenger` will grab this file and use it when it needs to challenge games. |
| 92 | + |
| 93 | + ### Deploy new dispute game contracts |
| 94 | + |
| 95 | + You will then take the absolute prestate and deploy new `FaultDisputeGame` and `PermissionedDisputeGame` contracts with that value. |
| 96 | + |
| 97 | + ### Update the DisputeGameFactory |
| 98 | + |
| 99 | + You will then need to update the `DisputeGameFactory` to point to the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. |
| 100 | + |
| 101 | + ### Execute the upgrade |
| 102 | + |
| 103 | + Once your `op-challenger` is ready with the new preimage, you can execute the "Set Dispute Game Implementation" transaction. Please simulate and validate that the expected output prior to executing the transaction. |
| 104 | +</Steps> |
| 105 | + |
| 106 | +## For bridges and users |
| 107 | + |
| 108 | +<Callout type="warning"> |
| 109 | + All withdrawals that are not finalized before the Fault Proofs upgrade executes will need to be reproven after the upgrade is complete. You may want to consider waiting until after the upgrade is complete to begin a withdrawal during this 7-day window. |
| 110 | +</Callout> |
| 111 | + |
| 112 | +Users should be aware of the following impacts: |
| 113 | + |
| 114 | +### Withdrawal flow changes |
| 115 | + |
| 116 | +1. There will be a one-time invalidation of all pending withdrawal proofs created on L1. |
| 117 | + |
| 118 | +2. Complete any pending withdrawals before the upgrade is executed |
| 119 | + |
| 120 | +3. Avoid creating new withdrawal proofs that would not become executable in time |
| 121 | + |
| 122 | +4. If a withdrawal was invalidated, submit a second withdrawal proof transaction on L1 |
| 123 | + |
| 124 | +This invalidation does not place any ETH or ERC-20 tokens at risk. |
| 125 | + |
| 126 | +## Technical details |
| 127 | + |
| 128 | +### Interop-ready smart contracts |
| 129 | + |
| 130 | +Upgrade 16 updates the core bridge contracts of the OP Stack to support native interoperability. Key modifications include: |
| 131 | + |
| 132 | +* The `OptimismPortal` now relies on the `AnchorStateRegistry` as the source of truth for the validity of dispute games |
| 133 | +* The `OptimismPortal` now stores ETH in a dedicated `ETHLockbox` contract |
| 134 | +* The `OptimismPortal` includes a version of the `proveWithdrawalTransaction` function that supports the updated `SuperFaultDisputeGame` implementation (disabled by default) |
| 135 | + |
| 136 | +### Stage 1 updates |
| 137 | + |
| 138 | +* The `DeputyGuardianModule` has been removed |
| 139 | +* The `DeputyPauseModule` has been updated to be installed into the Security Council's guardian safe |
| 140 | +* The pause action now expires automatically after 3 months |
| 141 | +* The pause action can now be applied on a per-chain basis as well as a Superchain-wide basis |
| 142 | + |
| 143 | +### Go 1.23 support in Cannon |
| 144 | + |
| 145 | +Cannon has been updated to support Go 1.23, allowing the OP Stack to benefit from upstream changes in go-ethereum. |
| 146 | + |
| 147 | +### `MAX_GAS_LIMIT` increases |
| 148 | + |
| 149 | +The `MAX_GAS_LIMIT` variable in the `SystemConfig` contract is being updated from 200m gas to 500m gas. |
| 150 | + |
| 151 | +### Security reviews |
| 152 | + |
| 153 | +* Changes to the bridge contracts were audited via a Cantina contest with no Medium+ severity issues found |
| 154 | +* Upgrade 16 as a whole was audited by Spearbit with no Medium+ severity issues found |
| 155 | + |
0 commit comments