From 77de59891507e43de63db87fed5c3a0939f2efb0 Mon Sep 17 00:00:00 2001 From: tynes Date: Wed, 17 Apr 2024 02:25:41 +0000 Subject: [PATCH] deploy: 644e868b68195a5dfc6ae57e1d4ef6dddd340052 --- print.html | 23 +++++++++++++++++------ protocol/superchain-upgrades.html | 23 +++++++++++++++++------ searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 36 insertions(+), 14 deletions(-) diff --git a/print.html b/print.html index aa4d5e36e..cc303819d 100644 --- a/print.html +++ b/print.html @@ -4767,14 +4767,15 @@

Super
  • OP-Stack Protocol versions
  • Post-Bedrock Network upgrades -
  • Canyon
  • Delta
  • Ecotone
  • Fjord
  • + +

    Overview

    Superchain upgrades, also known as forks or hardforks, implement consensus-breaking changes.

    @@ -4946,6 +4947,16 @@

    Governance Proposal.

    Post-Bedrock Network upgrades

    +

    Activation Timestamps

    +

    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.

    +
    + + + + +
    Network UpgradeMainnet Upgrade TimestampSepolia Upgrade TimestampGoerli Upgrade Timestamp
    Canyon170499240116999812001699981200
    Delta170856000017032032001703116800
    Ecotone171037440117085348001707238800
    Fjordn/an/an/a
    +

    Regolith

    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 @@

    Regolith

    The execution engine specification specifies the L1 cost function difference.

    The Regolith upgrade uses a L2 block-timestamp activation-rule, and is specified in both the rollup-node (regolith_time) and execution engine (config.regolithTime).

    -

    Canyon

    +

    Canyon

    The Canyon upgrade contains the Shapella upgrade from L1 and some minor protocol fixes.

    + +

    Overview

    Superchain upgrades, also known as forks or hardforks, implement consensus-breaking changes.

    @@ -394,6 +395,16 @@

    Governance Proposal.

    Post-Bedrock Network upgrades

    +

    Activation Timestamps

    +

    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.

    +
    + + + + +
    Network UpgradeMainnet Upgrade TimestampSepolia Upgrade TimestampGoerli Upgrade Timestamp
    Canyon170499240116999812001699981200
    Delta170856000017032032001703116800
    Ecotone171037440117085348001707238800
    Fjordn/an/an/a
    +

    Regolith

    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 @@ -416,7 +427,7 @@

    Regolith

    The execution engine specification specifies the L1 cost function difference.

    The Regolith upgrade uses a L2 block-timestamp activation-rule, and is specified in both the rollup-node (regolith_time) and execution engine (config.regolithTime).

    -

    Canyon

    +

    Canyon

    The Canyon upgrade contains the Shapella upgrade from L1 and some minor protocol fixes.