Algorand

P2P Protocol

A permissionless, pure Proof-of-Stake blockchain using a Byzantine Agreement consensus protocol, designed for immediate transaction finality (no forking/reorg risk) and high throughput.

Foundation
Links
Visit Website Suggest an edit

Details

License AGPL-3.0
Dev Status 🟢 Active
Owner Algorand Foundation.
Governing Body Algorand Foundation (non-profit).
Country Singapore (Algorand Foundation Ltd. is Singapore-registered — confirmed via the go-algorand repo's copyright notice)
Start Year 2019
Stack Go.
Funding Algorand Foundation grants and ecosystem programs.
Last Investigated Aug 23, 2026

Use Case Domains

Platform Evolution & Sovereignty

P2P Protocol Attributes

Origins Pure PoS L1 targeting immediate finality (no forks/reorgs) via a Byzantine Agreement protocol, designed by Silvio Micali (Turing Award-winning cryptographer).
Database N/A conventional DB; the Indexer service provides queryable historical data atop the node.
Query Language Indexer service query API.
Data Formats MessagePack.
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Via third-party wallets (Pera Wallet, Defly, etc.).
Web Support Via third-party wallets and dApp frontends.
Native Apps go-algorand ships as a binary.
Terms Free, open-source (AGPL-3.0 — copyleft; network-use triggers source-disclosure obligations); network fees minimal/fixed.
Funds Algorand Foundation treasury not independently sized this pass.
Based On Novel Byzantine Agreement design; not forked from a prior chain.
P2P Architecture Gossip network; committee-based Byzantine Agreement — a randomly, cryptographically-sortitioned committee proposes/votes each block, re-selected every round.
Overlay Network Global, permissionless.
Content Addressing No.
Local-First N/A
E2EE N/A
CRDTs Lib N/A
Byzantine Fault Tolerance Yes — Algorand's own Byzantine Agreement protocol, immediate (not probabilistic) finality.
Signature Ed25519.
Permissions Permissionless; every ALGO holder is eligible for the consensus committee (stake-weighted), no separate validator-registration step.
Semantic Web Compatibility No.
Smart Contract Yes — TEAL/Algorand Smart Contracts (ASC1), Python/Reach as higher-level authoring languages.
Protocol Stack Position Base-layer settlement + execution (Layer 1).
Asset / Value Embedding Native (ALGO) plus ASA (Algorand Standard Assets) as a first-class, non-smart-contract token layer.
Protocol Maturity / Standardization Mature, mainnet since 2019, no formal external standards body.