Arbitrum Nitro v3.12.4, dated November 9, 2026, adds an optional cap on pending conditional transactions and changes how its JSON-RPC interface handles required arguments. The release was reported on November 20, 2026. The changelog describes software changes, not an activated Ethereum protocol upgrade.
Conditional transactions and RPC handling
Node operators can set the hot-reloadable tx-pre-checker.max-pending-conditional-txs option to cap conditional transactions in flight. Its default value, 0, disables the cap. When a cap is set, the node rejects excess transactions with RPC error -32012. Two new metrics track pending conditional transactions and rejections caused by the cap.
JSON-RPC methods now reject null for required arguments, such as the transaction argument in eth_call. The release also includes a change intended to speed up JSON-RPC request decoding after large bursts of requests had stalled block production, along with tracer memory-management cleanup.
Operator image and earlier sequencer changes
The release lists Docker image offchainlabs/nitro-node:v3.12.4-960ca0a. Operators overriding its entrypoint need to preserve the default --validation.wasm.allowed-wasm-module-roots setting, which points to /home/user/nitro-legacy/machines,/home/user/target/machines. For validators running without a split validation server, the release instead specifies offchainlabs/nitro-node:v3.12.4-960ca0a-validator, whose entrypoint is /usr/local/bin/split-val-entry.sh.
The same release notes also include v3.12.3, dated October 26, 2026. That version added sequencer configuration options and pending-transaction metrics. Its listed behavior changes allow small transactions to overtake large ones after consecutive data-limited FIFO blocks, and reject same-sender, same-nonce transactions unless PGA is enabled and the tip is higher. The notes do not establish when any network deployed either version.