Hedera has announced significant changes regarding its AccountBalanceQuery feature, which will be deprecated by July 2026. This decision is set to enhance the network’s performance as it scales, redirecting developers to utilize the Mirror Node REST API for balance queries.
The impending removal of AccountBalanceQuery is attributed to its direct impact on the consensus nodes, the backbone of Hedera’s transaction processing. Each call to AccountBalanceQuery invokes a consensus node, which can hinder its operational efficiency and impair its primary function of processing transactions. As the network continues to expand, the necessity of optimizing performance has become apparent, leading to this major architectural shift.
Beginning in May 2026, a gradual throttling of requests for the AccountBalanceQuery will take effect. Currently, the query operates at a rate of 40,000 requests per second (rps), a limit that will remain in place until the end of April. In May, this will be reduced to 20,000 rps, followed by a further cut to 10,000 rps in June. By July, all requests will fail as the feature is fully retired. High-volume applications are expected to notice the effects starting in May, marking a critical juncture for developers.
In lieu of the deprecated feature, Hedera encourages developers to transition to the Mirror Node API, which is specifically designed for high-throughput data queries without impacting consensus processing. The Hedera-hosted mirror node allows free access with defined throttle limits, while commercial providers can offer higher volume plans.
For developers yet to make the transition, the replacement for AccountBalanceQuery is already operational. By simply swapping the AccountBalanceQuery call for a REST call to the Hedera Mirror Node API at the balances endpoint, developers can continue their operations seamlessly. Additionally, token balances can be accessed through a separate accounts tokens endpoint. An official migration guide is available, detailing a five-step process to ensure a smooth transition, emphasizing the need for completion before May to avoid the throttling issues.
While the transition to the Mirror Node API is currently essential, future enhancements are in development. Block Nodes, based on Hedera Improvement Proposals (HIP) 1056 and 1081, aim to provide event-driven balance updates through Block Streams, integrating various data types into a single verifiable stream. However, these enhancements are still underway and are not available for immediate use in the current migration phase.
The deprecation of AccountBalanceQuery extends across all operational environments: mainnet, testnet, and previewnet, ensuring a uniform transition timeline for developers.
This significant change is part of a strategic shift within Hedera, aiming for greater scalability by delineating roles within its architecture. The consensus nodes will focus solely on transaction processing, while purpose-built infrastructures will manage data queries. This approach aligns with Hedera’s broader objectives of expanding enterprise partnerships, engaging with policy bodies, and enhancing EVM compatibility, all geared toward building a more scalable network.
As outlined by the Hedera development team, the countdown to the deprecation of AccountBalanceQuery is already in motion, with developers urged to act swiftly. Resources for migration are available through official documentation and the Hedera Discord channels, supporting developers in adapting to this essential change.
