Avalanche
P2P Protocol
Company
Details
License BSD-3-Clause
Dev Status 🟢 Active
Owner Ava Labs (the company that developed and continues to steward core protocol/client development).
Governing Body Ava Labs directly — no independent foundation identified as a meaningfully separate governing body in this session's research (Avalanche Foundation exists but wasn't confirmed as holding independent authority over protocol direction).
Country N/A (Ava Labs is a US-based company; precise jurisdiction not independently confirmed this pass)
Start Year 2020
Stack Go.
Funding Ava Labs (VC-backed — Andreessen Horowitz, Polychain Capital, and Initialized Capital among its investors) plus the Avalanche Foundation's ecosystem grant programs.
Last Investigated Aug 23, 2026
P2P Protocol Attributes
Origins Metastable/repeated-sub-sampling consensus family (the "Snow*" protocols), enabling a novel BFT approach; supports multiple built-in chains (X-Chain, C-Chain, P-Chain) plus custom subnets.
Database N/A conventional DB; JSON-RPC (C-Chain is Ethereum-JSON-RPC-compatible).
Query Language JSON-RPC.
Data Formats Custom binary serialization (per-chain; C-Chain uses Ethereum-compatible RLP).
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Via third-party wallets (Core, MetaMask for the C-Chain).
Web Support Via third-party wallets and dApp frontends.
Native Apps AvalancheGo ships as a binary.
Terms Free, open-source; network fees paid to validators, partially burned.
Funds Ava Labs' funding as a VC-backed company is not fully public; Avalanche Foundation runs separate grant programs.
Based On Novel Snow*/Avalanche consensus family; C-Chain reuses Ethereum's execution semantics (EVM-compatible) but the underlying consensus is original.
P2P Architecture Repeated random sub-sampling gossip among validators (Avalanche/Snowman consensus family) rather than a fixed committee or global broadcast per round.
Overlay Network Global, permissionless (validators require staked AVAX).
Content Addressing No.
Local-First N/A
E2EE N/A
CRDTs Lib N/A
Byzantine Fault Tolerance Yes — the Avalanche consensus family, probabilistic-safety BFT via repeated sub-sampling.
Signature BLS (P-Chain/validator consensus, used for Avalanche Warp Messaging's cross-subnet aggregate signatures) and secp256k1 (C-Chain, EVM-compatible).
Permissions Permissionless for transacting; validating requires 2,000 AVAX minimum stake (materially higher than several peers in this batch).
Semantic Web Compatibility No.
Smart Contract Yes — the C-Chain is EVM-compatible (Solidity runs directly); the platform also supports custom-VM subnets.
Protocol Stack Position Base-layer settlement (P-Chain), asset exchange (X-Chain), smart-contract execution (C-Chain) as three built-in chains, plus custom subnets on top.
Asset / Value Embedding Native (AVAX) across all three built-in chains; subnets may define their own native assets.
Protocol Maturity / Standardization Mature, mainnet since 2020, no formal external standards body.
Relationships
How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.