Nonce Gap

Overview

Meaning and scope

A nonce gap occurs in an account-based blockchain when a transaction with a higher sequence nonce is submitted while one or more lower nonces are missing or unconfirmed. Because transactions from an account are normally processed in order, later transactions can remain pending until the missing nonce is confirmed or replaced.

Mechanism and operation

Suppose an account’s next expected nonce is 10. Nodes may keep the higher transaction pending or reject it depending on local policy. A gap can block an entire queue of payouts or contract calls. The missing transaction may have been underpriced, sent only to one provider, or lost during an application restart. Recovery begins by comparing confirmed nonce, provider pending nonce, and the application’s local transaction records. The operator can rebroadcast the missing transaction, replace it with a higher-fee transaction using the same nonce, or submit a harmless self-transfer if protocol and policy allow.

Practical payment example

An EVM account broadcasts transactions with nonces 18 and 20 but never submits nonce 19. The higher-nonce transaction remains blocked until the missing nonce is resolved.

Operational checks

Concurrent workers should use a centralized nonce allocator or transaction manager. Assignments and hashes must be persisted before broadcast so a crash does not erase intent. Reorganizations and replacements can also change apparent sequence state. Monitoring should alert when pending duration or nonce divergence exceeds expected limits.

Distinctions and limits

A transaction using nonce 12 may be validly signed, but the network cannot execute it before transactions using nonces 10 and 11. Repeatedly sending higher nonces does not solve the underlying problem. Proper nonce management prevents one missing transaction from delaying many unrelated operations.

Related reading

Related definitions: nonce, confirmed nonce.