Ethereum

P2P Protocol

A programmable, smart-contract-capable blockchain protocol. Unlike Bitcoin's narrow scripting, Ethereum runs a Turing-complete virtual machine (the EVM), enabling arbitrary decentralized applications. Multiple independent client implementations exist (Geth, Nethermind, Besu, Reth, Erigon) that must conform to the same consensus rules, developed through the Ethereum Improvement Proposal (EIP) process — informal rough consensus among client teams, researchers, and the Ethereum Foundation, not a foundation directive. Transitioned from Proof-of-Work to Proof-of-Stake in September 2022 ("the Merge").

Community
Links
Visit Website View economic detail Suggest an edit

Details

License Multi-client, no single license — reference client (Geth) is LGPL-3.0/GPL-3.0 dual; other major clients use their own licenses (Besu Apache-2.0, Nethermind LGPL-3.0, Reth MIT/Apache-2.0 dual).
Dev Status 🟢 Active
Owner No single owner — multiple independent client teams (Geth/EF, Nethermind, Besu/Hyperledger, Reth/Paradigm, Erigon) plus a broad open-source contributor base.
Governing Body None with unilateral authority — the EIP process is community rough-consensus; the Ethereum Foundation (Swiss nonprofit) funds research/development but does not control protocol changes unilaterally.
Country N/A (globally distributed; Ethereum Foundation is Swiss-registered but doesn't control the protocol)
Start Year 2015
Stack Multi-client — Go (Geth), C# (Nethermind), Java (Besu), Rust (Reth), Go (Erigon); all implement the same EVM/consensus spec.
Funding Ethereum Foundation grants/research funding; individual client teams also receive separate funding (e.g. Reth from Paradigm, a VC firm) — funding is genuinely distributed across multiple independent organizations, not centralized.
Last Investigated Aug 23, 2026

Use Case Domains

Platform Evolution & Sovereignty

P2P Protocol Attributes

Origins Programmable blockchain / "world computer" concept, proposed by Vitalik Buterin in the 2013 Ethereum whitepaper.
Database N/A (state trie, not a conventional database)
Query Language JSON-RPC for node queries; no query language for on-chain state beyond direct contract calls.
Data Formats RLP (Recursive Length Prefix) encoding for transactions/blocks.
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Via third-party wallet apps (MetaMask Mobile, etc.), not part of any single client.
Web Support Extensive — the dominant smart-contract platform for web3 dApps, via browser wallet extensions and JSON-RPC.
Native Apps Node software ships as desktop/server binaries (all 5 major clients).
Terms Free, open-source; network gas fees paid to validators.
Funds Ethereum Foundation's own treasury is publicly disclosed (multi-billion-dollar ETH holdings); individual client teams' funding varies.
Based On Extends Bitcoin's blockchain/PoW model (pre-Merge) with a Turing-complete VM; post-Merge PoS design draws on Casper FFG research.
P2P Architecture Gossip network of full/light nodes (devp2p protocol); validators additionally participate in PoS consensus (attestations, block proposals) via the Beacon Chain consensus layer.
Overlay Network Global, permissionless.
Content Addressing No (though IPFS is commonly used alongside Ethereum for off-chain data, it's a separate protocol).
Local-First N/A
E2EE N/A
CRDTs Lib N/A
Byzantine Fault Tolerance Yes — Casper FFG/LMD-GHOST PoS consensus (post-Merge), providing finality within ~2 epochs under honest-majority-stake assumptions.
Signature ECDSA (secp256k1) for transactions; BLS signatures for validator consensus messages.
Permissions Permissionless for transacting/deploying contracts; validating requires staking 32 ETH (or pooled staking).
Semantic Web Compatibility No, though many identity/credential standards (ERC-725, ERC-4337, did:ethr) are built on top.
Smart Contract Yes — Turing-complete EVM, primary smart-contract execution environment for the broader Ethereum ecosystem (and many EVM-compatible chains).
Protocol Stack Position Base-layer settlement + execution (Layer 1); Layer-2 rollups (Optimism, Arbitrum, etc.) build on top for scalability.
Asset / Value Embedding Native (ETH) plus a vast token ecosystem via smart contracts (ERC-20, ERC-721, etc.).
Protocol Maturity / Standardization Mature, de facto standard — formal EIP process with a defined lifecycle (Draft to Review to Last Call to Final), 10+ years of continuous operation, second-largest blockchain by market cap and developer activity.