From 27341844dc95a808e923d869550ddffc7eceecc9 Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 21 Jan 2025 16:57:22 -0800 Subject: [PATCH 1/8] adding pectra notice draft --- next-env.d.ts | 2 +- pages/builders/notices/_meta.json | 1 + pages/builders/notices/pectra-changes.mdx | 63 +++++++++++++++++++++++ 3 files changed, 65 insertions(+), 1 deletion(-) create mode 100644 pages/builders/notices/pectra-changes.mdx diff --git a/next-env.d.ts b/next-env.d.ts index a4a7b3f5c..4f11a03dc 100644 --- a/next-env.d.ts +++ b/next-env.d.ts @@ -2,4 +2,4 @@ /// // NOTE: This file should not be edited -// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information. +// see https://nextjs.org/docs/basic-features/typescript for more information. diff --git a/pages/builders/notices/_meta.json b/pages/builders/notices/_meta.json index 4b21e6372..c1db74fd1 100644 --- a/pages/builders/notices/_meta.json +++ b/pages/builders/notices/_meta.json @@ -1,4 +1,5 @@ { + "pectra-changes": "Preparing for Pectra breaking changes", "holocene-changes": "Preparing for Holocene breaking changes", "sdk-deprecation": "Preparing for Optimism SDK deprecation" } diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/builders/notices/pectra-changes.mdx new file mode 100644 index 000000000..cb582ed4f --- /dev/null +++ b/pages/builders/notices/pectra-changes.mdx @@ -0,0 +1,63 @@ +--- +title: Preparing for Pectra Breaking Changes +lang: en-US +description: Learn how to prepare for Pectra upgrade breaking changes. +--- + +import { Steps, Callout } from 'nextra/components' + +# Preparing for Pectra breaking changes + +This page outlines breaking changes related to the Ethereum Pectra (Prague-Electra) hard fork for chain operators and node operators on OP Stack chains. +If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). + + + * This page will be updated continuously with information on upgrade runbooks and timelines as they come. + * The Pectra upgrade for Holocene L1 proposed activation is on **Wed Feb 12**. + * The Pectra upgrade for Sepolia L1 proposed activation is on **Wed Feb 19**. + * The Pectra upgrade for Ethereum L1 will be activated in **March**. + + +## What's included in Pectra? + +Pectra contains a variety of EIPs, some of which apply to the OP Stack; others do not. The following EIPs are included in Pectra as outlined in the [Pectra Devnet 5 notes](https://notes.ethereum.org/@ethpandaops/pectra-devnet-5): + +* [EIP-2537: Precompile for BLS12-381 curve operations](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-2537.md) +* [EIP-2935: Save historical block hashes in state](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-2935.md) +* [EIP-6110: Supply validator deposits on chain](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-6110.md) +* [EIP-7002: Execution layer triggerable withdrawals](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7002.md) +* [EIP-7251: Increase the MAX_EFFECTIVE_BALANCE](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) +* [EIP-7549: Move committee index outside Attestation](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) +* [EIP-7623: Increase calldata cost ](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7623.md) +* [EIP-7685: General purpose execution layer requests](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7685.md) +* [EIP-7691: Blob throughput increase](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7691.md) +* [EIP-7702: Set EOA account code](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7702.md) +* [EIP-7840: Add blob schedule to EL config files ](https://github.com/ethereum/EIPs/pull/9129) + +## For chain operators + +The OP Stack is approaching the Pectra upgrade in two parts: + +1. Make the necessary upgrades to make sure OP Stack chains do not break when the L1 pectra upgrade activates +2. Upgrade OP Stack chains to support Pectra's new features that apply to L2s + +### For fault proof enabled chains + + + +## For node operators + +Node operators will need to upgrade to the respective releases before the activation dates. + +These following steps are necessary for every node operator: + + + ### Update to the latest release + + * [`op-node` at ``]() + * [`op-geth` at ``]() + + ### Verify Your Configuration + + + From d229281b6732200ce4f330c82c0886a9d9df54b0 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 24 Jan 2025 16:35:37 -0800 Subject: [PATCH 2/8] updating the pectra notice page --- pages/builders/notices/pectra-changes.mdx | 92 ++++++++++++++++++----- 1 file changed, 72 insertions(+), 20 deletions(-) diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/builders/notices/pectra-changes.mdx index cb582ed4f..668ed8eba 100644 --- a/pages/builders/notices/pectra-changes.mdx +++ b/pages/builders/notices/pectra-changes.mdx @@ -12,38 +12,86 @@ This page outlines breaking changes related to the Ethereum Pectra (Prague-Elect If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). - * This page will be updated continuously with information on upgrade runbooks and timelines as they come. - * The Pectra upgrade for Holocene L1 proposed activation is on **Wed Feb 12**. - * The Pectra upgrade for Sepolia L1 proposed activation is on **Wed Feb 19**. - * The Pectra upgrade for Ethereum L1 will be activated in **March**. + * This page will be updated continuously with information on upgrade runbooks and timelines as they come. + * The Pectra upgrade for Holocene L1 proposed activation is on **Wed Feb 12**. + * The Pectra upgrade for Sepolia L1 proposed activation is on **Wed Feb 19**. + * The Pectra upgrade for Ethereum L1 will be activated in **March**. ## What's included in Pectra? Pectra contains a variety of EIPs, some of which apply to the OP Stack; others do not. The following EIPs are included in Pectra as outlined in the [Pectra Devnet 5 notes](https://notes.ethereum.org/@ethpandaops/pectra-devnet-5): -* [EIP-2537: Precompile for BLS12-381 curve operations](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-2537.md) -* [EIP-2935: Save historical block hashes in state](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-2935.md) -* [EIP-6110: Supply validator deposits on chain](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-6110.md) -* [EIP-7002: Execution layer triggerable withdrawals](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7002.md) -* [EIP-7251: Increase the MAX_EFFECTIVE_BALANCE](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) -* [EIP-7549: Move committee index outside Attestation](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) -* [EIP-7623: Increase calldata cost ](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7623.md) -* [EIP-7685: General purpose execution layer requests](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7685.md) -* [EIP-7691: Blob throughput increase](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7691.md) -* [EIP-7702: Set EOA account code](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7702.md) -* [EIP-7840: Add blob schedule to EL config files ](https://github.com/ethereum/EIPs/pull/9129) +* [EIP-2537: Precompile for BLS12-381 curve operations](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-2537.md) +* [EIP-2935: Save historical block hashes in state](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-2935.md) +* [EIP-6110: Supply validator deposits on chain](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-6110.md) +* [EIP-7002: Execution layer triggerable withdrawals](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7002.md) +* [EIP-7251: Increase the MAX\_EFFECTIVE\_BALANCE](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) +* [EIP-7549: Move committee index outside Attestation](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) +* [EIP-7623: Increase calldata cost ](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7623.md) +* [EIP-7685: General purpose execution layer requests](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7685.md) +* [EIP-7691: Blob throughput increase](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7691.md) +* [EIP-7702: Set EOA account code](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7702.md) +* [EIP-7840: Add blob schedule to EL config files ](https://github.com/ethereum/EIPs/pull/9129) ## For chain operators The OP Stack is approaching the Pectra upgrade in two parts: -1. Make the necessary upgrades to make sure OP Stack chains do not break when the L1 pectra upgrade activates -2. Upgrade OP Stack chains to support Pectra's new features that apply to L2s +1. Make the necessary upgrades to make sure OP Stack chains do not break when the L1 pectra upgrade activates. +2. Upgrade OP Stack chains to support Pectra's new features that apply to L2s. + +For the first part, we will be releasing a new versions of the OP Stack that includes the necessary changes to make sure OP Stack chains do not break when the L1 pectra upgrade activates. It is essential for chain operators and the nodes on your network to upgrade to these latest versions. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. + +For the second part, we will be implementing all the features of Pectra that apply to L2s. We will be releasing a new version of the OP Stack that includes these features. We will provide more information on this part of the upgrade as when the engineering work is complete. + +These following steps are necessary for every chain operator: + + + ### Update to the latest releases + + * `op-node` at `vTBD` + * `op-geth` at `vTBD` + * `op-batcher` at `vTBD` + + ### Verify Your Configuration + + Make the following checks to verify that your node is properly configured. + + * `op-node` and `op-geth` will log their configurations at startup + * Check that the Pectra time is set to `activation-timestamp` in the op-node startup logs + * Check that the Pectra time is set to `activation-timestamp` in the op-geth startup logs + ### For fault proof enabled chains +Since the Pectra upgrade changes the derivation rules, the version of `op-program` used in the fault proof system has to be upgraded to a version that supports these changes. The `op-program` version used is specified via the `faultGameAbsolutePrestate` setting, deployed as part of `FaultDisputeGame` and `PermissionedDisputeGame` contracts. + + + ### Make sure the Superchain Registry is up to date + + The new `op-program` release will pull the configurations from the [superchain-registry](https://github.com/ethereum-optimism/superchain-registry). This is important because the op-challenger uses the `op-program` and it needs to be aware of your chain's configuration. If you are running a chain that is not in the superchain-registry, please open a PR to add your chain to the superchain-registry. + + ### Generate a new absolute prestate + + Once we have a finalized release of the `op-program`, we will provide a release tag for you to use to generate the absolute prestate. You will check out that release tag in the monorepo and run the `make reproducible-prestate` [command](https://github.com/ethereum-optimism/optimism/blob/80eff009a352c4e74ec8fb41a6bdb2a5778f3075/Makefile#L133-L135) to generate the absolute prestate. + + ### Deploy new dispute game contracts + + You will then take the absolute prestate and deploy new `FaultDisputeGame` and `PermissionedDisputeGame` contracts with that value. + + ### Update the DisputeGameFactory + + You will then need to update the `DisputeGameFactory` to use the point to the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. We will provide an upgrade task and script to facilitate this upgrade. + ### Update your op-challenger + + Finally you will need to update your `op-challenger` to the new release version that will be provided soon. + + +### For OP Stack forks + +We are working on a PR that will include the ability to sync L1 after the pectra upgrade. The commits from the PR will need to be applied to your chain before Pectra goes live on L1. We will provide a link to the PR after it is complete. ## For node operators @@ -54,10 +102,14 @@ These following steps are necessary for every node operator: ### Update to the latest release - * [`op-node` at ``]() - * [`op-geth` at ``]() + * `op-node` at `vTBD` + * `op-geth` at `vTBD` ### Verify Your Configuration - + Make the following checks to verify that your node is properly configured. + + * `op-node` and `op-geth` will log their configurations at startup + * Check that the Pectra time is set to `activation-timestamp` in the op-node startup logs + * Check that the Pectra time is set to `activation-timestamp` in the op-geth startup logs From 32c34d4f9ecdee1ed5b4dce50ec382a6b1ea142e Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 24 Jan 2025 16:37:21 -0800 Subject: [PATCH 3/8] adding tracking issue --- pages/builders/notices/pectra-changes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/builders/notices/pectra-changes.mdx index 668ed8eba..33d3e2de2 100644 --- a/pages/builders/notices/pectra-changes.mdx +++ b/pages/builders/notices/pectra-changes.mdx @@ -43,7 +43,7 @@ The OP Stack is approaching the Pectra upgrade in two parts: For the first part, we will be releasing a new versions of the OP Stack that includes the necessary changes to make sure OP Stack chains do not break when the L1 pectra upgrade activates. It is essential for chain operators and the nodes on your network to upgrade to these latest versions. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. -For the second part, we will be implementing all the features of Pectra that apply to L2s. We will be releasing a new version of the OP Stack that includes these features. We will provide more information on this part of the upgrade as when the engineering work is complete. +For the second part, we will be implementing all the features of Pectra that apply to L2s. We will be releasing a new version of the OP Stack that includes these features. We will provide more information on this part of the upgrade as when the engineering work is complete. The spec work is being tracked in this [issue](https://github.com/ethereum-optimism/specs/issues/499). These following steps are necessary for every chain operator: From 304d29c0a9b1d2e057a2a7d4e15eae6a4e475da4 Mon Sep 17 00:00:00 2001 From: soyboy <85043086+sbvegan@users.noreply.github.com> Date: Fri, 24 Jan 2025 16:43:31 -0800 Subject: [PATCH 4/8] Apply suggestions from code review Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/builders/notices/pectra-changes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/builders/notices/pectra-changes.mdx index 33d3e2de2..2ce67a38e 100644 --- a/pages/builders/notices/pectra-changes.mdx +++ b/pages/builders/notices/pectra-changes.mdx @@ -27,7 +27,7 @@ Pectra contains a variety of EIPs, some of which apply to the OP Stack; others d * [EIP-6110: Supply validator deposits on chain](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-6110.md) * [EIP-7002: Execution layer triggerable withdrawals](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7002.md) * [EIP-7251: Increase the MAX\_EFFECTIVE\_BALANCE](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) -* [EIP-7549: Move committee index outside Attestation](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) +* [EIP-7549: Move committee index outside Attestation](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7549.md) * [EIP-7623: Increase calldata cost ](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7623.md) * [EIP-7685: General purpose execution layer requests](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7685.md) * [EIP-7691: Blob throughput increase](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7691.md) From 5e1f1703ceac5c59024d1a03fae9b99dc30b4ae9 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 24 Jan 2025 16:42:26 -0800 Subject: [PATCH 5/8] fixing some linter issues --- pages/builders/notices/pectra-changes.mdx | 10 ++++---- pages/stack/fault-proofs/mips.mdx | 2 +- pages/stack/interop/op-supervisor.mdx | 29 ++++++++++++----------- words.txt | 5 ++++ 4 files changed, 26 insertions(+), 20 deletions(-) diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/builders/notices/pectra-changes.mdx index 2ce67a38e..09f8b340c 100644 --- a/pages/builders/notices/pectra-changes.mdx +++ b/pages/builders/notices/pectra-changes.mdx @@ -76,15 +76,15 @@ Since the Pectra upgrade changes the derivation rules, the version of `op-progra Once we have a finalized release of the `op-program`, we will provide a release tag for you to use to generate the absolute prestate. You will check out that release tag in the monorepo and run the `make reproducible-prestate` [command](https://github.com/ethereum-optimism/optimism/blob/80eff009a352c4e74ec8fb41a6bdb2a5778f3075/Makefile#L133-L135) to generate the absolute prestate. - ### Deploy new dispute game contracts + ### Deploy new dispute game contracts - You will then take the absolute prestate and deploy new `FaultDisputeGame` and `PermissionedDisputeGame` contracts with that value. - - ### Update the DisputeGameFactory + You will then take the absolute prestate and deploy new `FaultDisputeGame` and `PermissionedDisputeGame` contracts with that value. + + ### Update the DisputeGameFactory You will then need to update the `DisputeGameFactory` to use the point to the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. We will provide an upgrade task and script to facilitate this upgrade. - ### Update your op-challenger + ### Update your op-challenger Finally you will need to update your `op-challenger` to the new release version that will be provided soon. diff --git a/pages/stack/fault-proofs/mips.mdx b/pages/stack/fault-proofs/mips.mdx index 987027520..3de221a6c 100644 --- a/pages/stack/fault-proofs/mips.mdx +++ b/pages/stack/fault-proofs/mips.mdx @@ -78,7 +78,7 @@ This value is derived from the `exitCode` and `exited` values, and can be: * Unfinished (3) The reason for adding the VM status to the state hash is to communicate to the dispute game whether the VM determined the proposed output root was valid or not. -This in turn prevents a user from disputing an output root during a dispute game, while providng the state hash from a cannon trace that actually proves the output root is valid. +This in turn prevents a user from disputing an output root during a dispute game, while providing the state hash from a cannon trace that actually proves the output root is valid. ### Memory proofs diff --git a/pages/stack/interop/op-supervisor.mdx b/pages/stack/interop/op-supervisor.mdx index 9f7dfd835..4a3af2c43 100644 --- a/pages/stack/interop/op-supervisor.mdx +++ b/pages/stack/interop/op-supervisor.mdx @@ -11,14 +11,15 @@ import { InteropCallout } from '@/components/WipCallout' # OP-Supervisor -OP-Supervisor is a service that verifies cross-chain messages and manages interoperability between chains in the OP Stack. +OP-Supervisor is a service that verifies cross-chain messages and manages interoperability between chains in the OP Stack. The main information it contains about other blockchains is: -- Log entries, which could be [initiating messages](./explainer#how-messages-get-from-one-chain-to-the-other) for cross-domain messages. -- Blockchain heads, which are the latest blocks at various levels of confidence and safety: - - Unsafe (the latest block available through the gossip protocol) - - Local-safe (the latest block written to L1) - - Cross-safe (the latest block written to L1, and for which all the dependencies are written to L1) - - Finalized (the latest block written to L1, and that L1 block is safe from reorgs) + +* Log entries, which could be [initiating messages](./explainer#how-messages-get-from-one-chain-to-the-other) for cross-domain messages. +* Blockchain heads, which are the latest blocks at various levels of confidence and safety: + * Unsafe (the latest block available through the gossip protocol) + * Local-safe (the latest block written to L1) + * Cross-safe (the latest block written to L1, and for which all the dependencies are written to L1) + * Finalized (the latest block written to L1, and that L1 block is safe from reorgs) ```mermaid @@ -51,14 +52,14 @@ To do this, OP-Supervisor has to have RPC access to all the chains in the depend ## How other components use OP-Supervisor -- The execution client (typically `op-geth`) queries `op-supervisor` during block-building to verify if a message is sufficiently safe to include. - To do this, the execution client looks at every executing message and queries `op-supervisor` to see if there is a corresponding initiating message. +* The execution client (typically `op-geth`) queries `op-supervisor` during block-building to verify if a message is sufficiently safe to include. + To do this, the execution client looks at every executing message and queries `op-supervisor` to see if there is a corresponding initiating message. -- `op-node` queries cross-chain safety information and coordinates safety updates between OP stack nodes and `op-supervisor`. It uses the API provided by `op-supervisor` to: - - Retrieve the unsafe, local-safe, cross-safe, and finalized heads for other chains. - - Update the unsafe, local-safe, and finalized heads for its own chain. - - Attempt to promote blocks in its own chain to cross-safe status. - - Attempt to finalize L2 blocks based on L1 finality. +* `op-node` queries cross-chain safety information and coordinates safety updates between OP stack nodes and `op-supervisor`. It uses the API provided by `op-supervisor` to: + * Retrieve the unsafe, local-safe, cross-safe, and finalized heads for other chains. + * Update the unsafe, local-safe, and finalized heads for its own chain. + * Attempt to promote blocks in its own chain to cross-safe status. + * Attempt to finalize L2 blocks based on L1 finality. ### API diff --git a/words.txt b/words.txt index b660cb459..3d65e7399 100644 --- a/words.txt +++ b/words.txt @@ -89,6 +89,7 @@ Drand dripcheck Drippie Eigen +EIPs ENABLEDEPRECATEDPERSONAL enabledeprecatedpersonal enginekind @@ -250,6 +251,9 @@ opstack Pausability pausable pcscdpath +Pectra +pectra +Pectra's Peerstore peerstore peerstores @@ -377,6 +381,7 @@ thirdweb threadcreate tility timeseries +triggerable trustlessly trustrpc txfeecap From 3d945ffb6278434b8531f23557e88cb9e457d508 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 24 Jan 2025 16:47:24 -0800 Subject: [PATCH 6/8] linter issue in the notice page --- pages/builders/notices.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/builders/notices.mdx b/pages/builders/notices.mdx index 5ca3a4b7f..746de9e0f 100644 --- a/pages/builders/notices.mdx +++ b/pages/builders/notices.mdx @@ -11,6 +11,8 @@ import { Card, Cards } from 'nextra/components' Documentation covering Sdk Deprecation in the Notices section of the OP Stack ecosystem. + + From d79df697ba9bd55c3a33a74cf89986959bc8430c Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 24 Jan 2025 16:49:22 -0800 Subject: [PATCH 7/8] updating spell check --- words.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/words.txt b/words.txt index 558166449..d17d59bbc 100644 --- a/words.txt +++ b/words.txt @@ -305,7 +305,6 @@ pricelimit productionize productionized Protip -providng Proxied Proxyd proxyd @@ -378,6 +377,7 @@ Superchain superchain Superchain's Superchainerc +superchainerc Superchains Superscan Supersim From 34b7a97b67e9b4178f13409cc2f1216fcdc0604b Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 24 Jan 2025 16:52:40 -0800 Subject: [PATCH 8/8] removing padding --- pages/builders/notices/pectra-changes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/builders/notices/pectra-changes.mdx index 09f8b340c..b763c8ac3 100644 --- a/pages/builders/notices/pectra-changes.mdx +++ b/pages/builders/notices/pectra-changes.mdx @@ -28,11 +28,11 @@ Pectra contains a variety of EIPs, some of which apply to the OP Stack; others d * [EIP-7002: Execution layer triggerable withdrawals](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7002.md) * [EIP-7251: Increase the MAX\_EFFECTIVE\_BALANCE](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7251.md) * [EIP-7549: Move committee index outside Attestation](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7549.md) -* [EIP-7623: Increase calldata cost ](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7623.md) +* [EIP-7623: Increase calldata cost](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7623.md) * [EIP-7685: General purpose execution layer requests](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7685.md) * [EIP-7691: Blob throughput increase](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7691.md) * [EIP-7702: Set EOA account code](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7702.md) -* [EIP-7840: Add blob schedule to EL config files ](https://github.com/ethereum/EIPs/pull/9129) +* [EIP-7840: Add blob schedule to EL config files](https://github.com/ethereum/EIPs/pull/9129) ## For chain operators