Devcon Archive logo
Devcon Devconnect Forum Blog
  • Watch
  • Event
    Event: background logo
    • Devcon 8
    • Devconnect ARG
    • Devcon 7
    • Devcon 6
    • Devcon 5
    • Devcon 4
    • Devcon 3
    • Devcon 2
    • Devcon 1
    • Devcon 0
  • Categories
    Categories: background logo
    • Cryptoeconomics
    • Devcon
    • Developer Experience
    • Coordination
    • Core Protocol
    • Layer 2s
    • Real World Ethereum
    • Cypherpunk & Privacy
    • Security
    • Applied Cryptography
    • Usability
  • Playlists

Suggested

Loading results..

View all

About Devcon —

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.

An intensive introduction for new Ethereum explorers, a global family reunion for those already a part of our ecosystem, and a source of energy and creativity for all.

  • Watch
  • Devcon
  • Devconnect
  • Forum
  • Blog

Get in touch

devcon@ethereum.org

Subscribe to our newsletter

Crafted with passion ❤️ at the Ethereum Foundation

© 2026 — Ethereum Foundation. All Rights Reserved.

devcon8 / ream a new consensus clients journey to fusaka mainnet

  • YouTube
  • Details

Ream: A new consensus client's journey to Fusaka mainnet

Duration: 00:00:00

Speaker: Hans, Daniel

Type: CLS - EPF Talk

Expertise: Some familiarity with the topic

Event: Devcon 8

Date: Nov 2026

Fusaka changed how every consensus client handles blob data, peers and the beacon state. We took Ream through it in five steps, some with two tracks in parallel: 1. Closing the gap against the Fulu consensus-specs. 2. Full-custody PeerDAS, where blocks wait for their data, alongside range sync. 3. Kurtosis interop with other clients, alongside backfill sync. 4. Custody mode: storing only the columns a node is responsible for. 5. Following Ethereum mainnet, alongside running our own Hoodi validator. We'll share what broke on the way: spec mismatches like the fork digest that only showed up next to other clients; sync that held up on a devnet but stalled on a live network; validator APIs that external validator clients couldn't use, so our validators missed votes; and state processing that took seconds per mainnet block until we reworked it. If you build or maintain a consensus client, you'll leave with a practical picture of what it takes to make one work on post-Fusaka Ethereum.

Categories

Core ProtocolConsensusP2P