TL;DR:
- Hedera launched proposal HIP-1313 in model v0.73 of its community, introducing a devoted lane for high-volume entity creation.
- The brand new lane helps as much as 50,000 TPS for FileAppend and 25,000 TPS for ConsensusCreateTopic, with an combination cap of 31,500 TPS.
- The value of every transaction within the high-volume lane varies in response to real-time lane saturation and could be capped utilizing setMaxTransactionFee.
Hedera added a structural enchancment to its community with the launch of HIP-1313, a technical proposal that introduces a high-volume processing lane designed for the mass creation of entities. The replace was included in model v0.73 of the community and has been obtainable on mainnet and testnet since its deployment.
The core mechanism of HIP-1313 is an non-compulsory flag within the transaction physique: when a developer prompts `high_volume = true`, the transaction is routed away from the usual lane towards a set of throttle buckets devoted by operation kind. The usual lane undergoes no modification to its conduct or its mounted pricing scheme. Each paths coexist with out interference.
The proposal goals to resolve a concrete downside round demand spikes concentrated in brief time home windows. Among the many use circumstances addressed by the Hedera staff are mass consumer onboarding throughout a product launch, account migrations beneath regulatory deadlines, and NFT minting occasions that require processing 1000’s of operations inside minutes.
Hedera Implements Dynamic Pricing with a Assured Cap
The pricing mannequin of Hedera’s new lane operates on piecewise linear curves listed to real-time utilization of every bucket. The price of every transaction is calculated as `standard_fee × multiplier`, the place the multiplier rises proportionally to lane load. The values are dedicated in `simpleFeesSchedules.json` and are auditable within the consensus node repository.
To restrict monetary publicity, `setMaxTransactionFee` acts as an absolute ceiling: if the calculated charge exceeds the configured restrict, the transaction returns `INSUFFICIENT_TX_FEE` as an alternative of executing at a better price than anticipated. By this mechanism, Hedera permits groups to plan high-demand bursts inside already identified budgets.
Integration requires updating the corresponding SDK: Java v2.71 or greater, Go v2.79 or greater, and JavaScript v2.83 or greater. The Mirror Node REST API exposes the `high_volume` and `high_volume_pricing_multiplier` fields within the transaction endpoints, which permits verification of the efficient multiplier utilized by the community after consensus. These extensions have been obtainable since model 0.153.0 of the Mirror Node.
