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 / hs libp2p a haskell implementation of the libp2p stack

  • YouTube
hs-libp2p: A Haskell Implementation of the libp2p Stack preview
  • Details

hs-libp2p: A Haskell Implementation of the libp2p Stack

Duration: NaN:NaN:NaN

Speaker: Shouki Tsuda

Type: Lightning Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

Every Ethereum node reaches peers through libp2p: multiaddr, Noise, Yamux, Identify, Kademlia DHT, GossipSub. Yet this layer rests on a few implementations; when two read an underspecified spec corner differently, peers fail to connect or silently drop messages — a systemic risk with no owner. I built the full libp2p stack independently in Haskell — TCP, Noise XX, Yamux, multistream-select, Switch, Identify, Ping, Kademlia DHT, GossipSub — with 547 unit, property, and end-to-end tests, and joined libp2p/unified-testing to interop with other libp2p implementations. A layer-by-layer tour of Ethereum's p2p stack; the concrete spec ambiguities a fresh, strongly-typed implementation surfaces that incumbents absorbed as folklore; how cross-client interop keeps the network coherent; and why implementation diversity at the networking layer — not just the client layer — is a resilience and censorship-resistance property.

Categories

DecentralizationP2P