We will be upgrading our Morph Mainnet and Hoodi Testnet infrastructure to morph-geth v2.2.6 and morph-node v0.6.3
https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.6 Per-block tx payload budget raised from 120KB to 720KB This limit is enforced in the binary, not via genesis/chain config. Nodes running older versions will reject or mishandle blocks assembled under the new limit, making this effectively a consensus-breaking change requiring all operators to upgrade.
Txpool blacklist feature removed The --txpool.blacklist flag and all associated RPC/storage logic have been deleted. Nodes with this flag in their startup configuration will likely fail to start or emit errors. Leftover eth/db/blacklist/ data in the database can be deleted manually but is otherwise harmless.
Auth WebSocket endpoint now requires JWT The authenticated Engine API WebSocket path now enforces JWT authentication, matching the existing HTTP behavior. Clients or tooling connecting to the Engine API WS endpoint without JWT will be rejected.
L1 Rollup authorization model replaced — staked Submitter role replaces sequencer-set authorization The Rollup contract now only authorizes active staked Submitters. bitmap/BLS/BatchSignatureInput inputs are removed. The former sequencer-set field in batch headers is written as zero after cutover. Historical ABI/selector decoding is preserved, but new submissions require the staked Submitter flow.
Batch public-input preimage change — sequencer public-input field zeroed The prover zeros the former sequencer public-input field after the cutover. Batch-header layout and public-input preimage structure remain the same, but the sequencer field value changes to zero.
Prover DA decode library switched from zstd-rs to morph-da-encoder The prover now uses morph-da-encoder for DA decoding instead of zstd-rs. Operators running the prover must ensure the new library dependency is present.
Challenge-handler migrated to remote-signer SDK (sign_v1) with active proof signer validation The challenge-handler now uses the remote-signer SDK sign_v1 interface and validates the active proof signer. Operators must configure the remote signer endpoint accordingly.