TL;DR:
- Hedera launched proposal HIP-1313 in version v0.73 of its network, introducing a dedicated lane for high-volume entity creation.
- The new lane supports up to 50,000 TPS for FileAppend and 25,000 TPS for ConsensusCreateTopic, with an aggregate cap of 31,500 TPS.
- The price of each transaction in the high-volume lane varies according to real-time lane saturation and can be capped using setMaxTransactionFee.
Hedera added a structural improvement to its network with the launch of HIP-1313, a technical proposal that introduces a high-volume processing lane designed for the mass creation of entities. The update was included in version v0.73 of the network and has been available on mainnet and testnet since its deployment.
The core mechanism of HIP-1313 is an optional flag in the transaction body: when a developer activates `high_volume = true`, the transaction is routed away from the standard lane toward a set of throttle buckets dedicated by operation type. The standard lane undergoes no modification to its behavior or its fixed pricing scheme. Both paths coexist without interference.
The proposal aims to solve a concrete problem around demand spikes concentrated in short time windows. Among the use cases addressed by the Hedera team are mass user onboarding during a product launch, account migrations under regulatory deadlines, and NFT minting events that require processing thousands of operations within minutes.
Hedera Implements Dynamic Pricing with a Guaranteed Cap
The pricing model of Hedera’s new lane operates on piecewise linear curves indexed to real-time utilization of each bucket. The cost of each transaction is calculated as `standard_fee × multiplier`, where the multiplier rises proportionally to lane load. The values are committed in `simpleFeesSchedules.json` and are auditable in the consensus node repository.
To limit financial exposure, `setMaxTransactionFee` acts as an absolute ceiling: if the calculated fee exceeds the configured limit, the transaction returns `INSUFFICIENT_TX_FEE` instead of executing at a higher cost than expected. Through this mechanism, Hedera allows teams to plan high-demand bursts within already known budgets.
Integration requires updating the corresponding SDK: Java v2.71 or higher, Go v2.79 or higher, and JavaScript v2.83 or higher. The Mirror Node REST API exposes the `high_volume` and `high_volume_pricing_multiplier` fields in the transaction endpoints, which allows verification of the effective multiplier applied by the network after consensus. These extensions have been available since version 0.153.0 of the Mirror Node.
