Clients & Nodes

Client implementations and running them: why diversity protects the network, and how to operate a node or reach one through a provider.

458 talks

• Paying Nodes That Actually Execute: Proofs a Free-Rider Cannot Copy From a Peer
• Transcending Gossipsub
• devp2p, libp2p, ethp2p - Untangling Ethereum’s Networking Stack
• When the Network Shuts You Out: Measuring Resilience in Permissionless Networks
• AI security vulnerability scanning in Lighthouse
• A Yellow Paper you can run: an independent executable EVM spec in Lean 4
• FOCIL in Lighthouse
• Implementing EIP-8025 Optional Execution Proofs in Grandine
• EIP-7805 (FOCIL) Implementation in Erigon
• Pureth in Reth: SSZ Execution Blocks and Query Language
• 2D-Filtermaps in Reth
• EIP-8304: Trustless log and transaction index in Geth
• REST-SSZ Engine API for Lighthouse
• What can Ethereum learn from other networks?
• hs-libp2p: A Haskell Implementation of the libp2p Stack
• Light Client Backfill in Prysm
• What does it take to trust a transaction end to end?
• Grandine Lean Client Development
• Getting to Lean Ethereum
• Ethereum Is Decentralized. Your Access Isn’t.
• The 'Petabyte Chain' and how to survive it
• Running a Full Node and Staking on Free and Open Standard RISC-V Hardware
• SSZ Execution Blocks (EIP-7807) for Geth
• Ream: A new consensus client's journey to Fusaka mainnet