Update: AccountBalanceQuery Deprecation Extended | Throttle Timeline Shifted
Edited By
Elena Rossi
A growing concern from developers prompts changes to the planned deprecation timeline of the AccountBalanceQuery. The timeline for throttle reductions moves ahead, with key modifications announced for 2026.
Timeline Changes Highlighted
Starting in June 2026, the first throttle reduction will shift from May. Important dates include:
June 2026: 40,000 requests per second (rps)
July 2026: 20,000 rps
August 2026: 10,000 rps
September 2026: Full removal of requests, resulting in failures for all.
What Developers Must Do
Developers are urged to review their code concerning the AccountBalanceQuery and .getAccountBalance() functions. Transitioning to the Mirror Node REST API is critical and should be tested against the testnet mirror node gradually.
"Audit your code now to avoid failures later," one comment emphasized.
Community Response
Responses on user boards reflect a mix of apprehension and determination:
Concerns on Adaptation: Many developers argue the need for more preparation time.
Encouraging Migration: Some feel the migration is positive, encouraging modernization.
Mixed Reactions: Users show divided sentiments on the practicality of the timeline's enforcement.
Key Points to Note
⚠️ Throttle Changes: Initial throttle cuts are now a month later.
📉 Removal Timeline: Potential breakdown for existing requests in September.
🔧 Migration Advice: Test against the testnet first before making full transitions.
This announcement has created waves in developer forums as many scramble to adapt before the September cut-off. Correctly addressing these updates could mitigate disruptions in service as the industry continues to evolve. What’s your strategy to manage the transition?
Shifting Currents in Developer Adaptation
Experts predict that as developers confront the new throttle timeline, there’s a strong chance of increased collaboration among teams to swiftly transition to the new Mirror Node REST API. With the September deadline looming, about 60% of developers may expedite their migration efforts, driven by the fear of service disruptions. The immediacy of technological updates usually cultivates a culture of innovation, possibly leading to better resource sharing and teamwork. If the majority can adapt in time, it could result in a more robust and modernized infrastructure for the crypto community by the end of 2026.
Learning from the Shipping Industry
A lesser-known parallel can be drawn to the shipping industry’s response to the introduction of container shipping in the 1960s. Many shipping companies faced aggressive timelines to phase out traditional cargo methods and adapt to the new, streamlined containers. Similar to the concerns of developers today, many feared operational disruptions and revenue losses. However, those who embraced the change not only modernized their fleets but also transformed global trade dynamics, illustrating that tough transitions can lead to significant advancements. This historical context serves as a reminder that while disruptions can be daunting, they often lead to innovative efficiencies if approached with an open mind.