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 / designing for irreversibility lessons from shipping ensv2

  • YouTube
Designing for Irreversibility: Lessons from Shipping ENSv2 preview
  • Details

Designing for Irreversibility: Lessons from Shipping ENSv2

Duration: NaN:NaN:NaN

Speaker: Makoto Inoue, workemon.eth

Type: Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

ENSv2 replaces the flat ENS registry with hierarchical registries, shipping on L1 while millions of v1 names keep working. There is no undo: names are user-owned assets, and a bad deploy or design flaw is permanent. This talk covers how that constraint shaped three layers of the system. Protocol: token IDs regenerate whenever a name's permissions change or it is re-registered, so a seller can't list a name on a marketplace and quietly strip its roles before sale. Revoking a single role makes a name soulbound. Accounts: users get deterministic smart accounts with owner-derived salts, so funds sent to a counterfactual address are safe because the derivation itself is the security model. We also cover spoofing bugs we found and fixed. Process: phased runbooks, resumable deploys, and full dress rehearsals on Sepolia, including real incidents they caught. Attendees leave with a practical checklist for designing, auditing, and shipping systems where mistakes can't be rolled back.

Categories

IdentityAccount AbstractionSecurity