Hedera has launched a significant enhancement to its network with the introduction of proposal HIP-1313 in version v0.73. This development introduces a dedicated lane specifically designed for the high-volume creation of entities, catering to various applications that necessitate rapid transaction processing.
The new high-volume lane boasts impressive throughput capabilities, supporting up to 50,000 transactions per second (TPS) for FileAppend operations and 25,000 TPS for ConsensusCreateTopic actions. The overall aggregate limit for the lane is set at 31,500 TPS, providing substantial capacity to handle spikes in demand.
One of the key features of HIP-1313 is its implementation of an optional flag within the transaction body. Developers can activate this by setting high_volume = true, which reroutes the transaction from the standard lane to a series of throttle buckets dedicated to specific operation types. Importantly, the standard lane remains unaffected in terms of its behavior and pricing, allowing for both pathways to coexist without interference. This design addresses the challenges presented by concentrated demand during peak times.
The Hedera team identified several scenarios in which this enhancement would prove beneficial. These include the mass onboarding of users during product launches, account migrations that must adhere to regulatory deadlines, and minting events for non-fungible tokens (NFTs) that require the processing of thousands of operations in a very short timeframe.
Additionally, the pricing model for the new lane operates on dynamic, piecewise linear curves that are indexed to real-time utilization. Each transaction’s cost is determined using the formula standard_fee × multiplier, where the multiplier increases in proportion to the lane’s load. Values for this pricing model are stored in simpleFeesSchedules.json and can be audited through the consensus node repository.
To mitigate financial risks, Hedera has introduced the setMaxTransactionFee feature, which serves as an absolute cap on transaction costs. If the calculated fee surpasses this limit, the transaction will return an error indicating INSUFFICIENT_TX_FEE, thus protecting developers from unexpected expenses. This enables teams to effectively budget for high-demand periods with greater confidence.
To take advantage of these new features, developers are required to update their SDKs to the latest versions. Specifically, Java SDK must be version 2.71 or higher, Go SDK requires version 2.79 or higher, and JavaScript SDK must be version 2.83 or higher. The enhancements also extend to the Mirror Node REST API, which now includes fields for high_volume and high_volume_pricing_multiplier in its transaction endpoints, allowing developers to verify the effective multiplier applied after consensus. These updates have been accessible since version 0.153.0 of the Mirror Node.
In summary, the launch of HIP-1313 marks a pivotal step in Hedera’s ongoing efforts to enhance its network capabilities, particularly in handling high transaction volumes while ensuring predictable costs for developers.
