Hedera’s v2.1 whitepaper (August 15, 2020) covers its public network and governance, separately from the 2016 algorithm report.[1]
Authors and Document
Authors: Leemon Baird, Mance Harmon and Paul Madsen. Edition: v2.1; 65 PDF pages. Document rights: © 2018–2020 Hedera Hashgraph, LLC; separate from software licensing.[1]
Read the official Hedera whitepaper (PDF).
Whitepaper Scope
The paper addresses performance, security, governance, stability and regulatory compliance. Its council design accommodates up to 39 organizations; that is not a verified current membership count.[1]
In this design, HBAR pays fees and weights proof-of-stake consensus, with a 50-billion supply. Stake weighting differs from council voting rights.[1]
Algorithm and Security Assumptions
Hedera uses Hashgraph: gossip spreads events, while virtual voting derives votes from their shared history. The DAG records event relationships, helping determine transaction order without separate voting messages. Nodes still need communication and computing resources.[2]
aBFT has conditions: more than two-thirds of participant weight follows the protocol, cryptography remains secure, and communication between honest participants eventually succeeds. Finality holds under those assumptions; unbounded message delays do not come with a guaranteed completion deadline. A consensus guarantee does not establish that every application or smart contract is free of vulnerabilities.[2]
Interpreting Performance Figures
The benchmarks measure ordering and timestamps under specified conditions, excluding full transaction processing. They do not measure today’s network or every service’s throughput.[1]
Changes After the 2020 Edition
The document’s code restrictions are historical. Hedera’s updated announcement records the platform becoming open source under Apache 2.0 on August 5, 2022.[3] In September 2024, Hedera contributed its code to Hiero under LF Decentralized Trust; operational network governance remained with the Hedera Council.[4]
Software licensing and PDF copyright must therefore be checked separately. Open code does not automatically grant permission to operate a consensus node on an existing network. Compare the 2020 roadmap and policies with current documentation before treating a proposal as implemented.
Common Misconceptions
- Public access and operator admission differ. Check present network rules before assuming permissionless participation.
- 39 is a council-design capacity. It does not establish today’s membership.
- This paper differs from the 2016 report. Its subject includes network governance.
- Consensus benchmarks do not measure all services. Transaction processing also requires resources.
Last updated: October 8, 2026
Related Terms
- Hedera (HBAR) — the network and its native asset.
- DAG — the structure linking events.
- Consensus Mechanism — how participants reach agreement.
See Also
- 2016 Hashgraph algorithm report — a distinct, consensus-focused document.
- The Byzantine Generals Problem — background on Byzantine fault models.
- Avalanche whitepaper — a different consensus design.
Sources
- Baird, Harmon and Madsen. Hedera: A Public Hashgraph Network & Governing Council, v2.1 (August 15, 2020). Historical document and benchmark limitations.
- Hedera documentation. Hashgraph Consensus Algorithm. Mechanisms, security assumptions and resource requirements.
- Hedera. Hashgraph Platform is Now Available as Open Review (2020; updated notice). Records the 2022 licensing change.
- Adkins, Charles. Introducing Hiero: The Foundation of the Future (September 16, 2024). Code contribution and network governance.