What is HBAR?

Introduction

HBAR is easiest to understand if you start with its job rather than its branding. Users and applications spend HBAR to use Hedera, and the token’s stake weight helps determine how the network reaches consensus. If you buy HBAR, you are not getting equity in the Hedera Council or a claim on protocol cash flows. You are getting exposure to the asset at the center of Hedera’s fee system, staking system, and treasury release schedule.

HBAR often gets discussed as if it were just a generic layer-1 coin. It is not. Hedera’s economic design puts unusual weight on two features: fees are set in U.S. dollar terms and converted into HBAR at the time of use, and a large share of total supply has historically sat under council-directed treasury control before being released to user accounts. The token thesis is therefore more conditional than “more activity means number go up.” Applications must choose Hedera often enough to create recurring HBAR demand, and released supply must not outpace that demand.

What is HBAR used for on the Hedera network?

HBAR has a dual purpose that Hedera itself describes as network fuel and network protection. “Fuel” is the straightforward part. Transactions and services on Hedera cost fees, and those fees are paid in HBAR. “Protection” is the security side: staking HBAR to a node contributes to that node’s consensus weight, which is effectively its voting power in the network.

That dual role is the compression point for the whole asset. A token that only pays fees behaves like a consumable input. A token that only secures consensus behaves more like collateral. HBAR does both at once. The same asset is needed by builders and users who want transactions processed, and by holders who want to participate in staking and help secure the network.

The practical consequence is that HBAR demand can come from different motives that do not always move together. An application operator may need HBAR simply to keep transactions flowing. A long-term holder may want HBAR for staking rewards or because they believe network adoption will increase token demand over time. An exchange, custodian, or fund may hold HBAR because clients want tradable exposure. These are related, but they are not identical sources of demand, and confusing them leads to bad analysis.

How do Hedera’s USD‑priced fees create demand for HBAR?

The most distinctive part of Hedera’s demand story is its fee model. Hedera says it avoids gas-based pricing. Instead, fees are predictable, set in USD, and converted to HBAR when the transaction is processed.

That changes what application builders are really buying. On many networks, users face fees that rise or fall with congestion and speculative activity in the native token. On Hedera, the economic promise is different: the service is priced in dollar terms, and HBAR is the settlement asset used to pay that bill. For a business that wants auditable and reasonably predictable transaction costs, that is attractive. It lowers budgeting uncertainty and makes the network feel more like paying for infrastructure than bidding in an open gas auction.

But HBAR demand from fees is more subtle than “higher token price equals higher revenue.” If a fee is fixed in USD terms, then a higher HBAR price means fewer HBAR are needed to pay the same dollar-denominated fee. If HBAR’s dollar price falls, more HBAR are needed for the same network action. So transaction demand creates underlying need for the token, but the amount of HBAR consumed per transaction varies with the exchange rate.

Fee demand is still real; it needs to be framed correctly. Usage creates a recurring need to source HBAR, especially for applications with steady transaction volume. What usage does not automatically create is a simple one-directional increase in HBAR units spent. The token benefits if the network wins sustained transaction flows, but the strength of that benefit depends on whether those flows are large enough and sticky enough to offset the supply coming into market circulation.

Why does Released Supply matter more than the 50 billion HBAR cap?

HBAR has a total supply of 50 billion, and the Hedera Council’s governing documents say that total supply cannot be increased above 50 billion without unanimous member consent. The cap is meaningful. But for market exposure, the more important question is not the cap alone. It is how much of that supply has actually been released from treasury-controlled accounts to user-controlled accounts.

Hedera’s own reporting does not use the term “circulating supply.” Instead, it distinguishes between Unreleased Supply and Released Supply. All HBAR begin as Unreleased Supply. Once HBAR are transferred to a user account, they become Released Supply. Hedera further divides unreleased tokens into Unallocated Supply, which has not been assigned a purpose, and Allocated Supply, which has been assigned by council decision.

That accounting tells you where the real dilution risk sits. A capped token can still create heavy market pressure if a central treasury releases large balances into the market or to ecosystem recipients who later sell. A token can also look inflationary on paper while being more manageable if releases are slow, locked, or absorbed by actual usage.

The historical record on HBAR distribution is important here. In 2020, Hedera revised its economics paper and moved from an earlier estimate that 59% of all HBAR would be released by 2025 to an estimate of 34% by 2025. That was a major change to expected near-term supply. It happened partly because of the SAFT Exchange Offer, which let earlier SAFT holders accept longer distribution schedules in exchange for additional allocations, and partly because Hedera revised allocation categories and schedules.

The specific 2020 numbers should be handled carefully because Hedera later said that blog summary was outdated and pointed readers to its treasury management reporting for current information. But the lesson remains: HBAR’s market exposure has always depended heavily on release timing, not just total supply.

By Q1 2026, Hedera Council treasury reporting showed about 47.308 billion HBAR as Released Supply. That implies most of the 50 billion supply had already been released to user accounts by that point, even though Hedera still avoids using a standard “circulating supply” label. This narrows one uncertainty and leaves another. The narrowing part is that the market is much closer to seeing the full token base released than it was a few years earlier. The remaining uncertainty is where those released tokens sit, how liquid they are, and how concentrated ownership remains.

How does the Hedera Council’s treasury control affect HBAR supply and concentration?

HBAR is not governed like a credibly neutral asset with no identifiable steering body. The Hedera Council has formal authority over treasury transfers and network changes. The LLC agreement says HBAR may only be transferred out of a Hedera Treasury Account upon approval of a majority of council members. The same agreement says proposed modifications to Hedera network software require council approval and then implementation by members under council procedures.

For some users, that structure is part of the appeal. A known governing body with named organizations can support enterprise comfort, policy continuity, and operational accountability. For others, it is a core risk. treasury outflows are not algorithmically automatic; they are politically and organizationally controlled. Software change is not permissionless rough consensus; it is managed governance.

This is not a purely philosophical issue. It shapes the token directly. If a meaningful quantity of HBAR remains in treasury-linked or foundation-linked hands, then token supply, ecosystem grants, and market overhang remain tied to governance decisions. A Nasdaq filing tied to the proposed Grayscale Hedera Trust cited the Hedera Council as holding roughly 10.624 billion HBAR, or 21.25% of total supply, as of February 20, 2025, and noted a 7 billion HBAR grant to the Hedera Foundation announced in December 2024. Even if those balances are not all immediately market-active, they are large enough that concentration has to be part of any serious HBAR thesis.

So the correct question is not whether HBAR has a cap. It does. The sharper question is how much effective market supply sits in concentrated hands that can influence future sell pressure, grants, lockups, or staking behavior.

How does staking HBAR change my exposure and market dynamics?

Staking changes HBAR from a purely directional asset into an asset that can earn network rewards, but the mechanics are important. Hedera’s staking program lets an account stake HBAR to a network node and earn rewards while contributing to that node’s consensus weight. There is no lock-up period, no bonding requirement, and no slashing. Your HBAR remains liquid.

That is materially different from proof-of-stake systems where staking means giving up liquidity for a fixed period or taking explicit slash risk if validators misbehave. On Hedera, the holder experience is gentler. You can keep liquidity and still participate. It lowers the friction to stake, which can support broader participation, but it also means staking does not remove supply from circulation in the same hard way that bonded systems do.

Rewards are distributed from the staking reward account, 0.0.800, and that account is primarily funded by daily distributions from the fee collection account, 0.0.802. After HIP-1259, transaction fees are consolidated into the fee collection account and then distributed via a daily synthetic transaction. It ties staking rewards more cleanly to the network’s fee machinery.

The economic implication is mixed. On the positive side, staking rewards are not simply magic emissions detached from network activity; they are connected to fee collection flows and program funding. On the limiting side, because HBAR remains liquid and staked balances are not forcibly locked, staking is less of a structural supply sink than in networks where tokens are immobilized for long periods.

Reward eligibility also has practical conditions. An account has to be staked for a full 24-hour staking period, measured from midnight UTC to midnight UTC, and both the chosen node and the reward account must meet their threshold conditions. There is also indirect staking, where one account stakes to another account that then stakes to a node. In that arrangement, both balances help the node’s stake weight, but rewards are paid to the intermediary account. That is relevant for custodians and exchanges, because if they sit between you and the node, they may control reward receipt and payout policy.

How does holding HBAR directly compare with custody or a fund wrapper?

The cleanest HBAR exposure is direct ownership in your own account. You hold the native asset, can move it, can stake it, and bear your own custody risk. If you use a custodian, the exposure changes. You still have economic exposure to HBAR, but a third party controls key management and often shapes how staking, transfers, and approvals work.

Hedera has built explicit support for institutional custody integrations. Its Custodians Library supports Fireblocks and DFNS, and the documentation emphasizes why third-party custody matters for security, compliance, and institutional workflows. Fireblocks support for HBAR and Hedera-specific tooling show that HBAR is not only a retail-tradable token; it is also an asset being fitted into professional treasury and custody systems. That can widen market access, but it also adds familiar counterparty risk: your asset may be economically yours while operational control sits elsewhere.

Fund wrappers change the exposure even more. The proposed Grayscale Hedera Trust ETF is designed to hold HBAR and have its shares reflect the value of HBAR held by the trust, less expenses and liabilities. That sounds simple, but what you actually own is a share in a vehicle, not HBAR in your own account. You cannot use those shares to pay Hedera fees, cannot natively stake through the trust today, and are exposed to fund-level frictions such as fees, creation and redemption mechanics, custody concentration, and tracking error.

The prospectus is especially clear on two points. First, the trust’s staking condition had not been met as of the filing, so the trust could not stake HBAR at that time. Second, the sponsor’s fee and related expenses are paid in HBAR, which means the amount of HBAR represented by each share declines over time. So a fund wrapper gives convenience and brokerage-style access, but it strips out some of the token’s native utility and introduces fee drag.

What risks could weaken HBAR’s investment thesis?

The cleanest bull case for HBAR is that enterprises and applications value predictable, USD-denominated fees enough to bring durable transaction volume to Hedera, while staking and broad market access keep the token financially relevant. The cleanest bear case is that HBAR’s role in the network remains real but economically weaker than holders expect.

There are several ways that can happen. If applications use Hedera but hold only working balances of HBAR because fees are dollar-priced and operationally predictable, fee demand may remain utilitarian rather than strongly speculative. If treasury-linked or foundation-linked balances are large and periodically released, supply overhang can absorb demand. If governance concentration or council control becomes a market concern, institutions may treat HBAR as more policy-exposed than competitors. If competing networks offer similar or better utility with stronger decentralization, deeper liquidity, or better developer mindshare, HBAR’s niche can narrow.

There is also operational risk. Hedera’s status infrastructure shows active maintenance and generally strong uptime, but the network has also had meaningful incidents, including the 2023 episode in which mainnet proxies were turned off after reported network irregularities. The exact exploit narratives around that event were disputed at the time, but the lasting point is straightforward: network accessibility, upgrade governance, and smart-contract safety are not abstractions. They affect whether HBAR’s utility is trusted in production.

Finally, access rails can help or hurt. A proposed ETF, futures access, and institutional custody integrations can broaden the buyer base. But those rails are conditional on regulators, custodians, listing venues, and wrapper mechanics. Direct spot ownership remains the least transformed exposure. Readers who want to buy or trade HBAR can do that on Cube Exchange, where the same account can handle an initial quick convert, later spot orders, and repeat rebalancing without piecing together multiple apps.

Conclusion

HBAR is best understood as the spend-and-stake asset of the Hedera network. Its value depends less on abstract layer-1 narratives than on a concrete balance: whether predictable-fee network usage and staking demand can outweigh the effects of treasury releases, concentrated holdings, and governance-controlled supply. If you remember one thing, remember this: owning HBAR is exposure to Hedera’s utility and security mechanism, not to ownership of the council that governs it.

How do you buy Hedera?

If you want Hedera exposure, the practical Cube workflow is simple: fund the account, buy the token, and keep the same account for later adds, trims, or exits. Use a market order when speed matters and a limit order when entry price matters more.

Cube lets readers fund with crypto or a bank purchase of USDC and get into the token from one account instead of stitching together multiple apps. Cube supports a quick convert flow for a first allocation and spot orders for readers who want more control over later entries and exits.

1. Fund your Cube account with fiat or a supported crypto transfer.
2. Open the relevant market or conversion flow for Hedera and check the current spread before you place the trade.
3. Choose a market order for immediate execution or a limit order for tighter price control, then enter the size you want.
4. Review the estimated fill and fees, submit the order, and confirm the Hedera position after execution.