On September 9, 2026, Offchain Labs released Nitro v3.11.4, the latest iteration of the Arbitrum Layer‑2 scaling solution. The update is distributed as Docker images on Docker Hub, making it easier for operators to deploy and maintain Nitro nodes.
The primary image, offchainlabs/nitro-node:v3.11.4-7d5ac27, includes default flags in its entrypoint that must be replicated if the entrypoint is overridden. For validators that do not use a split validation server—a common configuration—the team also published a specialized image, offchainlabs/nitro-node:v3.11.4-7d5ac27-validator, which uses a dedicated script as its entrypoint.
Beyond deployment convenience, the release introduces several functional improvements. The BoLD staker’s “Waiting for more batches to post next assertion” log now contains a reason field, providing clearer diagnostics for operators.
A critical bug fix addresses the decoding of parent chain headers on the Glamsterdam devnet‑8, specifically the blockAccessListHash (EIP‑7928) and slotNumber (EIP‑7843) fields. The updated logic now reproduces the canonical block hash, ensuring consistency between the L1 and L2 chains.
The update also enforces stricter limits on certain RPC calls. eth_getProof now rejects requests with more than 1,024 storage keys, preventing unbounded memory allocation and aligning Nitro’s behavior with upstream geth. Similarly, eth_feeHistory will reject requests that request more than 100 reward percentiles.
Finally, a regression in the batch poster that treated a reverted gas estimation as a successful estimate of zero gas has been corrected, improving the reliability of gas estimation for transaction batching.
Collectively, these changes enhance the stability, security, and observability of Nitro nodes, making it easier for validators and developers to run and interact with the Arbitrum network.
The release demonstrates Offchain Labs’ ongoing commitment to refining the Nitro codebase, addressing both operational concerns and protocol‑level bugs. As the Arbitrum ecosystem continues to grow, such incremental updates play a vital role in maintaining a robust and developer‑friendly infrastructure.