ENSIP-19 primary sources — 2026-05-13

What I reviewed

• ENS documentation:
  • https://docs.ens.domains/ensip/19
  • https://docs.ens.domains/ensip/
  • https://docs.ens.domains/ensip/3
  • https://docs.ens.domains/ensip/9
  • https://docs.ens.domains/ensip/10
  • https://docs.ens.domains/ensip/11
• ENS implementation / ecosystem surfaces:
  • https://github.com/ensdomains/ensips
  • https://github.com/ensdomains/address-encoder
  • https://raw.githubusercontent.com/ensdomains/address-encoder/master/README.md

Key takeaways from primary sources

• ENSIP-19 standardizes a real identity-verification loop, not just a nicer reverse record. A primary name is only valid if reverse resolution yields a candidate name and forward resolution of that name returns the same address bytes.
• The most useful architectural split is between default EVM-wide names and chain-specific names. ENSIP-19 turns a previously fuzzy wallet convention into explicit namespace and resolver policy.
• ENSIP-19 depends directly on earlier lower layers: ENSIP-9 supplies coin-typed address records, ENSIP-11 supplies chainId-to-coinType mapping, ENSIP-10 supplies wildcard resolution, and ENSIP-3 is the older Ethereum-only reverse-resolution baseline.
• The multichain-Ethereum section is where the real control surface appears. Registry-independent registrars, wildcard resolvers, and trustless verification for rollups become the practical machinery behind “what name should this address display?”
• The spec is unusually valuable because it is explicit about client-side risk. It tells clients to stop assuming that mainnet addresses or primary names should silently act as defaults across all chains, especially once smart contract accounts diverge by chain.
• The reverse namespace becomes a policy surface in its own right: addr.reverse, default.reverse, and [coinTypeAsHex].reverse each encode a different answer to the question of which identity should be canonical.

Specific source signals worth retaining

• ENSIP-19 is the best direct source for the two-phase verification algorithm, reverse-namespace derivation, default-address fallback rule, and deprecation guidance.
• ENSIP-3 is the best source for the earlier Ethereum-only reverse-resolution baseline that ENSIP-19 generalizes beyond.
• ENSIP-9 is the best source for coin-type-aware address lookup; ENSIP-11 is the best source for algorithmic EVM coin-type derivation; ENSIP-10 is the best source for wildcard-resolution context.
• The ENSIP index page is the best compact source for proposal status and family context.
• The address-encoder README is a useful implementation-side reminder that ENS multichain address handling already lives in shared libraries, which raises the stakes of ENSIP-19’s default-name assumptions.

Why this entry belongs in the corpus

• It isolates verified primary-name policy as its own layer beneath wallet/profile UX and above basic address lookup.
• It helps separate reverse naming, forward naming, default identity policy, and chain-specific identity policy instead of flattening them into one generic ENS feature.
• The durable insight is that multichain identity is governed not only by who owns a name, but by how clients decide which name should count as canonical on which chain and under which verification path.