What is Hedera Hashgraph and how does HBAR work?

The first thing most newcomers hear about Hedera is that it is “just another blockchain.” That framing misses the central design choice. Hedera does not organize data into sequential blocks chained together by cryptographic hashes the way Bitcoin and Ethereum do. Instead, it records transactions in a directed acyclic graph, a structure where every event references two earlier events instead of one prior block. The result is a consensus layer that confirms transactions in parallel, reaches mathematical finality in seconds, and tolerates up to one third of malicious nodes without stalling. Understanding that distinction is the starting point for evaluating everything else the network offers.

Hashgraph versus blockchain

Traditional blockchains process transactions inside discrete blocks. Each block references the previous one, forming a single chain. Miners or validators compete to propose the next block, and the network discards competing proposals. That sequential process caps throughput and introduces latency.

Hashgraph abandons blocks entirely. Every node in the network creates an “event” each time it receives new information, and that event records two parent hashes: one from the node itself and one from the node it just communicated with. Over time these events weave into a graph instead of a chain. Because every node can create events simultaneously, the structure processes transactions in parallel instead of waiting for one winner.

The practical payoff is speed. Hedera has recorded peak production throughput above 3,300 transactions per second with three-to-five-second finality. Theoretical capacity under lab conditions exceeds 10,000 TPS. For comparison, Ethereum Layer 1 handles roughly 15 to 30 TPS before rollups, and Bitcoin processes about seven.

The tradeoff is architectural complexity. The hashgraph data structure requires every node to maintain a full copy of the graph in memory, which increases hardware requirements as the network grows. The consensus algorithm was originally patented by Swirlds, the company co-founded by Hedera’s creators Leemon Baird and Mance Harmon. That patent followed a different intellectual-property path than most open-source Layer 1 projects, though the code was later released under an Apache 2.0 license in 2022.

Another distinction worth noting is transaction ordering. Hashgraph provides “fair ordering,” meaning the consensus timestamp assigned to a transaction reflects the median of the times at which nodes first received it. This prevents a single node from front-running transactions by manipulating their position in the queue, a property that has drawn interest from financial institutions concerned about miner extractable value.

How consensus works: gossip-about-gossip and virtual voting

Hedera reaches consensus through two mechanisms that run together.

Gossip-about-gossip is the communication protocol. Each node randomly selects another node and shares its latest events plus the history of who told it what. Because every event contains metadata about its two parent events, each round of gossip carries exponentially more information than a simple transaction broadcast. Within a few rounds the entire network converges on the same set of events.

Virtual voting is the agreement protocol. Once every node has the same graph, each node can independently calculate how every other node would have voted on the ordering of transactions, without sending a single vote message. The math works because the graph already encodes when each node learned about each event. Nodes simply run the same deterministic algorithm and arrive at the same result.

Together, these two mechanisms achieve asynchronous Byzantine fault tolerance, or aBFT. That is the strongest guarantee in distributed-systems theory: the network will reach correct consensus even if up to one third of nodes are malicious and even if messages between honest nodes are delayed by an attacker. No proof-of-work lottery or leader election is needed.

The practical benefit of aBFT over weaker consensus models is finality. On many blockchain networks, a transaction is “probabilistically final” after a certain number of confirmations, meaning there is a shrinking but nonzero chance it could be reversed. On Hedera, once the virtual voting algorithm determines a transaction’s consensus timestamp and order, that result is mathematically final. No future event can reorder or undo it, which is a property that regulated financial institutions often require before settling high-value transfers on a distributed ledger.

The tradeoff is that aBFT consensus depends on the assumption that more than two thirds of the stake-weighted voting power remains honest. If that threshold is breached, the entire model fails outright instead of degrading gracefully.

The governing council

Unlike most public networks that rely on anonymous, permissionless validator sets, Hedera is governed by a council of term-limited organizations. As of mid-2026, the council has 31 members out of a maximum 39 seats.

Members include Google, IBM, Dell, Boeing, Standard Bank, Deutsche Telekom, LG Electronics, Chainlink Labs, Ubisoft, the London School of Economics, University College London, and more recently McLaren Racing. Each member operates a consensus node, holds equal voting rights regardless of company size, and serves a maximum of two consecutive three-year terms.

The council controls three things: network software upgrades, treasury disbursements from the HBAR reserve, and strategic direction. This model gives the network a level of corporate accountability that is unusual in cryptocurrency but raises a legitimate question about centralization. Critics point out that 31 hand-picked multinationals do not constitute the same kind of decentralization that thousands of anonymous validators provide on networks like Ethereum.

Hedera has responded by stating that the council structure is a transitional measure and that the long-term goal is to open node operation to the public. Community nodes began rolling out in phases, but full permissionless validation is not yet live.

The council also manages the HBAR treasury, which holds the unallocated portion of the 50 billion token supply. Treasury disbursements fund ecosystem grants, developer incentives, and operational costs. Decisions about how and when to release tokens from the treasury require council approval, giving these organizations direct influence over the token’s circulating supply schedule.

Token economics

HBAR has a fixed maximum supply of 50 billion tokens, all pre-minted at the network genesis in September 2018. There is no inflation mechanism and no token burn. New supply enters circulation through scheduled treasury releases managed by the governing council, typically on a quarterly basis. As of mid-2026, approximately 86.6% of the total supply is in circulation.

The token serves three functions. First, it pays transaction fees, which are set in USD terms and converted to HBAR at the current exchange rate, giving users predictable costs regardless of token price volatility. Second, it secures the network through proxy staking, where HBAR holders delegate tokens to nodes to increase their consensus weight. Third, it acts as a unit of account across Hedera native services like the Token Service and Consensus Service.

Staking rewards come from the network treasury, not from inflation. The protocol caps fully rewarded staked HBAR at 6.5 billion tokens, or 13% of total supply. As of May 2026, roughly 7.3 billion HBAR were staked, meaning actual annualized yields sit between 1.8% and 2.1% due to proportional dilution beyond the reward cap.

One structural critique is the value-accrual model. Network transaction fees flow to node operators and the council treasury. They are not burned or redistributed to all token holders. Strong network usage therefore does not translate automatically into direct price support for HBAR, a gap that separates it from deflationary models used by some competing networks.

Use cases: enterprise, stablecoins, and CBDC pilots

Hedera has positioned itself as infrastructure for institutional and government use cases, with less emphasis on retail DeFi.

Stablecoin issuance. The Hedera Stablecoin Studio provides a modular toolkit for issuing fiat-backed tokens on the network with fixed fees and high throughput. PHPX, a multi-bank Philippine peso stablecoin built in collaboration with Rizal Commercial Banking, Cantilan Bank, and UBX, is one live example. The low per-transaction cost makes micropayment-heavy stablecoin use cases viable in ways that higher-fee networks struggle to support.

CBDC pilots. The Reserve Bank of Australia worked with Hedera as part of Project Acacia, exploring central bank digital currency settlement on the network. Separately, the Universal Digital Payments Network completed a proof-of-concept integrating Hedera-native stablecoins and CBDCs from the EMTECH Sandbox into a cross-border messaging layer. These remain pilot-stage projects, not production deployments.

Supply-chain and audit trails. The Hedera Consensus Service records tamper-evident, time-stamped logs that enterprises use for provenance tracking, compliance reporting, and cross-system data integrity proofs. Several logistics and carbon-credit platforms have adopted HCS for ordered event streams that need to be independently verifiable.

Tokenized assets. Integration between Hedera and tokenized equity platforms allows EVM-compatible smart contracts to manage redemption logic for securities, bonds, and real-world assets, aligning with broader institutional interest in on-chain settlement.

Carbon credit and ESG tracking. Several environmental platforms use the Hedera Consensus Service to create verifiable, timestamped records of carbon offset purchases and sustainability metrics. The Guardian, an open-source platform originally developed by Hedera and now maintained by the Linux Foundation, allows organizations to mint auditable carbon credits as tokens on the network. The appeal for ESG use cases is that the network itself consumes minimal energy compared to proof-of-work chains, and every credit issuance receives a tamper-proof consensus timestamp.

Native services: HTS, HCS, and smart contracts

Hedera separates core functionality into three native services, each optimized at the protocol level and not built as smart-contract wrappers.

Hedera Token Service handles both fungible and non-fungible token creation directly in the consensus layer. Minting, transferring, and managing token compliance features like freeze, wipe, and KYC flags happen as native operations with predictable fees measured in fractions of a cent. This is meaningfully cheaper than deploying a full ERC-20 or ERC-721 contract on Ethereum or similar networks.

Hedera Consensus Service provides ordered, tamper-evident message logs. Any application can submit a message to an HCS topic and receive a consensus timestamp plus a running hash that proves the message existed in that order at that time. Use cases include oracle feeds, audit trails, and cross-chain event sequencing.

Smart Contract Service runs a Solidity-compatible EVM execution environment based on the Hyperledger Besu client. Developers who already write Ethereum smart contracts can deploy them on Hedera without code changes, gaining lower fees and faster finality while retaining access to Hedera native services through precompiled system contracts. The integration means that a single smart contract can issue HTS tokens, read HCS logs, and interact with HBAR balances natively.

The EVM layer also supports common Ethereum tooling, including Hardhat, Ethers.js, and MetaMask, which lowers the barrier for developers migrating from Ethereum-based projects. Gas costs on Hedera’s EVM are denominated in “tinybars” (the smallest HBAR subdivision, equal to one hundred-millionth of an HBAR) and are pegged to USD-denominated fee schedules, so contract execution costs remain predictable even during periods of token price volatility.

Competitive position

Hedera occupies a specific niche. It targets organizations that need predictable fees, fast finality, regulatory legibility, and fair transaction ordering, and it trades off grassroots decentralization to deliver those properties.

Against Ethereum, Hedera offers lower fees and faster base-layer finality but has a far smaller decentralized exchange and DeFi ecosystem. Ethereum Layer 2 rollups have narrowed the fee gap significantly, reducing one of Hedera’s historical advantages.

Against Solana, Hedera shares the emphasis on high throughput but differs in governance philosophy. Solana relies on thousands of permissionless validators; Hedera relies on a curated council. Each model carries different failure modes: Solana has experienced multiple outages under congestion, while Hedera has maintained higher uptime but with far lower real-world transaction volume relative to theoretical capacity.

Against enterprise-focused permissioned ledgers like Hyperledger Fabric, Hedera offers a public, auditable ledger with a native token and open access, while permissioned networks offer tighter privacy controls and no token dependency.

The network’s DeFi total value locked and developer ecosystem remain small compared to the top five smart-contract platforms. Hedera’s strength is enterprise adoption and institutional pilots; its weakness is organic community-driven growth.

One area where Hedera has made inroads is the ETF narrative. In late 2024, Canary Capital filed for a spot HBAR exchange-traded fund with the U.S. Securities and Exchange Commission, marking one of the first ETF applications for a token outside the Bitcoin and Ethereum ecosystem. Whether approval materializes or not, the filing signals growing institutional interest in HBAR as a distinct asset class within the broader cryptocurrency market.

Limitations and open questions

Centralization concerns. Thirty-one council-selected nodes is more centralized than most public networks claim to be. Until full permissionless node operation goes live, the network depends on the continued participation and good faith of its council members.

Value accrual. As noted above, network revenue flows to operators and the treasury, not to token holders. Strong transaction growth does not mechanically benefit HBAR holders the way fee burns benefit holders on deflationary networks.

DeFi and developer adoption. Hedera’s DeFi ecosystem is thin. Most liquidity and developer attention in the broader market flows to Ethereum, Solana, and their respective Layer 2 and appchain ecosystems. Attracting builder mindshare remains a challenge.

Intellectual property history. The hashgraph algorithm was originally patented by Swirlds and later open-sourced. That history created early friction with the open-source ethos that dominates crypto culture, and some developers remain wary.

Staking yield. With staked HBAR exceeding the reward cap, effective yields are modest and declining. This limits the token’s appeal as a yield-bearing asset compared to networks with higher or inflation-funded staking returns. The council has not publicly committed to raising the reward cap, so stakers should expect yields to compress further as more HBAR is delegated.

Network activity versus capacity. While Hedera’s theoretical throughput exceeds 10,000 TPS and peak production has reached 3,300 TPS, average real-time throughput typically sits in the low double digits. That gap between capacity and actual usage raises questions about current demand for the network’s services, even as cumulative transaction counts grow.

What this does not cover

This guide does not cover HBAR price forecasts, technical chart analysis, or investment advice. It does not provide step-by-step instructions for buying or staking HBAR on specific exchanges. It does not assess the legal or regulatory status of HBAR in any jurisdiction. It does not cover Hedera’s mirror node architecture, SDK implementation details, or testnet developer workflows in depth. It does not compare Hedera to every competing Layer 1 network, nor does it evaluate individual DeFi protocols or NFT projects built on the network.

Practical checks

Read the whitepaper and the open-source hashgraph code. The algorithm is no longer behind a patent wall. Review the Hedera documentation and the Swirlds hashgraph repository on GitHub to understand the consensus math firsthand.

Verify council node status. The Hedera network explorer shows which council members are operating nodes, their uptime, and their stake weight. Check whether the node set has changed before making assumptions about network security.

Compare fee structures. Hedera publishes a fee schedule denominated in USD. Compare the actual cost of minting a token, submitting a consensus message, or executing a smart contract against equivalent operations on Ethereum, Solana, and Polygon to see where the savings are meaningful for a specific use case.

Check staking economics before delegating. With staked HBAR above the reward cap, new stakers receive diluted yields. Run the numbers on current annualized returns (1.8% to 2.1% as of mid-2026) before committing tokens, and factor in the opportunity cost of locking capital.

Audit DeFi protocol risk independently. Hedera’s native services handle token issuance and consensus logging at the protocol level, but third-party DeFi applications built on top carry their own smart-contract and liquidity risks. Do not assume that protocol-level security extends to every application deployed on the network.

Disclaimer: This article is for informational and educational purposes only. It does not constitute financial, investment, or legal advice. Cryptocurrency markets are volatile and carry significant risk. Always conduct your own research before making any financial decisions. Information is current as of September 2, 2026, and may become outdated.