Ethereum

Protocolo P2P

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").

Comunidad
Enlaces
Visitar Sitio Web Ver Detalle Económico Sugerir una corrección

Detalles

Licencia 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).
Estado de Desarrollo 🟢 Activo
Propietario No single owner — multiple independent client teams (Geth/EF, Nethermind, Besu/Hyperledger, Reth/Paradigm, Erigon) plus a broad open-source contributor base.
Órgano de Gobierno 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)
Año de Inicio 2015
Stack Multi-client — Go (Geth), C# (Nethermind), Java (Besu), Rust (Reth), Go (Erigon); all implement the same EVM/consensus spec.
Financiamiento 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 Investigación 23 ago 2026

Dominios de Caso de Uso

Evolución de Plataformas y Soberanía

Protocolo P2P Atributos

Orígenes Programmable blockchain / "world computer" concept, proposed by Vitalik Buterin in the 2013 Ethereum whitepaper.
Base de Datos N/A (state trie, not a conventional database)
Lenguaje de Consulta JSON-RPC for node queries; no query language for on-chain state beyond direct contract calls.
Formatos de Datos RLP (Recursive Length Prefix) encoding for transactions/blocks.
Edición Colaborativa en Vivo N/A
Edición de Texto Enriquecido N/A
Soporte Móvil Via third-party wallet apps (MetaMask Mobile, etc.), not part of any single client.
Soporte Web Extensive — the dominant smart-contract platform for web3 dApps, via browser wallet extensions and JSON-RPC.
Aplicaciones Nativas Node software ships as desktop/server binaries (all 5 major clients).
Términos Free, open-source; network gas fees paid to validators.
Fondos Ethereum Foundation's own treasury is publicly disclosed (multi-billion-dollar ETH holdings); individual client teams' funding varies.
Basado En Extends Bitcoin's blockchain/PoW model (pre-Merge) with a Turing-complete VM; post-Merge PoS design draws on Casper FFG research.
Arquitectura P2P Gossip network of full/light nodes (devp2p protocol); validators additionally participate in PoS consensus (attestations, block proposals) via the Beacon Chain consensus layer.
Red de Superposición Global, permissionless.
Direccionamiento por Contenido No (though IPFS is commonly used alongside Ethereum for off-chain data, it's a separate protocol).
Local-First N/A
Cifrado de Extremo a Extremo (E2EE) N/A
Biblioteca de CRDTs N/A
Tolerancia a Fallos Bizantinos Yes — Casper FFG/LMD-GHOST PoS consensus (post-Merge), providing finality within ~2 epochs under honest-majority-stake assumptions.
Firma ECDSA (secp256k1) for transactions; BLS signatures for validator consensus messages.
Permisos Permissionless for transacting/deploying contracts; validating requires staking 32 ETH (or pooled staking).
Compatibilidad con la 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).
Posición en la Pila del Protocolo Base-layer settlement + execution (Layer 1); Layer-2 rollups (Optimism, Arbitrum, etc.) build on top for scalability.
Incorporación de Activos/Valor Native (ETH) plus a vast token ecosystem via smart contracts (ERC-20, ERC-721, etc.).
Madurez del Protocolo / Estandarización 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.