Update | AccountBalanceQuery Deprecation Extended | Migration Guidance
Edited By
Nate Robinson
A shift in the timeline for the AccountBalanceQuery deprecation is sparking concern among developers. Originally set for May, the first throttle reduction is now pushed to June, with full removal moving from July to September 2026, according to recent sources.
Significant Changes and New Schedule
The new schedule features several key adjustments:
June 2026: Throttle reduces to 40,000 rps
July 2026: Throttle further reduces to 20,000 rps
August 2026: Throttle drops to 10,000 rps
September 2026: Complete removal of the query; all requests will fail
Developers are urged to audit their code focused on AccountBalanceQuery and .getAccountBalance(). A migration to the Mirror Node REST API is recommended, starting with tests on the testnet mirror node.
"This change requires immediate action from the community to avoid disruption," noted a prominent developer on local forums.
Community Response and Concerns
Comments across user boards show mixed sentiments as developers share perspectives:
Some feel the timeline extension opens the door for better planning.
Others believe it adds unnecessary pressure to adjust existing implementations.
There are concerns regarding the adequacy of migration documentation provided.
Key Insights from the Community
✅ Many developers have begun preparations early, anticipating challenges.
🔴 "Not enough guidance for a smooth transition," one comment reads.
🔄 A growing call for more support during migration is evident.
This timely adjustment and developer response indicate a need for proactive discussions on best practices in migration to minimize future disruptions. While the extension offers some breathing room, a sense of urgency remains within the community.
Next Steps
For those affected by the changes:
Audit your code without delay.
Begin migration tests with the Mirror Node REST API.
Stay updated through official channels for further developments.
For more information on migration guidelines, check the official documentation on the API.
What Lies Ahead for Developers
As the deprecation timeline for AccountBalanceQuery approaches, developers face critical decisions. Many are likely to ramp up their migration efforts, given that current estimates suggest a 70% chance of delays in adapting to the Mirror Node REST API. Developers who delay may encounter significant disruptions in service, especially if they wait until September. The extension provides a window for refining code efficiency but could also create a bottleneck if too many developers postpone action. Those who start now are better positioned to troubleshoot and address integration issues that may surface during the transition.
A Tale of Two Updates
In the tech world, the transition from physical to digital media mirrors what we see with this API situation. Consider the music industry’s shift to streaming. Initially met with skepticism, it required both artists and labels to rethink distribution models. Similar to the current hesitance among developers, many feared their revenue would be hurt. However, those who embraced the change early not only survived but thrived. The lesson here emphasizes the need for adaptability and proactive changes in response to tech shifts—a lesson worth remembering as the coding community navigates this adjustment.