Sb/pectra u12a update

pages/notices/pectra-changes.mdx

@@ -19,6 +19,14 @@ import { Steps, Callout } from 'nextra/components'
 
 # Preparing for Pectra breaking changes
 
+<Callout type="warning">
+  Please note that this notice page was updated March 11th, 2025. There was a bug found in previous op-node releases where the L1 Block's blob base fee (for the sake of computing the L1 fees) is calculated with pre-Prague=Cancun blob schedule parameters, instead of using the Prague parameters. This bug has been fixed in the latest release of op-node.
+
+  This is not a critical issue on any OP Sepolia chain. However, when L1 blob base fees rise to 100 Mwei or higher on Sepolia, there is a temporary liveness risk, because we'd be overcharge L1 fees. Essentially, our L1 cost computation now overcharges by an exponential of 1.5, BBF\_Cancun = `BBF_Prague^1.5` (where BBF=blob base fee).
+
+  You must update your Sepolia nodes to the latest release of op-node to avoid this issue. There are new instuctions in the node operator section to help you mitigate this issue.
+</Callout>
+
 This page outlines breaking changes related to the Ethereum Pectra (Prague-Electra) hard fork for chain operators and node operators on OP Stack chains. The OP Stack is dividing the Pectra upgrade into two parts:
 
 1.  **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're running a fault proof enabled chain, you will need to follow additional steps outlined below.
@@ -30,9 +38,10 @@ If you experience difficulty at any stage of this process, please reach out to [
   This page will be updated continuously with information on upgrade runbooks and timelines as they come. Here's the tentative L1 Pectra hard fork times per the ACDC that happened on Feb 6th:
 
   L1 Client testnet releases out by Feb 13 (ACDE):
-      *   Holesky slot: `1740434112` (Mon, Feb 24 at 21:55:12 UTC)
-      *   Sepolia slot: `1741159776` (Wed, Mar 5 at 07:29:36 UTC)
-      *   +30 day mainnet slot: `1744154711` (Tue, Apr 8 at 23:25:11 UTC)
+
+  *   Holesky slot: `1740434112` (Mon, Feb 24 at 21:55:12 UTC)
+  *   Sepolia slot: `1741159776` (Wed, Mar 5 at 07:29:36 UTC)
+  *   +30 day mainnet slot: `1744154711` (Tue, Apr 8 at 23:25:11 UTC)
 </Callout>
 
 ## What's included in Pectra?
@@ -61,47 +70,48 @@ Node operators will need to upgrade to the respective releases before the activa
   Full node operators, meaning those who are running op-geth with `gc-mode=full`, will need to reference the [`op-geth v1.101411.8`release notes](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101411.8) to handle an intermediate upgrade step before upgrading to the latest release. Archive node operators, `gc-mode=archive`, can skip this step and upgrade directly to the latest release.
 </Callout>
 
-*   `op-node` at [`v1.11.1`](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.11.1)
-*   `op-geth` at [`v1.101500.0`](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101500.0)
+*   `op-node` at [`v1.`]()
+*   `op-geth` at [`v1.`]()
 *   `op-reth` at [`v1.2.0`](https://github.com/paradigmxyz/reth/releases/tag/v1.2.0) also includes L1 Pectra support.
 
+For node operators of not included in the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), you will need to manually configure the activation. This can be done one of two ways:
+
+*   **Option 1:** Set the `pectrablobschedule` activation time in the `rollup.json` for `op-node`. You will still need to set the `pectrablobschedule` flag in `op-geth` if you use this option.
+*   **Option 2:** Set the activation time via overrides (CLI) in `op-node`. These will need to be set on `op-node` for the sequencer and all other nodes.
+
 ## For chain operators
 
 The following sections are how chain operators can prepare the first part of the OP Stack's Pectra L1 support. This ensures OP Stack chains do not break when the L1 Pectra upgrade activates. Every chain operator will need to:
 
 <Steps>
-
   ### Update your node binaries
 
-  Follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases. 
+  Follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases.
 
   ### Update your batcher and proposer
 
   Update your binaries to:
 
-  *   [`op-batcher/v1.11.4`](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.11.4).
+  *   [`op-batcher/v1.11.5`](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.11.5).
   *   [`op-proposer/v1.10.0`](https://github.com/ethereum-optimism/optimism/releases/tag/op-proposer%2Fv1.10.0).
-
 </Steps>
 
-
 ## For fault proof enabled chains
 
 <Callout type="info">
   The following instructions assume your chain is on the latest contract release `op-contracts/v1.8.0` and has Holocene activated.
 </Callout>
 
-All fault proof enabled chains (both permisionless and permissioned fault proof systems) need to update their `op-challenger` binary to [`op-challenger/v1.3.1`](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.3.1). 
+All fault proof enabled chains (both permisionless and permissioned fault proof systems) need to update their `op-challenger` binary to [`op-challenger/v1.3.1`](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.3.1).
 
-The following steps are to update your absolute prestate with new dispute game contracts. **This is absolutely necessary for chains running permissionless fault proofs.** For chains running the Fault Proof System with permissioned games you can skip this section because games will not be played out and the absolute prestate is not used. 
+The following steps are to update your absolute prestate with new dispute game contracts. **This is absolutely necessary for chains running permissionless fault proofs.** For chains running the Fault Proof System with permissioned games you can skip this section because games will not be played out and the absolute prestate is not used.
 
 The Pectra upgrade changes the derivation rules, permissionless fault proof chains need to upgrade the `op-program` version used in the fault proof system to support these changes. The `op-program` version used is specified via the `faultGameAbsolutePrestate` setting, deployed as part of `FaultDisputeGame` and `PermissionedDisputeGame` contracts.
 
 <Steps>
-
   ### Verify the new absolute prestate
 
-  The absolute prestate is generated with the [op-program/v1.5.0-rc.2](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.5.0-rc.2). You can use this new absolute prestate (`0x035ac388b5cb22acf52a2063cfde108d09b1888655d21f02f595f9c3ea6cbdcd`) for the following chains:
+  The absolute prestate is generated with the [op-program/v1.5.0-rc.4](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.5.0-rc.4). You can use this new absolute prestate (`0x0354eee87a1775d96afee8977ef6d5d6bd3612b256170952a01bf1051610ee01`) for the following chains:
 
   *   Sepolia: Base, OP, Metal, Mode, Zora, Ethernity, Unichain, Ink, Minato (Soneium)
   *   Mainnet: Base, OP, Orderly, Lyra, Metal, Mode, Zora, Lisk, Ethernity, Binary, Ink, Unichain, Soneium
@@ -115,18 +125,18 @@ The Pectra upgrade changes the derivation rules, permissionless fault proof chai
   You should expect the following output at the end of the command:
 
   ```shell
-  Cannon Absolute prestate hash: 
-  0x035ac388b5cb22acf52a2063cfde108d09b1888655d21f02f595f9c3ea6cbdcd
-  Cannon64 Absolute prestate hash: 
-  0x03a7d967025dc434a9ca65154acdb88a7b658147b9b049f0b2f5ecfb9179b0fe
-  CannonInterop Absolute prestate hash: 
-  0x0379d61de1833af6766f07b4ed931d85b3f6282508bbcbf9f4637398d97b61c1
+  Cannon Absolute prestate hash:
+  0x0354eee87a1775d96afee8977ef6d5d6bd3612b256170952a01bf1051610ee01
+  Cannon64 Absolute prestate hash:
+  0x03ee2917da962ec266b091f4b62121dc9682bb0db534633707325339f99ee405
+  CannonInterop Absolute prestate hash:
+  0x03673e05a48799e6613325a3f194114c0427d5889cefc8f423eed02dfb881f23
   ```
 
   ### Upload your new preimage file
 
-  During the previous step, you also generated the preimage of the absolute prestate, which is basically the op-program serialized into a binary file. You'll find that new file at `optimism/op-program/bin/prestate.bin.gz`. Rename that file to have the absolute prestate hash as the filename so it looks like `0x035ac388b5cb22acf52a2063cfde108d09b1888655d21f02f595f9c3ea6cbdcd.bin.gz`. 
-  
+  During the previous step, you also generated the preimage of the absolute prestate, which is basically the op-program serialized into a binary file. You'll find that new file at `optimism/op-program/bin/prestate.bin.gz`. Rename that file to have the absolute prestate hash as the filename so it looks like `0x0354eee87a1775d96afee8977ef6d5d6bd3612b256170952a01bf1051610ee01.bin.gz`.
+
   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.
 
   ### Deploy new dispute game contracts
@@ -137,7 +147,7 @@ The Pectra upgrade changes the derivation rules, permissionless fault proof chai
 
   You will then need to update the `DisputeGameFactory` to point to the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. You can utilize this [template](https://github.com/ethereum-optimism/superchain-ops/tree/main/tasks/sep/fp-recovery/005-set-game-implementation) to generate the transaction and validation script for this step. Before executing, you will need to update your op-challenger.
 
-  ### Execute the upgrade 
+  ### Execute the upgrade
 
   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.
 </Steps>

words.txt

@@ -173,6 +173,7 @@ inator
 INFLUXDBV
 influxdbv
 initcode
+instuctions
 IPCDISABLE
 ipcdisable
 ipcfile
@@ -238,9 +239,9 @@ NETRESTRICT
 netrestrict
 NETWORKID
 networkid
-nextra
 NEWPAYLOAD
 newpayload
+nextra
 NOCOMPACTION
 nocompaction
 NODEKEY
@@ -315,11 +316,12 @@ PRICELIMIT
 pricelimit
 productionize
 productionized
-Proxied
 Protip
+Proxied
 Proxyd
 proxyd
 Pyth
+Pyth's
 QRNG
 Quicknode
 quicknode
@@ -339,20 +341,21 @@ replayor
 reposts
 REQUIREDBLOCKS
 requiredblocks
-rpcs
 rollouts
 Rollups
 rollups
 Routescan
 rpckind
 RPCPREFIX
 rpcprefix
+rpcs
 RPGF
 Runbooks
 runbooks
 RWAs
 safedb
 Schnorr
+SEPOLIA
 Sepolia
 sepolia
 seqnr