Arbitrum Nitro v3.1.2

This release is available as a Docker image on Docker Hub at offchainlabs/nitro-node:v3.1.2-309340a

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

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.1.2-309340a-validator which has the extra script /usr/local/bin/split-val-entry.sh as the entrypoint.

It's important that you only run the nitro node against trusted databases. If you want to use an untrusted database, you can first remove the wasm directory if it exists (it might be inside the a folder called nitro). Otherwise, the database may have malicious unvalidated code that can result in remote code execution. This is also mitigated by running the Arbitrum Nitro node inside docker.

What's Changed

This release fixes a crash in v3.1.1 for chains imported from Arbitrum Classic, i.e. Arbitrum One. For details on the v3.1.1 release, see the v3.1.1 release notes.

Internal Highlights

• Return false if nil is passed to IsNotExistError: #2616

Full Changelog: v3.1.1...v3.1.2