Hedera Deprecates AccountBalanceQuery as Migration Deadline Approaches in July

Hedera is set to retire the AccountBalanceQuery feature by July 2026. This move is part of broader efforts to reduce the burden on consensus nodes and improve the platform's scalability according to technical assessments. Developers have until July to complete the migration to the Mirror Node REST API, a more efficient solution for handling high-volume queries as reported.

The transition is being phased in with reduced throttling limits beginning in May. This gradual approach aims to give developers time to adjust their codebases and test their applications with the new API before the final deadline according to the platform's roadmap. The Mirror Node API offers improved performance and is already supported by limited throttling, making it a viable option for high-throughput operations as confirmed.

Hedera's decision follows a technical assessment that revealed AccountBalanceQuery calls were directly impacting the performance of consensus nodes. By shifting these queries to mirror nodes, the platform hopes to optimize transaction processing and improve overall system efficiency as detailed in the technical report.

Why Is Hedera Making This Change?

The AccountBalanceQuery feature places a direct load on consensus nodes, which are essential for validating transactions and maintaining the network's integrity according to platform documentation. As the platform scales, the need to offload such queries becomes more critical. Mirror nodes are designed to handle read-heavy operations, allowing consensus nodes to focus on processing transactions as described.

This change aligns with broader industry trends toward distributed architecture and optimized data handling. Other blockchain platforms have also moved similar functions to dedicated nodes to maintain scalability as user demand grows according to industry analysis.

How Should Developers Prepare for the Migration?

Developers are advised to identify existing instances of AccountBalanceQuery in their code and begin testing with the Mirror Node REST API on the testnet as recommended. This early testing is crucial to avoid disruptions when the feature is fully disabled in July as stated.

The Mirror Node API is currently free to use, with paid options available for higher throughput needs. Developers should evaluate their current usage patterns to determine whether they will need to upgrade to a paid plan according to service documentation.

A future option involving block nodes is under development but will not be available for the current migration window. Developers should focus on completing their transition to mirror nodes before that option becomes available as noted.

This shift highlights Hedera's ongoing commitment to enhancing performance while maintaining backward compatibility. As the migration deadline approaches, developers will need to act swiftly to ensure their applications remain fully functional on the updated platform according to platform updates.