
OP Stack Releases: Required Batcher Update Explained
Five OP Stack components were released together. The batcher update is labelled required and the supernode update recommended, without evidence of a live exploit or network-wide activation.
Custody, validators, service providers and network operations.

Five OP Stack components were released together. The batcher update is labelled required and the supernode update recommended, without evidence of a live exploit or network-wide activation.

Updated guidance pins client versions, Super Root RPC, SafeDB, and cutover order, while the governance vote and Sepolia and mainnet executions remained pending at the evidence cutoff.

OP Labs announced a support transition from Flashblocks to Subblocks for OP Enterprise. Existing migrations and support end points remained future and partly to be confirmed.

The CFTC approved a final whistleblower-award rule with a 30% presumption for awards of US$5 million or less, but Federal Register publication and effectiveness remained pending.

How to separate a proposal, approved change, software release, activation window and completed network transition.

A transparent look at the verbs, status labels and correction practices used across this publication.