Update: EIP-7951 (formerly EIP-7212), which introduces a precompile for secp256r1
curve, has been included in the upcoming Fusaka upgrade, tentative June 23, 2025. You can track its inclusion here.
This opens a fascinating design space for ENS. If this implementation lands on L1, no fundamental cryptographic blockers will remain for the following:
- WebAuthn + ENS login: Authenticate into WebAuthn-supported apps (email, banking, dapps) using ENS name—e.g. sign in as
yourname.eth
using Face ID or a YubiKey. - Onchain DNSSEC + ENS integration: Secure, verifiable domains backed by DNSSEC can be linked to ENS, enabling cross-chain and Web2 ↔ Web3 identity resolution.
- Enterprise ENS subnames: Issue
alice.company.eth
tied to a P256-secured device for passwordless access to internal tools, gated dapps, or multi-role DAOs. - IoT authentication with ENS: Use ENS to manage and verify identities of constrained devices (sensors, drones, routers) that rely on P256-based crypto stacks.
- Gov/NGO identity systems: Map national or organizational IDs to ENS in a way that respects existing infrastructure while unlocking composability across Ethereum.
- Unified identity layer: Reduce cognitive overhead from managing fragmented accounts—anchor all online presence to a single, sovereign ENS identity, verified across Web2 and Web3.
—
Special note to @ulerdogan and co., I express remorse for having called this initiative a red herring. Your conviction is inspiring, and I’ve learned not to underestimate the long arc of infrastructure work.
For a primer on what the secp256r1 precompile unlocks for Ethereum and ENS identity flows, check out Enabling Unified Identity Frameworks with P256 on Ethereum — m