Decentralized DNS Monday — September 07 2026 Weekly Update

Weekly companion to Overview - Decentralized DNS, ENS, PKARR, GNS, Handshake, Namecoin, and related files. Covers Sep 1–7. Key themes: the ENS Labs × Immunefi audit competition closes Sep 14 (not Sep 22 as the Aug 31 weekly incorrectly stated) — T-7 days with 306 reports submitted by Aug 31 (20 confirmed, 56 under review); ICANN's Board met Sep 4–6 in Los Angeles with the New gTLD 2026 Round on the agenda, putting the mid-Sep Reveal Day date announcement on track for this week; ENS DAO activity spikes with five new forum threads Sep 1 alone (Newsletter #119, P-256 Precompile Migration impact report, ENSIP-28 Name Owned Accounts, ENSIP Stealth Address Resolution, ENSIP Text Record Attestations); the ENSv2 mainnet deployment clock now has a clean pre-launch checklist — audit close (Sep 14) → project remediation deadline (Sep 20) → results frozen (Sep 28) → mainnet deploy window opens; root KSK rollover is T-34 days with the Sep 4 ICANN Board meeting in LA producing fresh EMEA/APAC comms; Pubky ecosystem plateau confirmed — pkarr still at v8.0.0 (Aug 6), pubky-homeserver still at v0.11.0 (Aug 19), pubky-app still at v1.7.0 (Aug 13); Handshake PR #952 still frozen at May 11 activity, no new hsd release; DNS-AID draft-02 expires Nov 28 with no new draft yet.

TL;DR — This Week

• ENS Labs × Immunefi audit competition ENDS Sep 14 (correction to Aug 31 weekly's "~Sep 22" estimate). Per Immunefi's live program page, the full schedule is: competition Aug 18 → Sep 14 (11:00 UTC), project remediation deadline Sep 20, results frozen Sep 28, 48-hour dispute window to Sep 29, payment Oct 26, results published Oct 26. As of Aug 31: 306 reports submitted, 20 confirmed valid, 56 under review, 0 Critical/High reported public yet. Reward pool is dynamically tiered: $70K if a Critical is found, $50K if High, $30K if Medium/Low, $3K if none. Primary Pool $49K / All Stars $14K / Podium $7K. KYC required. Vault TVL $69,973.68 (1 USDC still in flight).
• ICANN Board LA workshop (Sep 4–6) had the New gTLD 2026 Round as a stated agenda item. Per the ICANN Aug 13 announcement, the Reveal Day date is scheduled to be announced in mid-Sep — this week is the natural window. CircleID's Sep post-close analysis confirms the pattern: ~1,300 net applications (≈300 below 2012), ~1,100 replacement strings filed (low-cost collision protection), Reveal Day itself expected in October. Track ICANN announcements this week for the specific Reveal Day date.
• ENS DAO ecosystem Sep 1 forum burst: (a) Newsletter #119 (Sep 1); (b) P-256 Precompile Migration Impact Report — realized Mar 9 → Jul 27 2026, saved 1.12B gas across all eligible DNS imports, 82.3% of what those imports would otherwise have cost, RIP-7212 fallback contract shaves 330k → 3.4k gas per P-256 verify (~100× reduction); (c) ENSIP-28 ENS Name Owned Accounts (Standards, Sep 2, 11 replies); (d) [RFC] Privacy-Preserving Names: ENSIP for Stealth Address Resolution] (7 replies, Sep 1) — the first stealth-address ENSIP, directly relevant to private-info-retrieval stack; (e) ENSIP: Text Record Attestations (Standards, Sep 1); (f) Voting Period Bulletin Term 7; (g) [Executable] SPP3 Marketplace RFP Award: Nomentum Labs (Grails)].
• ENS Labs Q3 progress report framing: "Q3 will involve completing the remaining security and audit work and reading v2 for final deployment. After v2 launches on mainnet Ethereum, the team is looking forward to a more experimental phase of product development around specific integrations and use cases." Two audit firms + Rhinestone formal verification remain the gating stack. The post-audit mainnet deploy window is now mechanical: close Sep 14 → fix Sep 20 → freeze Sep 28 → mainnet deploy after Oct 26 results publication.
• Pubky plateau CONFIRMED — no new tagged releases Aug 19 → Sep 7 (19 days). pkarr still at v8.0.0 (Aug 6); pubky-homeserver still at v0.11.0 (Aug 19); pubky-app still at v1.7.0 (Aug 13); pubky-nexus last commit Aug 13. Architecture docs PR #280 (Aug 11) remains the recent shipping artifact. The team is in SDK stabilization — pubky-sdk 0.9.1 (May 27) is the current stable.
• Root KSK rollover — T-34 days, ICANN EMEA/APAC webinar comms continuing per Sep 4 Board meeting. No delays; Oct 11 hard cutover still on. Jan 2027 old-key retirement.
• Handshake — no movement on PR #952 (still last-updated May 11); hns-rs still at v0.3.1 (Aug 23); no new hsd release. HNS market: ~$0.0017 (still -99.8% from ATH), modest recovery volume.
• DNS-AID quiet — draft-02 expires Nov 28, no new draft. Cloudflare "Agent Readiness" checker enforcement-of-draft-01 issue from Aug 24 weekly still unaddressed.

Deep dives

1. ENS Labs × Immunefi audit competition — T-7 days to close, Sep 14 not Sep 22

The Aug 31 weekly update estimated the competition closing ~Sep 22. It was wrong. Per the live Immunefi program page, the canonical schedule is:

The competition is "26d 20h remaining" as of Sep 7 capture. The scope is the new ENS App + ENS Explorer codebases (137,845 LOC per Immunefi). Tiered reward structure:

• A Critical is found → $70,000 USD pool (Primary $49K / All Stars $14K / Podium $7K)
• A High is found → $50,000 USD
• Medium or Low found → $30,000 USD
• No security vulnerability found (insights don't count) → $3K USD

USDC rewards on ETH, KYC required, Immunefi Vault-funded ($69,973.68 currently visible; 70K USDC in vault at 0x39befB5b7F778278Cc1d9Ee3a4F1e06CBA163293). The vault program funds the pool directly — there's no ENS Labs escrow step.

Findings state as of Aug 31: 306 reports submitted, 20 confirmed valid, 56 under review. Publicly visible confirmed findings include website/app findings (Aug 14 disclosures on the Immunefi page) — examples: SEC-MGR-008/SEC-MGR-011 development-only surfaces (debug route + hardcoded localhost SIWE + router devtools) shipped in production builds (High), R2-02 (Medium) Manager app lacks CSP/X-Frame-Options/Referrer-Policy/X-Content-Type-Options. These are app-layer findings, not contract-layer — consistent with the scope being ENS App + Explorer, not the ENSv2 contracts themselves (those were separately audited by two firms + Rhinestone formal verification per the Q3 report).

Cross-reference: ENS; see also Aug 31 weekly §"ENS Labs × Immunefi audit competition" (now requires date correction).

Operational gate sequence for ENSv2 mainnet: 1. Sep 14: competition closes (T-7 days) 2. Sep 20: ENS Labs completes remediation of all reported issues 3. Sep 28: results frozen 4. Sep 29: 48-hour dispute window closes 5. Oct 26: payments complete + results published 6. ENS’s 6 February 2026 plan places ENSv2 exclusively on Ethereum L1; Namechain development ceased.

The window between Sep 29 (dispute resolution) and Oct 26 (payment) is the mainnet-deploy decision gate. If results publish on Oct 26 with no Critical, the path to mainnet is essentially cleared. The ENS Forum thread "Building ENSv2: From Code to Coordination" (p-59259) remains the canonical roadmap.

2. ENS DAO governance Sep 1 burst — five threads, one newsletter, one report

The ENS DAO forum's "latest" page for Sep 1 is unusually dense — five new threads + the bi-weekly newsletter + voting bulletin. Catalogued:

(a) ENS DAO Newsletter #119 — 09/01/2026 (Newsletter, 23 views, 0 replies). Bi-weekly on Tuesdays at 11 AM ET. The release of Newsletter #119 sits exactly between the audit-competition window (Aug 18 → Sep 14) and the Term 7 voting period — a normal cadence beat, not an emergency.

(b) Report: Measuring the Impact of ENS's P-256 Precompile Migration (Ecosystem Discussion, 89 views, 1 reply, Sep 1). The headline data: 1.12B gas saved across all eligible DNS imports over the realized period Mar 9 → Jul 27 2026 — equal to 82.3% of what those imports would otherwise have cost. RIP-7212 fallback contract shaves P-256 verify from ~330k gas (Solidity fallback) to ~3.4k gas (precompile) — about a 100× reduction. The precompile was active on Ethereum L1 and key L2s by mid-2025; ENS DNSSEC imports are the biggest beneficiaries because P-256 ECDSA is what most DNSSEC chains actually use. For PKARR/DNSSEC-style key-rooted naming, this is the gas-cost argument for P-256-based identity (WebAuthn / passkeys / Secure Enclave) over secp256k1 — the same trade-off avalanche's ACP-204 makes.

(c) ENSIP-28: ENS Name Owned Accounts (Standards, 88 views, 11 replies, Sep 2). First seen as a Standards thread, now seeing discussion. Continues the ENSv2 contract refactor conversation — "name owned accounts" suggests a clean EOA-like interface for ENS names themselves, decoupling the holding account from the resolution process.

(d) [RFC] Privacy-Preserving Names: ENSIP for Stealth Address Resolution] (Standards, 236 views, 7 replies, Sep 1). The most cryptographically novel ENSIP in the batch. Stealth addresses per-address per-recipient unlinkable payment targets — a privacy primitive most associated with Monero and, recently, Ethereum (ERC-5564 / ERC-6538). An ENSIP for stealth-address resolution means a .eth name can resolve to a fresh per-transaction stealth address without leaking the recipient's primary wallet. This is the first time stealth addresses are reaching the naming layer. The relevance to PIR and the broader censorship-resistance stack is direct: a recipient's wallet becomes ephemeral on-chain, with the ENS name as the only stable identifier.

(e) ENSIP: Text Record Attestations (Standards, 25 views, 0 replies, Sep 1). A standard for cryptographic attestations attached to text records — likely signing pubkeys, capability attestations, or third-party claims. Connects to ENSIP-16 (DNSSEC), ENSIP-17 (optimistic record challenges), and the broader CCIP-Read verifier surface.

(f) Voting Period Bulletin — Term 7 (Meta-Governance voting, 91 views, 3 replies, Sep 1). Working group stewards Term 7 election cycle.

(g) [Executable] SPP3 Marketplace RFP Award: Nomentum Labs (Grails)] (Active Proposal, 94 views, 2 replies, Sep 1). SPP3 (Service Provider Program round 3) grant: Nomentum Labs / Grails for marketplace work. Continues the Blockful / JustaName service-provider trajectory.

(h) "SafeNotes Shutting Down — DAO-Wide" (24 views, 0 replies, Sep 1). ENS DAO infrastructure decommissioning note — the SafeNotes internal documentation/wiki tool being sunset is a routine operational cleanup.

Cross-reference: ENS; Overview - Decentralized DNS §"ENSv2"; Aug 31 weekly §"ENS Forum thread"; Aug 10 weekly §"ENS Next Era".

3. ICANN Board LA workshop + Reveal Day — announcement expected this week

The ICANN Board met Sep 4–6 in Los Angeles (per ICANN Board Chair Tripti Sinha's preview blog post), with the New gTLD Program 2026 Round on the agenda. The Aug 13 ICANN announcement stated Reveal Day's specific date would be announced in mid-September 2026, with publication no later than nine weeks after Aug 12 (≈ Oct 13).

CircleID's post-close analysis ("After the Close: What the 2026 gTLD Round Has Already Revealed", Kevin Murphy, ≈ early Sep) gives the post-cleanup numbers:

• ~1,300 net applications (≈300 below 2012 round's ~1,930)
• ~1,100 replacement strings filed (low-cost collision protection — applicants protect their primary strings by also filing variants at lower cost)
• The "more than 1,600" ICANN figure includes both primary and replacement-string applications; the net after admin check is ~1,300
• Reveal Day publication expected for October specifically (Lexology and CaptainDNS analysis agree with the ICANN ≤ Oct 13 hard deadline)

What to watch this week: ICANN announcement mid-Sep window is now open. The Reveal Day date is likely to drop between Sep 7 (post-Board-meeting) and Sep 14 (one week later). The ICANN Board meeting minutes + Chair blog follow-up are the earliest signal; the formal Reveal Day date announcement is the binding event.

Freedom-tech stakes: Reveal Day publishes the public portions of all applications passing Administrative Check — primary strings, variant strings, replacement strings, contention groups. The diff against Unstoppable Domains' 19+ application portfolio, ENS's .ens application, and Handshake's on-chain TLDs is the audit task. Any string that gets delegated to a competing applicant creates resolution ambiguity for existing Web3 name holders in every ICANN-resolving browser.

Key-rooted schemes are structurally immune to this collision pressure — PKARR, Tor .onion, GNS, Yggdrasil, cjdns all use a public key or petname as the root identifier and don't compete for ICANN string space.

Cross-reference: Unstoppable Domains (UD's 19+ applications); ENS (.ens gTLD application); Handshake (on-chain TLDs); Aug 31 weekly §"Reveal Day"; Aug 24 weekly §"ICANN 2026 round closure".

4. Pubky — 19-day shipping plateau confirmed, SDK stabilization phase

The Aug 31 weekly flagged a "shipping plateau" from Aug 19 → Aug 31. As of Sep 7, that plateau is now 19 days long. Tagged-release ledger (no new releases since):

This is a stable release-train phase, not abandonment. Three signals support that reading:

1. Architecture docs PR #280 (Aug 11) — committed after pkarr v8.0.0 landed, locking in the new resolver/publisher API surface for downstream integrators. This is the docs-pass-on-a-major-version move.
2. Migration guide for /priv events stream — PR #539 by @MCarlomagno in pubky-homeserver v0.11.0 (Aug 19). Documents a new ALPHA storage endpoint with breaking-changes semantics.
3. SDK internal refactor continuing — GrantManager (account-level grant listing/revocation), AuthState, PkarrError::Query/PkarrError::Resolve, get_homeserver_of — all visible in the v0.10.0 → v0.11.0 migration guide. The next SDK release (likely v0.10.0 stable post the alpha/beta) will consolidate this surface.

Why this matters operationally: Pubky is the most actively developed key-rooted naming stack (PKARR + homeserver + SDK + app + Nexus + Ring key manager). A 19-day release plateau for a project shipping ~2-3 versioned crates per month is normal — but the floor of "next release wave" is late September, after the ENSv2 audit closes (Sep 14) and the DNS-AID draft-02 review window ends (Nov 28). The hns-rs cohort release Aug 23 (Handshake) and iroh-pkarr-node-discovery v0.6.0 (Aug 6) are the broader ecosystem markers showing continued investment.

Cross-reference: PKARR (last updated Aug 24); Pubky (in 11-Identity); Aug 31 weekly §"Pubky — shipping plateau".

5. Root KSK rollover — T-34 days, EMEA/APAC comms continuing

The hard cutover date remains Oct 11, 2026. From Sep 7, that's T-34 days. The Sep 4–6 ICANN Board LA workshop reinforced the timeline. New this week:

• ICANN EMEA Webinar Series — KSK Rollover 2026 continues with the Aug 26 webinar (Isaac Saaki, MTN; Yazid Akanho, Technical Engagement Manager; Ulrich Wisser, ICANN Europe Technical Engagement Manager). 12:00–13:00 UTC. Covering what to expect, how to check resolvers, and what operators should prepare for.
• ICANN x.com reminder posts (Sep 1 window): "On 11 October 2026, the new trust anchor, KSK-2024, is planned to be used to sign the root zone for the first time. Are your DNSSEC-validating resolvers prepared?"
• Old key retires Jan 2027 (dual-signing period ends).

For Daemon operators (per Aug 31 weekly, still relevant): any self-sovereign validating resolver — pkdns instances, GNS-to-DNS proxies, hand-rolled unbound/knot/BIND 9.11+ resolvers — must confirm KSK-2024 (Key Tag 38696) in the trust-anchor set before Oct 11. Verification: delv @resolver . DNSKEY against IANA trust anchors.

Cross-reference: Overview - Decentralized DNS §"DNSSEC"; Aug 31 weekly §"Root KSK rollover"; Aug 24 weekly §"KSK rollover T-48 days".

6. Handshake — PR #952 still frozen, hns-rs stable, market flat

PR #952 "Handshake Hard Fork — Arbitrary DNS Records, Supply Reallocation, and Tree Interval" has not moved this week — last activity May 11, 2026 in the PR thread. The CI workflow runs (handshake-org/hsd/actions) still show the build artifact from Jan 21, 2025 (Build #690). The hard-fork conversation remains on three tracks:

1. Reorg safety at every-block tree commits (consensus concern)
2. Foundation as funding vehicle (governance concern)
3. RAW-record enablement as the actual DNS-on-chain unlock (protocol concern)

No merges, no new commits, no new sub-discussions visible this week.

hns-rs v0.3.1 (Aug 23) remains the latest release. No v0.3.2 or v0.4.0 tagged this week. The Rust-native protocol stack is the forward-looking implementation; the legacy Node.js hsd (the canonical full-node daemon) has no new release either.

HNS market: ~$0.0017 (CoinGecko, Sep 7 capture); still -99.8% from ATH; modest recovery volume from the ATL ($0.001139 Jul 8). The 2nd halving (Jul 22 2026, 1000 HNS/block) is now 47 days behind us with no new token-economics developments.

Cross-reference: Handshake (hns-rs 0.3.1 cohort; PR #952 hard-fork; HNS market; Namecheap exited HNS Jun 10).

7. DNS-AID / stealth ENSIP — quiet week, but adjacent ENSIP signals a privacy turn

DNS-AID draft-02 (Mozley/Williams/Sarikaya/Schott/Damick; May 27 2026) expires Nov 28, 2026. No new draft has been posted this week. The Cloudflare "Agent Readiness" DNS-AID checker enforcement-of-draft-01 issue flagged in the Aug 24 weekly is still unaddressed.

Adjacent signal: the ENSIP Stealth Address Resolution RFC (Sep 1) is a parallel track that touches the same "agent-to-agent identity discovery" problem space DNS-AID addresses, but at the naming layer rather than the DNS record layer. Both efforts converge on the same long-term question: when agents are communicating, how does one agent discover the canonical identity of another without leaking metadata? DNS-AID's answer is _agents.<domain> TXT records with DNSSEC validation. The ENSIP Stealth Address Resolution answer is ENS name → ephemeral stealth address → unlinkable payment target. The two approaches are complementary — DNS-AID for capability advertisement, stealth ENS for transaction-level unlinkability.

A third related IETF draft is draft-nemethi-aid-agent-identity-discovery-00 (Balazs Nemethi, last updated Mar 16 2026) — a non-DNS agent identity scheme. Status: I-D Exists, no stream defined. Not actively shipping.

Cross-reference: Aug 24 weekly §"DNS-AID"; Aug 3 weekly §"DNS-AID — naming layer for the agentic web"; Identity (Nostr/Pubky stealth-address-equivalent features).

8. GNUnet / GNS — 0.29.0 holds, no point release

GNUnet 0.29.0 (released Aug 20 2026 per the official news page and Wikipedia infobox) remains the latest. No 0.29.1 point release this week. The Aug 20 release notes call out:

• Major version → protocol break with 0.28.x. All peers must upgrade in lockstep.
• Transport subsystem regressions addressed.
• General stability fixes.

The GNS protocol surface is unchanged at the spec level — the protocol break is in transport. GNS lookup-privacy story is unchanged: queries against the GNS DHT are encrypted and unlinkable to the queried name. The strongest of the decentralized-naming schemes for lookup-privacy, but the smallest deployed base (single-digit thousand active nodes per rough community estimates).

Cross-reference: GNS; Overview - Decentralized DNS §"GNS"; Aug 31 weekly §"GNS".

9. Namecoin — Core 31.1 unchanged, no new release

Namecoin Core 31.1 (the Bitcoin Core rebased version, last release ~Jul 13 2026) is still the latest. The Bitcoin Core 31.1 release was Sep 5 2026 (per bitcointalk announce thread) — Namecoin Core follows Bitcoin Core with a rebase pass, so a Namecoin Core 31.2 rebasing on Bitcoin Core 31.1 is plausible in the next 4-6 weeks.

Operational status: .bit resolution via ncp11 + ncdns2 + ncgencert stack still works for browsers that accept the certs. The Namecoin homepage lists FOSDEM 2026 (Jan 31 – Feb 1, Brussels) and 39C3 as the recent conference presence; no new conference mentions for fall 2026.

Cross-reference: Namecoin; Aug 31 weekly §"Namecoin Core 31.1".

Calendar (next 4 weeks)

Evidence at a glance

Freedom-tech takeaways

1. The ENS audit closes Sep 14, not Sep 22. Researchers holding valid findings still have T-7 days to submit via the Immunefi portal. Daemon operators should verify any ENS Labs contact claiming audit-related work references the canonical Immunefi competition page (immunefi.com/audit-competition/audit-competition-ens) and the 0x39befB5b7F778278Cc1d9Ee3a4F1e06CBA163293 vault address.
2. ENSv2 mainnet is now on a mechanical clock. Sep 14 close → Sep 20 fix → Sep 28 freeze → Sep 29 dispute → Oct 26 publish → mainnet deploy. If the Oct 26 results publish with no Critical, ENSv2 contracts go to mainnet inside Q4. The window between Oct 26 and Q4-end is the mainnet deploy window.
3. ICANN Reveal Day announcement is this-week expected. The Sep 4–6 Board LA workshop was the staging event; the ICANN-specific announcement should land between Sep 7 and Sep 14. When it does, the diff against UD's portfolio + ENS's .ens + Handshake's on-chain TLDs is the audit task.
4. Stealth-address ENSIP is a signal that privacy-by-default is now in the naming layer. The Sep 1 RFC for Stealth Address Resolution is the first time the stealth-address primitive (Monero / ERC-5564) is being elevated to an ENS standard. For Daemon identity work, this opens the door to ENS-fronted unlinkable payment targets — a recipient's .eth name resolves to a fresh stealth address per transaction, breaking chain analytics without breaking the human-meaningful identifier.
5. P-256 precompile data is the gas argument for WebAuthn/Passkey-native identity. 1.12B gas saved across ENS DNS imports → P-256 is the right curve for DNSSEC-anchored identity on Ethereum. PKARR's Ed25519 choice is still correct (no DNSSEC use case), but any future ENSIP for hardware-key-backed identity should use P-256 not secp256k1.
6. Pubky release plateau is a stabilization phase, not abandonment. 19 days without a tagged release from a project that ships ~2-3 crates per month is normal. The next release wave is most likely late September, after the ENSv2 audit closes.
7. Oct 11 KSK rollover is the operational deadline. T-34 days. Daemon operators must verify KSK-2024 (Key Tag 38696) in trust-anchor set before Oct 11 via delv @resolver . DNSKEY against IANA trust anchors. Self-sovereign infrastructure (pkdns, GNS-to-DNS proxies, unbound/knot/BIND 9.11+ resolvers) is the failure surface.
8. Handshake's hns-rs 0.3.1 cohort is the only shipping line. PR #952 is a long-running conversation thread; the Rust protocol stack is the operational reality. Until a new hsd or hns-node-rs mainnet canary appears, the HNS "uncensorable DNS-on-chain" story is at v0.3.1 protocol-stack maturity.

Cross-cutting

• Overview - Decentralized DNS — comparative landscape; ENSv2 timeline; KSK rollover comms.
• ENS — ENSv2 mainnet audit window closes Sep 14 (corrected from Aug 31 weekly); Security Council activated Jul 21; stay-on-L1 (Feb 2026); Turkey adoption (Jun 2026); .ens gTLD application; Next Era Foundation (Aug 9); P-256 precompile impact (Sep 1); ENSIP-28 (Sep 2); Stealth Address Resolution RFC (Sep 1); Text Record Attestations ENSIP (Sep 1); Newsletter #119 (Sep 1).
• PKARR — v8.0.0 (Aug 6); pubky-homeserver v0.11.0 (Aug 19); pubky-app v1.7.0 (Aug 13); architecture docs PR #280 (Aug 11); 19-day release plateau; iroh-pkarr-node-discovery v0.6.0 (Aug 6).
• Pubky (in 11-Identity) — ecosystem overview; identity + data stack on PKARR.
• Handshake — hns-rs 0.3.1 cohort (Aug 23); PR #952 hard-fork (open since March); HNS market +34.3% 30d; Namecheap exited HNS Jun 10.
• GNS — GNUnet 0.29.0 (Aug 20); protocol break with 0.28.x.
• Namecoin — Core 31.1 (Jul 13); no new release this week.
• Mesh & Off-Grid Naming — Yggdrasil, cjdns, Briar (mesh layer adjacent to decentralized DNS).
• Overlay Naming - Tor .onion and I2P — operator-confidentiality story; structurally immune to ICANN collision.
• Unstoppable Domains — cautionary; 19+ application portfolio intersecting with ICANN collision review.
• MOC - Censorship Resistance — naming as one layer of the stack; stealth ENSIP relevant here.
• Identity — Nostr/Pubky stealth-address-equivalent primitives; ENSIP Stealth Address Resolution RFC.
• Glossary — DNS, ENS, Handshake, GNS, PKARR, petname, Zooko's triangle, Ed25519, P-256, RIP-7212, DNSSEC, KSK, RFC 5011.

Primary sources

• ENS is staying on Ethereum, 6 February 2026