-
Notifications
You must be signed in to change notification settings - Fork 101
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
36 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4767,14 +4767,15 @@ <h1 id="superchain-upgrades"><a class="header" href="#superchain-upgrades">Super | |
<li><a href="protocol/superchain-upgrades.html#op-stack-protocol-versions">OP-Stack Protocol versions</a></li> | ||
<li><a href="protocol/superchain-upgrades.html#post-bedrock-network-upgrades">Post-Bedrock Network upgrades</a> | ||
<ul> | ||
<li><a href="protocol/superchain-upgrades.html#activation-timestamps">Activation Timestamps</a></li> | ||
<li><a href="protocol/superchain-upgrades.html#regolith">Regolith</a></li> | ||
</ul> | ||
</li> | ||
<li><a href="protocol/superchain-upgrades.html#canyon">Canyon</a></li> | ||
<li><a href="protocol/superchain-upgrades.html#delta">Delta</a></li> | ||
<li><a href="protocol/superchain-upgrades.html#ecotone">Ecotone</a></li> | ||
<li><a href="protocol/superchain-upgrades.html#fjord">Fjord</a></li> | ||
</ul> | ||
</li> | ||
</ul> | ||
<!-- END doctoc generated TOC please keep comment here to allow auto update --> | ||
<h2 id="overview-14"><a class="header" href="#overview-14">Overview</a></h2> | ||
<p>Superchain upgrades, also known as forks or hardforks, implement consensus-breaking changes.</p> | ||
|
@@ -4946,6 +4947,16 @@ <h2 id="op-stack-protocol-versions"><a class="header" href="#op-stack-protocol-v | |
<a href="https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669">Governance Proposal</a>.</li> | ||
</ul> | ||
<h2 id="post-bedrock-network-upgrades"><a class="header" href="#post-bedrock-network-upgrades">Post-Bedrock Network upgrades</a></h2> | ||
<h3 id="activation-timestamps"><a class="header" href="#activation-timestamps">Activation Timestamps</a></h3> | ||
<p>Governance approves all network upgrades & the time at which the upgrade activates. The approved governance | ||
proposal is the canonoical document for the timestamp; however, the timestamps are replicated here for ease of use.</p> | ||
<div class="table-wrapper"><table><thead><tr><th>Network Upgrade</th><th>Mainnet Upgrade Timestamp</th><th>Sepolia Upgrade Timestamp</th><th>Goerli Upgrade Timestamp</th></tr></thead><tbody> | ||
<tr><td>Canyon</td><td>1704992401</td><td>1699981200</td><td>1699981200</td></tr> | ||
<tr><td>Delta</td><td>1708560000</td><td>1703203200</td><td>1703116800</td></tr> | ||
<tr><td>Ecotone</td><td>1710374401</td><td>1708534800</td><td>1707238800</td></tr> | ||
<tr><td>Fjord</td><td>n/a</td><td>n/a</td><td>n/a</td></tr> | ||
</tbody></table> | ||
</div> | ||
<h3 id="regolith"><a class="header" href="#regolith">Regolith</a></h3> | ||
<p>The Regolith upgrade, named after a material best described as "deposited dust on top of a layer of bedrock", | ||
implements minor changes to deposit processing, based on reports of the Sherlock Audit-contest and findings in | ||
|
@@ -4968,7 +4979,7 @@ <h3 id="regolith"><a class="header" href="#regolith">Regolith</a></h3> | |
The <a href="protocol/exec-engine.html">execution engine specification</a> specifies the L1 cost function difference.</p> | ||
<p>The Regolith upgrade uses a <em>L2 block-timestamp</em> activation-rule, and is specified in both the | ||
rollup-node (<code>regolith_time</code>) and execution engine (<code>config.regolithTime</code>).</p> | ||
<h2 id="canyon"><a class="header" href="#canyon">Canyon</a></h2> | ||
<h3 id="canyon"><a class="header" href="#canyon">Canyon</a></h3> | ||
<p>The Canyon upgrade contains the Shapella upgrade from L1 and some minor protocol fixes.</p> | ||
<ul> | ||
<li>Shapella Upgrade | ||
|
@@ -4993,10 +5004,10 @@ <h2 id="canyon"><a class="header" href="#canyon">Canyon</a></h2> | |
<p>The Canyon upgrade uses a <em>L2 block-timestamp</em> activation-rule, and is specified in both the | ||
rollup-node (<code>canyon_time</code>) and execution engine (<code>config.canyonTime</code>). Shanghai time in the | ||
execution engine should be set to the same time as the Canyon time.</p> | ||
<h2 id="delta"><a class="header" href="#delta">Delta</a></h2> | ||
<h3 id="delta"><a class="header" href="#delta">Delta</a></h3> | ||
<p>The Delta upgrade consists of a single consensus-layer feature: <a href="protocol/span-batches.html">Span Batches</a>.</p> | ||
<p>The Delta upgrade uses a <em>L2 block-timestamp</em> activation-rule, and is specified only in the rollup-node (<code>delta_time</code>).</p> | ||
<h2 id="ecotone-1"><a class="header" href="#ecotone-1">Ecotone</a></h2> | ||
<h3 id="ecotone-1"><a class="header" href="#ecotone-1">Ecotone</a></h3> | ||
<p>The Ecotone upgrade contains the Dencun upgrade from L1, and adopts EIP-4844 blobs for data-availability.</p> | ||
<p>Dencun Upgrade:</p> | ||
<ul> | ||
|
@@ -5039,7 +5050,7 @@ <h2 id="ecotone-1"><a class="header" href="#ecotone-1">Ecotone</a></h2> | |
<li>Auto-upgrading and extension of the <a href="protocol/deposits.html#ecotone-l1block-upgrade">L1 Attributes Predeployed Contract</a> | ||
(also known as <code>L1Block</code> predeploy)</li> | ||
</ul> | ||
<h2 id="fjord"><a class="header" href="#fjord">Fjord</a></h2> | ||
<h3 id="fjord"><a class="header" href="#fjord">Fjord</a></h3> | ||
<p>Name of the next upgrade after Ecotone. Placeholder for development coordination.</p> | ||
<div style="break-before: page; page-break-before: always;"></div><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/dist/katex.min.css"> | ||
<h1 id="system-config"><a class="header" href="#system-config">System Config</a></h1> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.