Polkadot

P2P Protocol

Layer-0 multichain protocol enabling independent blockchains (parachains) to interoperate with shared security via a central relay chain. Features on-chain governance (OpenGov), cross-chain messaging (XCM), and nominated proof-of-stake consensus. Parachains maintain sovereignty while inheriting relay chain security.

Community

Links

Visit Community

Details

License

Open source — GPL/Apache 2.0; GitHub: github.com/paritytech/polkadot-sdk

Dev Status 🟢 Active

Dev Status Detail

Production — actively developed; Polkadot SDK released on stable quarterly cadence

Owner

Web3 Foundation (non-profit, Zug, Switzerland), founded by Gavin Wood, Peter Czaban, and Robert Habermeier; core development by Parity Technologies (London, UK)

Country

Switzerland / UK

Start Year 2016

Stack

Rust (primary); WebAssembly (Wasm) runtime; Polkadot SDK (formerly Substrate + Cumulus + Polkadot); BABE block production + GRANDPA finality gadget

Funding

ICO 2017 raised $144M; Web3 Foundation grants program; DOT on-chain treasury (OpenGov treasury)

Last Investigated Jul 1, 2026

Use Case Domains

Platform Evolution & Sovereignty

P2P Protocol Attributes

Origins

Created by Gavin Wood (Ethereum co-founder and former CTO) after leaving Ethereum in 2015 to pursue a more interoperable multi-chain architecture; whitepaper published 2016

Database

Relay chain state; parachain state managed independently per chain

Query Language

None native

Data Formats

SCALE codec; XCM message format

Collaborative Live Editing

Rich Text Editing

Mobile Support

Via wallets and parachain-specific apps; no native protocol-level mobile SDK

Web Support

Yes — via Polkadot.js and parachain-specific interfaces

Native Apps

Yes — Polkadot SDK for building chains; various wallet and staking apps

Terms

Apache 2.0 / GPL

Funds

Web3 Foundation grants program (open, 300+ projects funded globally); DOT treasury via OpenGov

Based On

Ethereum (conceptual origins; Gavin Wood co-founded both); BABE derived from Ouroboros Praos; NPoS consensus mechanism

P2P Architecture

Relay chain + parachain model; validators on relay chain verify parachain state transitions submitted by collators; nominators delegate stake to validators

Overlay Network

Relay chain serves as coordination and security layer; parachains connect to it via coretime allocation

Content Addressing

Partial — block hashes used for state verification; no IPFS-style content addressing

Local-First

E2EE

No native E2EE at protocol level

CRDTs Lib

Byzantine Fault Tolerance

Yes — GRANDPA finality gadget provides Byzantine fault-tolerant finality

Signature

Sr25519 (Schnorrkel); Ed25519; ECDSA

Permissions

Permissionless for validators (via NPoS staking) and parachain deployment (via coretime purchase with DOT)

Semantic Web Compatibility

Smart Contract

Yes — via parachains (e.g., Moonbeam for EVM-compatible smart contracts; ink!/PolkaVM for Wasm contracts)

Protocol Stack Position

Layer 0

Asset / Value Embedding

Yes — DOT native token for staking, governance, and coretime; parachain-native tokens; Asset Hub system parachain for multi-asset management

Protocol Maturity / Standardization

De Facto Standard — mainnet live since 2020; large active ecosystem; not submitted to formal standards body