Important Note: Once a database is run with v3.10.x, the database cannot be used with v3.9.9.
This release is available as a Docker Image on Docker Hub at offchainlabs/nitro-node:v3.10.1-d7f07be
This Docker image specifies default flags in its entrypoint which should be replicated if you're overriding the entrypoint: /usr/local/bin/nitro --validation.wasm.allowed-wasm-module-roots /home/user/nitro-legacy/machines,/home/user/target/machines\
Special note: On Monday, May 18, 2026 at 17:00 UTC, ArbOS 60 will activate on the Arbitrum Sepolia chain. Arbitrum Sepolia node operators must upgrade to Nitro v3.10 ahead of this activation to continue syncing the chain. This is not a required upgrade for Arbitrum One at this time, the date for Arbitrum One ArboOS upgrade has not been set yet.
Sepolia validators can use block-validator.pending-upgrade-module root="0x7a9e6a77354888257a9989ce0b6bb39df5fedf222d453932933fdf7a489cbb57" to validate against the planned arbos-60 upgrade
Important for any chains still on ArbOS40:
- If you're running a validator without a split validation server (this will be true of most validators), you should instead use the image
offchainlabs/nitro-node:v3.10.1-d7f07be-validatorwhich has the extra script/usr/local/bin/split-val-entry.shas the default entrypoint (no need to override the default entrypoint). This will run bothv3.10.0andv3.7.6validator workers for you. - If you are using a split validator, you do not want to use
-validatorimage, you need to run a validator worker onv3.7.6as well as a worker forv3.10.1 - Arbitrum Chain SDK v0.25.2 (along with consensus_v51.1) is required for ArbOS51
Important for any chains that previously upgraded to ArbOS51 with consensus_v51:
- Validator should use configuration option
--node.block-validator.pending-upgrade-module-root=""to avoid performing unnecessary work trying to validateconsensus_v51.1.
v3.10.1 - 2026-05-12
Configuration
- Add
--execution.legacy-zero-base-fee-until <unix-ts>opt-in compatibility flag (default 0 = disabled). When set, restores the pre-v3.7 behavior of treating headers withArbOSFormatVersion <= 40andBaseFee == 0as non-arbitrum, for blocks with timestamp strictly less than the given value.
Added
- Include transaction-filterer binary in nitro-node and nitro-node-stripped Docker images.
Changed
- Set default
EnableETHCallFilterto false. - Update address-filter S3 hash list format
- Ensure genesis block is appropriately validated
Fixed
- Resolve BoLD Staking Bug That Attempts Self-Challenge