FileAppend operations, with an aggregate network cap of 31,500 TPS.
Hedera deployed its HIP-1313 upgrade on May 25, boosting the network’s capacity to 50,000 transactions per second for specific operations and introducing a dedicated lane for high-throughput entity creation.
The upgrade, part of network version v0.73, introduces an optional flag for developers to route transactions to a new high-volume lane, according to a technical post published by the Hedera team. Both the standard and high-volume lanes coexist without interference.
The new lane supports up to 50,000 TPS for FileAppend and 25,000 TPS for ConsensusCreateTopic, with a combined aggregate limit of 31,500 TPS across all throttles. Pricing in this lane is dynamic, calculated as the standard fee multiplied by a multiplier that rises with real-time load. To prevent runaway costs during demand spikes, developers can use the setMaxTransactionFee function, which rejects transactions that would exceed a predefined budget.
This upgrade positions Hedera to better handle enterprise-grade workloads like mass user onboarding and large-scale NFT mints, enhancing its competitiveness against other high-throughput chains like Solana and Sui. The changes are now live on the mainnet and testnet.
The core of HIP-1313 is its solution for managing demand spikes. By routing high-volume operations away from the standard fixed-fee lane, Hedera can offer greater capacity without altering its base transaction costs. The dynamic fee multiplier for the high-volume lane is based on piecewise linear curves tied to the real-time utilization of each operation's dedicated throttle bucket.
This mechanism is designed for use cases such as product launches that onboard thousands of users simultaneously or time-sensitive account migrations. Developers can plan for these bursts within a known budget by setting the maximum fee, ensuring financial predictability.
To integrate the new feature, developers must update to the latest SDK versions: Java v2.71, Go v2.79, or JavaScript v2.83 and higher. The corresponding Mirror Node REST API has also been updated in version 0.153.0 to expose fields that allow for the verification of the transaction path and the final pricing multiplier applied.
This article is for informational purposes only and does not constitute investment advice.
