Fireblocks Wallet Pools route around stuck Ethereum nonce lanes

The launch did not stop at pools. Transaction Timeout and Account Traffic Control round out the reliability stack. Transaction Timeout targets the transaction that never confirms and never officially fails; it lets teams mark such items as FAILED before they reach the blockchain, so a pending queue stops waiting on a single transaction. Fireblocks said that pre-broadcast handling cuts the time teams spend babysitting pending transactions. Account Traffic Control adds a real-time monitoring layer, alerting operations teams within minutes, before a developing backlog cascades. Fireblocks describes the combined effect as moving operations from reactive firefighting to proactive monitoring.

Single-vault dependency has been a persistent vulnerability for institutions running high volumes. Fireblocks said it serves thousands of organizations across more than 150 blockchain networks, with BNY Mellon and Revolut among the named clients. The user base spans banks and payments processors, whose settlement flows cannot wait for a stuck batch to clear. Each vault carries its own nonce queue, so a client spanning many networks runs many queues at once, each a potential stall point. When one vault backs up, business lines stall; pooling the load cuts that single point of failure.

For competing custody providers such as BitGo and Copper, the release sets a new baseline for how vault software handles congested networks. Load balancing across redundant nodes is standard practice in traditional technology infrastructure, and applying that logic to nonce-aware vault management is the differentiation Fireblocks is selling.

The WALLET_POOL peer type appeared in the company's developer changelog in late July. For teams already building on the Fireblocks API, the integration follows a familiar pattern; the new abstraction layer sits on top of existing vault infrastructure.