Hedera sets its transaction fees in dollars and charges them in HBAR

A different approach to transaction pricing

Most public networks price their transactions directly in their native token, which means the real cost of any on-chain action moves in lockstep with market conditions. @hedera takes a different path. Hedera pegs transaction fees to a static value in USD, but with the actual fees paid in $HBAR. The result is that users and enterprises know what a transaction costs in dollar terms before they sign it, regardless of where $HBAR is trading.

A basic transfer is fixed at $0.0001, denominated in USD and settled in HBAR. Hedera updates its exchange rate file frequently so that clients are insulated from HBAR volatility. As HBAR moves up or down against the dollar, the amount of HBAR charged adjusts accordingly, keeping the USD price stable.

How the fee schedule and exchange rate work under the hood

Prices come from the configured fee schedule stored in system file 0.0.113 and may change. Fees are charged in HBAR, converted from USD at the live exchange rate. The exchange rate itself is published separately by the network and refreshed roughly once an hour, meaning the HBAR amount a user pays can shift between updates even for an identical transaction.

The fee model applies one consistent pricing structure to every transaction on Hedera. A transaction's total fee is the sum of three components: a node fee, a network fee, and a service fee, each calculated as a base amount plus extras that measure specific resources consumed.

All values are computed in USD, stored as tinycents in the canonical schedule, and converted to HBAR using the network exchange rate at handle time. All fees are defined in USD as tinycents, where 10^8 tinycents form one cent and 10^10 tinycents equal one dollar, providing a high degree of precision while avoiding floating point math.

Standard fees follow the published table, but not every transaction is straightforward. The fee tables reflect standard transaction pricing. If the high-volume flag is set on a supported entity creation transaction, a variable-rate multiplier is applied on top of the standard fee. Developers working at scale should account for this when estimating costs.

By offering consistent and transparent costs, Hedera's approach aligns with the expectations of businesses and enterprises that rely on stable operational expenses for scalability and budget planning. For builders, this predictability also has a practical side: transaction cost becomes a property of the application code that can be planned for, asserted against, and audited, and wallets can show the exact fee before the user signs.

Sources:
Hedera Official Fee Documentation
Hedera: How Hedera Calculates the HBAR/USD Exchange Rate
HIP-1261: Simple Fees