Devcon Archive logo
Devcon Devconnect Forum Blog
  • Watch
  • Event
    Event: background logo
    • Devcon 7
    • Devcon 6
    • Devcon 5
    • Devcon 4
    • Devcon 3
    • Devcon 2
    • Devcon 1
    • Devcon 0
    • Devconnect ARG
  • 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 / epf project presentation rest ssz engine api for lighthouse

  • YouTube
EPF Project Presentation: REST-SSZ Engine API for Lighthouse preview
  • Details

EPF Project Presentation: REST-SSZ Engine API for Lighthouse

Duration: NaN:NaN:NaN

Speaker: Sameer Agarwal

Type: CLS - EPF Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

Every slot, the consensus layer drives the execution layer over the Engine API by importing blocks, updating the head, producing payloads, and fetching blobs. It sits on the critical path for block propagation and validation timing and it runs on JSON-RPC, which has inefficiencies such as doubled wire size from hex-encoding, and repeated encoding and decoding between SSZ and JSON in consensus clients, forcing the node to spend additional bandwidth, CPU, and memory thereby adding latency to every slot. I am implementing the REST-SSZ Engine API in Lighthouse based on the [spec](https://github.com/ethereum/execution-apis/pull/793) where REST-SSZ will be the primary transport with JSON-RPC acting as the fallback. The talk will cover redesign demands on the consensus clients set out in the spec, changes that have landed in the spec since the EPF project proposal creation, and REST-SSZ vs JSON-RPC results from client interop on local and Glamsterdam devnet results.

Categories

Core Protocol