Fireblocks, the digital asset infrastructure firm that secures trillions in transactions annually, has rolled out Wallet Pools, a feature that lets clients consolidate multiple vaults into unified pools. The system uses a health-tiered round-robin algorithm to route transactions, automatically avoiding stuck lanes and sending traffic through ones that are working.
How Wallet Pools actually work
On blockchains like Ethereum, transactions must be processed in a specific order determined by something called a nonce, essentially a sequential number assigned to each transaction from a given address. If transaction number 47 gets stuck, transactions 48 through infinity just sit there waiting. For a payments firm processing thousands of transactions daily, that’s an operational crisis.
Wallet Pools tackle this by grouping multiple vaults into a single transaction source. Instead of routing everything through one vault, the system distributes transactions across the pool. When one vault encounters a stuck transaction, the algorithm routes new transactions to healthy vaults in the pool.
The new WALLET_POOL peer type appeared in Fireblocks’ developer changelog in late July 2026. For teams already building on the Fireblocks API, integration follows a familiar pattern with a new abstraction layer sitting on top of existing vault infrastructure.
Two companion features round out the package
Wallet Pools didn’t arrive alone. Fireblocks simultaneously introduced Transaction Timeout and Account Traffic Control, two features that address different parts of the same reliability problem.
Transaction Timeout handles the transaction that never confirms but also never officially fails. With Transaction Timeout, delayed transactions can be marked as FAILED before they even hit the blockchain. Pre-broadcast failure handling means teams spend less time babysitting pending transactions.
Account Traffic Control functions as a real-time monitoring layer that sends alerts when vault health deteriorates, notifying operations teams within minutes. Together, these three features form a coherent reliability stack: Wallet Pools routes around problems, Transaction Timeout kills zombie transactions, and Account Traffic Control tells you something went wrong before it cascades.
Why institutions care about plumbing
Fireblocks serves thousands of organizations, including names like BNY Mellon and Revolut. These institutions process enormous transaction volumes across more than 150 blockchain networks. The dependency on single vaults has been a persistent vulnerability in institutional crypto operations. When one vault goes down or gets backed up, entire business lines can stall. Wallet Pools directly reduces that single-point-of-failure risk by distributing the operational load.
What this means for the competitive landscape
Account Traffic Control’s real-time alerting, combined with Wallet Pools’ automatic routing, moves the operational model from reactive firefighting to proactive monitoring. For competing infrastructure providers like Anchorage, BitGo, and Copper, this raises the bar. Load balancing across redundant nodes is standard practice in traditional tech infrastructure, but applying it specifically to crypto vault management with nonce-awareness is a meaningful product differentiation.