
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.
Reporting that separates proposals, releases, activations and confirmed outcomes. Every item carries a publication date, review context and internal reading path.

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.

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.

Bitcoin records confirm a roughly 4,000-BTC Liquid-related peg-out sequence. Later statements described a security incident and pause, while actor, cause, final loss, recovery, and India impact remained unresolved.

An off-chain Aave vote closed in favor of bounded delegated risk roles for V4 on Ethereum and Avalanche, but the required Security Council execution was not established.

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