You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade execution timelines are being publicly tracked in this [release management project board](https://github.com/orgs/ethereum-optimism/projects/117/views/12).
24
-
25
-
* OP Sepolia, Ink Sepolia, and Minato Sepolia upgrades have already been executed.
26
-
* OP Mainnet, Soneium Mainnet, Ink Mainnet are expected to execute Upgrade 14 on **April 25th, 2025**.
27
-
* Base Mainnet is executing its upgrade on **April 25th, 2025**.
28
-
* Unichain Mainnet is executing its upgrade on **April 25th, 2025**.
29
-
* Other Optimism governed chains' upgrades will be tracked in the release management project board.
23
+
Upgrade execution timelines are being publicly tracked in this [release management project board](https://github.com/orgs/ethereum-optimism/projects/117/views/12).
24
+
25
+
*OP Sepolia, Ink Sepolia, and Minato Sepolia upgrades have already been executed.
26
+
*OP Mainnet, Soneium Mainnet, Ink Mainnet are expected to execute Upgrade 14 on **April 25th, 2025**.
27
+
*Base Mainnet is executing its upgrade on **April 25th, 2025**.
28
+
*Unichain Mainnet is executing its upgrade on **April 25th, 2025**.
29
+
*Other Optimism governed chains' upgrades will be tracked in the release management project board.
30
30
</Callout>
31
31
32
32
This page outlines changes related to the Upgrade 14 network upgrade for chain operators, node operators, and users of OP Stack chains. The upgrade proposal is available [here](https://gov.optimism.io/t/upgrade-proposal-14-mt-cannon-and-isthmus-l1-contracts/10123) and the governance vote is available [here](https://vote.optimism.io/).
@@ -37,10 +37,10 @@ If you experience difficulty at any stage of this process, please reach out to d
37
37
38
38
Upgrade 14 contains four main components:
39
39
40
-
***MT-Cannon**: An upgrade to the fault proof VM that supports the MIPS-64 instruction set and multi-threaded programs, removing memory constraints for the fault proof program.
41
-
***L2 Withdrawals Root in Block Header**: A change making it easier for chain operators to guarantee the security of fault proofs for chains in the Superchain as the number of chains scales.
42
-
***Operator Fee**: Introduction of the first phase of a mechanism addressing challenges in accurately pricing user fees when chains employ ZK proving, alt-DA, and custom gas tokens.
43
-
***L2 Pectra Support**: Support for Ethereum's Pectra hard fork features including BLS12-381 precompiles, historical block hashes on-chain, and set-code transactions (EIP-7702).
40
+
***MT-Cannon**: An upgrade to the fault proof VM that supports the MIPS-64 instruction set and multi-threaded programs, removing memory constraints for the fault proof program.
41
+
***L2 Withdrawals Root in Block Header**: A change making it easier for chain operators to guarantee the security of fault proofs for chains in the Superchain as the number of chains scales.
42
+
***Operator Fee**: Introduction of the first phase of a mechanism addressing challenges in accurately pricing user fees when chains employ ZK proving, alt-DA, and custom gas tokens.
43
+
***L2 Pectra Support**: Support for Ethereum's Pectra hard fork features including BLS12-381 precompiles, historical block hashes on-chain, and set-code transactions (EIP-7702).
44
44
45
45
## Technical details
46
46
@@ -50,37 +50,37 @@ MT-Cannon is an upgrade to [Cannon](/stack/fault-proofs/cannon), the [fault proo
50
50
51
51
Key changes:
52
52
53
-
* The emulated CPU architecture is now MIPS64 instead of MIPS32
54
-
* Registers now hold 64-bit values
55
-
* Memory address space is dramatically expanded
56
-
* New 64-bit specific instructions added for operations on 64-bit values
57
-
* Supports reading 8 bytes of data at a time from the pre-image oracle instead of 4
58
-
* Multithreading support
59
-
*Concurrency via multitasking
60
-
* VM now tracks ThreadState objects for each thread
61
-
* Thread-safe memory access enabled by Load Linked Word (ll) and Store Conditional Word (sc) instructions
62
-
* Extended syscall support for multi-threading
63
-
* Improved exception handling for unrecognized syscalls
53
+
*The emulated CPU architecture is now MIPS64 instead of MIPS32
54
+
* Registers now hold 64-bit values
55
+
* Memory address space is dramatically expanded
56
+
* New 64-bit specific instructions added for operations on 64-bit values
57
+
*Supports reading 8 bytes of data at a time from the pre-image oracle instead of 4
58
+
*Multithreading support
59
+
*Concurrency via multitasking
60
+
* VM now tracks ThreadState objects for each thread
61
+
* Thread-safe memory access enabled by Load Linked Word (ll) and Store Conditional Word (sc) instructions
62
+
* Extended syscall support for multi-threading
63
+
*Improved exception handling for unrecognized syscalls
64
64
65
65
After this upgrade, the on-chain implementation of the fault proof VM will be [MIPS64.sol](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/cannon/MIPS64.sol) instead of [MIPS.sol](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/cannon/MIPS.sol).
66
66
67
67
### L2 Withdrawals Root in Block Header
68
68
69
69
This component makes changes to:
70
70
71
-
* Add the storage root of the `L2ToL1MessagePasser` contract to the `ExecutionPayload`
72
-
* Add a new p2p gossip topic (`v4`) for Isthmus blocks
73
-
* Update the SSZ encoding & gossip to account for withdrawalsRoot
74
-
* Use the Isthmus timestamp activations
71
+
*Add the storage root of the `L2ToL1MessagePasser` contract to the `ExecutionPayload`
72
+
*Add a new p2p gossip topic (`v4`) for Isthmus blocks
73
+
*Update the SSZ encoding & gossip to account for withdrawalsRoot
74
+
*Use the Isthmus timestamp activations
75
75
76
76
These changes make it easier for chain operators to guarantee the security of fault proofs as the Superchain scales.
77
77
78
78
### Operator Fee
79
79
80
80
This introduces two new rollup operator configured scalars:
81
81
82
-
*`operatorFeeScalar`
83
-
*`operatorFeeConstant`
82
+
*`operatorFeeScalar`
83
+
*`operatorFeeConstant`
84
84
85
85
These parameters are factored into the fee calculation as follows:
86
86
@@ -96,22 +96,22 @@ The scalars will be updated via the SystemConfig L1 contract. A new fee vault, t
96
96
97
97
This component prepares for Ethereum's Pectra upgrade by including support for several EIPs:
***EIP-7685**: General purpose execution layer requests
114
+
* No requests currently applicable to OP Stack
115
115
116
116
### Absolute Prestate
117
117
@@ -123,14 +123,14 @@ If this proposal is accepted, multisig ceremonies will be coordinated to execute
123
123
124
124
For chain operators running fault-proof infrastructure, ensure you are running up-to-date versions of the following:
125
125
126
-
* op-challenger: `op-challenger/v1.3.3` (preferred) or at least `op-challenger/v1.3.1`
127
-
* op-dispute-mon: `op-dispute-mon/v1.4.0`
126
+
*op-challenger: `op-challenger/v1.3.3` (preferred) or at least `op-challenger/v1.3.1`
127
+
*op-dispute-mon: `op-dispute-mon/v1.4.0`
128
128
129
129
## For node operators
130
130
131
131
Node operators should ensure they are running an up-to-date version of op-node that can handle new events emitted from the `SystemConfig` contract:
132
132
133
-
* op-node: `op-node/v1.12.2`
133
+
*op-node: `op-node/v1.12.2`
134
134
135
135
## For bridges and users
136
136
@@ -142,11 +142,11 @@ Node operators should ensure they are running an up-to-date version of op-node t
142
142
143
143
The code for Upgrade 14 has undergone multiple audits:
144
144
145
-
***Spearbit**: Completed an audit of MT-Cannon. Details available [here](#).
146
-
***Coinbase Protocol Security**: Completed an audit of MT-Cannon. Details available [here](#).
145
+
***Spearbit**: Completed an audit of MT-Cannon. Details available [here](#).
146
+
***Coinbase Protocol Security**: Completed an audit of MT-Cannon. Details available [here](#).
147
147
148
148
## Emergency cancellation
149
149
150
150
If a critical security issue is discovered before upgrading, OP Labs will collaborate with the community to extensively communicate that the upgrade will no longer occur. The Optimism Foundation and Security Council will work to coordinate an emergency cancellation.
151
151
152
-
For more detailed information, please refer to the full upgrade proposal or reach out to developer support.
152
+
For more detailed information, please refer to the full upgrade proposal or reach out to developer support.
0 commit comments