Optimism proposes Pectra-readiness maintenance for OP Stack chains

What happened

Optimism published Upgrade Proposal #12 to make OP Stack node software, protocol specifications, and L1 fault-proof contracts compatible with Ethereum Pectra.

What changed

A concrete maintenance payload and operator-upgrade requirement entered governance. The proposal identifies EIP-7702 transaction decoding and the EIP-7685 requestsHash header field as breaking inputs that OP Stack software must support.

What did not change

Within the February window this was a proposal, not evidence that every OP Stack chain or canonical bridge had completed the upgrade. The proposal says it does not change fee take, governor/servicer roles, ossified gas limits, or related authorization structures.

Confirmed

• The official proposal was published on February 25, 2025.
• It states that unmodified OP Stack chains could suffer a safe-head stall, sequencing-window expiry, and a large reorganization after Pectra activates on their L1.
• It covers node software, protocol specifications, and fault-proof contracts and anticipates no downtime if applied before the relevant L1 activation.

Still open

• Approval, execution, and chain-by-chain operator adoption were not established within the backfill window.
• The manifest does not receipt bridge-specific deployment state for Optimism or Base.

What it means for an advisor

• Require bridge diligence to verify Pectra-ready node and fault-proof deployments before treating the Optimism and Base canonical bridges as operationally unchanged.
• Keep current bridge approvals under review until implementation receipts, not merely governance approval, are documented.