Ethereum
Protocolo P2P
Comunidade
Detalhes
Licença 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).
Status de Dev 🟢 Ativo
Proprietário No single owner — multiple independent client teams (Geth/EF, Nethermind, Besu/Hyperledger, Reth/Paradigm, Erigon) plus a broad open-source contributor base.
Órgão de Governança 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.
País N/A (globally distributed; Ethereum Foundation is Swiss-registered but doesn't control the protocol)
Ano de Início 2015
Stack Multi-client — Go (Geth), C# (Nethermind), Java (Besu), Rust (Reth), Go (Erigon); all implement the same EVM/consensus spec.
Financiamento 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.
Última Investigação 23 de ago. de 2026
Protocolo P2P Atributos
Origens Programmable blockchain / "world computer" concept, proposed by Vitalik Buterin in the 2013 Ethereum whitepaper.
Banco de Dados N/A (state trie, not a conventional database)
Linguagem de Consulta JSON-RPC for node queries; no query language for on-chain state beyond direct contract calls.
Formatos de Dados RLP (Recursive Length Prefix) encoding for transactions/blocks.
Edição Colaborativa em Tempo Real N/A
Edição de Texto Rico N/A
Suporte Móvel Via third-party wallet apps (MetaMask Mobile, etc.), not part of any single client.
Suporte Web Extensive — the dominant smart-contract platform for web3 dApps, via browser wallet extensions and JSON-RPC.
Aplicativos Nativos Node software ships as desktop/server binaries (all 5 major clients).
Termos Free, open-source; network gas fees paid to validators.
Fundos Ethereum Foundation's own treasury is publicly disclosed (multi-billion-dollar ETH holdings); individual client teams' funding varies.
Baseado Em Extends Bitcoin's blockchain/PoW model (pre-Merge) with a Turing-complete VM; post-Merge PoS design draws on Casper FFG research.
Arquitetura P2P Gossip network of full/light nodes (devp2p protocol); validators additionally participate in PoS consensus (attestations, block proposals) via the Beacon Chain consensus layer.
Rede de Sobreposição Global, permissionless.
Endereçamento por Conteúdo No (though IPFS is commonly used alongside Ethereum for off-chain data, it's a separate protocol).
Local-First N/A
Criptografia de Ponta a Ponta (E2EE) N/A
Biblioteca de CRDTs N/A
Tolerância a Falhas Bizantinas Yes — Casper FFG/LMD-GHOST PoS consensus (post-Merge), providing finality within ~2 epochs under honest-majority-stake assumptions.
Assinatura ECDSA (secp256k1) for transactions; BLS signatures for validator consensus messages.
Permissões Permissionless for transacting/deploying contracts; validating requires staking 32 ETH (or pooled staking).
Compatibilidade com a Web Semântica No, though many identity/credential standards (ERC-725, ERC-4337, did:ethr) are built on top.
Contrato Inteligente Yes — Turing-complete EVM, primary smart-contract execution environment for the broader Ethereum ecosystem (and many EVM-compatible chains).
Posição na Pilha de Protocolo Base-layer settlement + execution (Layer 1); Layer-2 rollups (Optimism, Arbitrum, etc.) build on top for scalability.
Incorporação de Ativo / Valor Native (ETH) plus a vast token ecosystem via smart contracts (ERC-20, ERC-721, etc.).
Maturidade / Padronização do Protocolo 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.