Technologie & IA
Arbitrum Nitro adds an optional cap on pending conditional transactions
Offchain Labs released Nitro 3.12.4 on November 19. Operators can limit how many conditional transactions a node has in flight. A separate notice proposes disabling their submission method on two public services on January 17, 2027.

A configurable limit for each node
Nitro 3.12.4, a version of the software that runs nodes on Arbitrum chains, was released on November 19, 2026, at 22:21 UTC. The corresponding changelog entry is dated November 9. One addition concerns transactions submitted with conditions. According to Arbitrum’s documentation, those conditions can involve a state value or a block or time bound that must still hold when the sequencer includes the transaction.
Nitro now lets operators set a maximum number of conditional transactions in flight on a node. The default value is zero, which leaves the cap off. The software can apply a change to that value without a restart. When a configured cap is reached, the node rejects additional conditional submissions. Each node operator makes that choice, and the release does not impose a new cap on every Arbitrum chain.
Two measurements for the queue
The release notes describe two metrics. A gauge shows how many conditional transactions are in flight. A separate counter records those that were rejected because the cap had been reached. The gauge shows a state at a given time. The counter tracks rejections caused by that setting. An operator can distinguish a temporary buildup of requests from a series of refusals caused by a limit they set.
The release also changes how Nitro handles JSON-RPC requests. The affected methods now reject a required argument passed as null. Offchain Labs also reports faster request decoding and a change in tracer memory management. The notes present these changes separately from the cap on conditional transactions. The cap applies to requests in flight on the node, while argument validation applies to the form of the affected requests.
A separate notice for Arbitrum One and Nova
In a notice published on November 18, Offchain Labs says it plans to disable the conditional submission method at the public sequencer endpoints for Arbitrum One and Arbitrum Nova on January 17, 2027. The company is taking feedback until December 18, 2026, and says feedback could change its decision or timeline. The notice keeps the standard submission method in place. The dates apply to the two public services named in the notice.
Independently operated Nitro sequencers can continue to support the method until the version that removes it, according to the documentation. Offchain Labs plans to identify that removal in the relevant release notes. The cap introduced in Nitro 3.12.4 is therefore for operators that still support conditional submissions. Enabling it on a node is a local setting, while removal at the two public endpoints follows the notice’s timeline.
