Arbitrum Nitro v3.12.2 Released with Docker Images and Bug Fixes

Offchain Labs has published Nitro v3.12.2 as a Docker image on Docker Hub, adding a transaction‑feed client example and fixing several bugs. The release includes a validator‑specific image with a split‑validation script and resolves head truncation, sequencer panic, and block deletion issues.

Arbitrum Nitro v3.12.2 Released with Docker Images and Bug Fixes

Offchain Labs has rolled out Arbitrum Nitro version 3.12.2, making the new release available as a Docker image on Docker Hub under the tag offchainlabs/nitro-node:v3.12.2-5f02f3f. The image comes with a pre‑configured entrypoint that sets default flags, notably "/usr/local/bin/nitro --validation.wasm.allowed-wasm-module-roots /home/user/nitro-legacy/machines,/home/user/target/machines", which should be replicated if the entrypoint is overridden.

For validators that do not use a split validation server—most validators in practice—Offchain Labs also provides a dedicated image, offchainlabs/nitro-node:v3.12.2-5f02f3f-validator. This variant replaces the entrypoint with the script /usr/local/bin/split-val-entry.sh, simplifying the setup for validator nodes.

A key addition in this release is a transaction‑feed client example implementation. The example, added in commit b8d83b7541e15c9d0fa8ae296470b518430200f9, demonstrates how developers can subscribe to transaction feeds, enabling real‑time monitoring and integration with off‑chain services.

The update also addresses several bugs that impacted node stability. Commit c9f1ccf374a12eb3d91c84e6f0178da6a8795848 fixes a head truncation issue that occurred when the chain diverged from a tail group. Another fix, in commit 498ce18fcba28eba8f0a6594ea95522b60c61ad2, ensures the sequencer can recover from a panic while processing a delayed message, retrying after a minute. Finally, commit 5f02f3f03076343061f167e81b8e82ec5518064b restores recent blocks when a node is rolled back from 3.11.x to 3.12.x, preventing accidental data loss.

These improvements enhance both the developer experience and the resilience of the Nitro node. The Docker images make deployment straightforward, while the new client example and bug fixes reduce operational risk. Developers can review the full commit history and compare changes on GitHub via the v3.12.1…v3.12.2 comparison link.

Overall, Nitro v3.12.2 strengthens the Arbitrum ecosystem by providing a more robust, developer‑friendly node implementation that is easier to run in production environments and less prone to the edge‑case failures that previously surfaced.

Trust 88 Importance 66 Noise 0% Related symbol Informational material, not financial advice.