Weekly companion to Overview - Decentralized DNS, ENS, PKARR, GNS, Handshake, Namecoin, and related files. Covers Sep 15–21. Key themes: the Pubky ecosystem ends its release plateau with two tag releases in 7 days — pubky-app v1.10.0 (Sep 18, breaking 32-day plateau since v1.7.0 Aug 13) and pubky-app v1.9.0 (Sep 17) sitting immediately behind it, and pubky-homeserver v0.12.0 (Sep 14 09:52 — just after the Sep 14 weekly closed; we missed this one) ending a 26-day plateau since v0.11.0 Aug 19; ENS Labs shipping the most ambitious DAO weekly content of Q3 — ENS Newsletter #120 (Sep 15) with the ENS token-transparency filing, ENS as Registry Layer for Tokenized Assets blog, One-Click Registration, Name Activity Notifications, and a Blockful analysis identifying premium sales as the second revenue pillar ($113K in August after 3 months of growth); ENSIP-31: Payment Preferences (Sep 17, Unruggable / nxt3d) is the first ENSIP of Q3 to tackle recipient-side multi-chain routing at the protocol layer; ICANN TSG public comment on gTLD Integrations with Alternative Naming Systems closes TODAY Sep 21 — the single highest-signal policy event for the decentralized-DNS stack in 2026 because it is the only formal ICANN venue currently open to specifically address blockchain/alt-naming coexistence with the gTLD root; root KSK rollover T-20 days to Oct 11; Endowment NAV reaches $93M (Steakhouse August report); ENSv2 plugin for MetaMask Agent Wallet v0.8.0 shipped (Sepolia ENSv2 resolution, ERC-8004 agent identity); ENS Labs × Immunefi audit competition closed Sep 14 11:00 UTC on schedule — vault TVL $69,981.17 (Sep 21, essentially unchanged; competition is over); pkarr still v8.0.1 (Aug 31) with dependabot-only trunk commits Sep 18; hns-rs v0.4.1 (Sep 1) still the only release in the v0.4 line; hsd still dormant Aug 22 2025 >1y.
TL;DR — This Week
- pubky-app v1.10.0 (Sep 18) + v1.9.0 (Sep 17) + pubky-homeserver v0.12.0 (Sep 14) — three Pubky tagged releases in 7 days, ending the Aug 13/19 plateau the prior two weeklys were tracking. The Sep 14 weekly file was written before v0.12.0 landed and missed it; this W39 update catches up. v1.10.0 contains the v1.10.0/v1.9.0 workstream (45+ PRs, dominant author:
talosmachinaandsecondl1ght, focused on the PWA service worker, OAuth completion, character-limit UX, the undo on reposts, and the cypress e2e utf-16 limit match). v0.12.0 contains the v0.12.0 workstream (Docker default flip to homeserver, SDK two-stage auth flow publicly available, PKARR-relay republishing, rate-limit sort, broken-test runner fix). This is a substantive release cluster — not just patches. See §3. - ENSIP-31: Payment Preferences (Sep 17, ENS Development, 0 replies) — author nxt3d (Unruggable Labs); draft PR ensdomains/ensips#87. Uses ENSIP-24 data records with key
payment-preference[<multichainTokenHash>]. Recipients publish an ordered, token-specific chain preference list; wallets read before resolving the receiving address. Open question: how to fingerprint a multichain token — symbols aren't canonical, addresses are per-chain. This is the first ENSIP in 2026 to standardize recipient-side routing intent at the protocol layer. See §4. - ICANN TSG public comment on gTLD Integrations with Alternative Naming Systems closes Sep 21 (TODAY) — only formal ICANN venue open in Q3 2026 specifically addressing blockchain/alt-naming coexistence with the gTLD root. This is the policy event that will shape whether
.eth,.crypto,.x,.bit,.wallet, ENS subdomains, Handshake TLDs, etc., can be referenced from gTLD governance as "compatible". Public comment track is the only input mechanism. See §5. - ENS DAO Newsletter #120 (Sep 15) — substantively the most DAO-content-rich newsletter of Q3. Highlights: ENS token-transparency filing (Blockworks, investor-protection: "no dividend or revenue-distribution rights"); ENS as Registry Layer for Tokenized Assets (hierarchical-registries pitch to issuer ecosystem); One-Click Registration (production); Name Activity Notifications (live in App Beta) — directly addresses the user-research finding "people are afraid of losing control of their names"; ensjs PR #377 points Sepolia at the clean hackathon testnet deployment; DNSSEC contracts PR #572 (adraffy) stores ancestor inceptions onchain per
(node, type)withgetInception(name, type)getter +InceptionChangedevent (the change Sepolia has been waiting for to make DNSSEC import trust-anchored, not oracle-dependent); deploy script bug fix PR #573 (hiddentao) routes .eth-resolver-setting throughRegistrarSecurityController; docs PR #589 adds.lockerto the custom-TLD list. Endowment NAV $93M, Steakhouse August slides. Premium sales $113K in August (3-month rising trend), Blockful September delegate-incentive pool 8K ENS. See §6. - ENSv2 MetaMask Agent Wallet plugin v0.8.0 (Sep 15, estmcmxci) — adds Sepolia ENSv2 resolution, registration, records, primary names, and ERC-8004 agent identity to the MetaMask Agent Wallet CLI. This is the first ENSv2 SDK path through the MetaMask Agent Wallet surface (Sepolia only — mainnet blocked on audit close). See §7.
- ENS Labs × Immunefi audit competition CLOSED Sep 14 11:00 UTC, no overrun. Post-close schedule holds: Sep 20 = ENS deadline to resolve all submitted reports; Sep 28 = results frozen; Sep 29 = final 48-hour dispute window closes; Oct 26 = payment + public results publication. Vault TVL $69,981.17 Sep 21 (vs $69,989.29 Sep 14) — declined $8 over the week, consistent with the competition being over (no more researcher inflow to top up). Public findings state (306 reports / 20 confirmed / 56 under review as of Aug 31) is unchanged on the public view; the actual triage is internal until Oct 26 publication. See §1.
- Root KSK rollover T-20 days to Oct 11, 2026 hard cutover; old-key retirement Jan 2027. ICANN Board LA workshop (Sep 4–6) approved resolutions published Sep 8 (
approved-resolutions-special-meeting-of-the-icann-board-06-09-2026-en). Reveal Day announcement window is the ICANNWiki formal "no later than 9 weeks after Aug 12 close" → Oct 14 as upper bound (still no separate Reveal Day date confirmed publicly as of Sep 21). See §2. - DNS-AID draft-02 still the current (no new draft, expires Nov 28 2026). draft-mozleywilliams-dnsop-dnsaid-02 is the canonical reference; dns-aid-core reference implementation at v0.4.8+ supports SVCB/SVCB custom parameters + DNSSec. The Cloudflare Agent-Readiness checker from Aug 24 still enforces draft-01 expectations without acknowledging the breakage. Watch for any cut before Nov 28 expiry. Stale. See §8.
- GNUnet / GNS — no new release since 0.29.0 (Aug 20). No new release; experimental software. Namecoin — no Namecoin Core tag since nc31.1 (Bitcoin Core upstream sync continues). hsd (handshake-org/hsd) — last commit 2025-08-22, no v3.x tag; only hns-rs is shipping in the Handshake ecosystem. See §9.
Deep dives
1. ENS Labs × Immunefi audit competition — closed Sep 14, post-close window now in flight
Status as of Sep 21: competition ended on schedule Sep 14 11:00 UTC. No extension, no post-close complications in the public record. Schedule now in the resolution phase:
| Milestone | Date | Status |
|---|---|---|
| Announcement | Aug 10, 2026 | ✅ done |
| Launch | Aug 18, 2026 | ✅ done |
| Competition ends | Sep 14, 2026 11:00 UTC | ✅ closed on schedule |
| Project deadline to resolve all reports | Sep 20, 2026 | 🔴 today/yesterday — ENS applied by deadline (Sunday) |
| Results frozen and calculated | Sep 28, 2026 | pending |
| Final 48-hour dispute window | Sep 29, 2026 | pending |
| Payment complete | Oct 26, 2026 | pending |
| Results published | Oct 26, 2026 | pending |
Vault TVL $69,981.17 Sep 21 (was $69,989.29 Sep 14; $69,986.98 Sep 7; $69,973.68 Aug 31) — declined $8 since Sep 14, consistent with the competition being closed and no researcher-side activity. The "70K USDC target" was not quite reached but the gap is within operational variance.
Public findings state (Aug 31) is unchanged on the public view: 306 reports / 20 confirmed valid / 56 under review. The actual triage list has been internal since Sep 14. The public counters will not refresh until Oct 26 publication.
ENS Labs Q3 framing (per Sep 7 / Sep 14 weeklys): "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." Sep 20 = project deadline to resolve = the milestone where Q3 framing either lands or slips to Q4.
Operational gate sequence from here: 1. ✅ Sep 14 — competition closed on schedule 2. 🔴 Sep 20 — ENS Labs resolved all Critical/High/Medium/Low reports (deadline was yesterday; outcome not publicly posted) 3. Sep 28 — results frozen and calculated (Immunefi triage complete) 5. Sep 29 — final 48-hour dispute window closes 6. Oct 26 — payment + public results publication 7. After Oct 26 — ENSv2 mainnet deploy window opens (separate ENS Labs + DAO governance go/no-go)
Cross-reference: ENS; Decentralized DNS Monday — September 14 2026 Weekly Update (Sep 14 closure date correction); Sep 7 weekly (closing schedule published).
2. Root KSK rollover — T-20 days, Reveal Day Oct 14 upper bound
T-20 days to Oct 11, 2026 KSK-2024 cutover; old-key retirement Jan 2027.
Recent comms:
- Sep 6 ICANN Board meeting approved resolutions published Sep 8 (approved-resolutions-special-meeting-of-the-icann-board-06-09-2026-en). Includes Universal Acceptance Expert Working Group Guidelines (final), NextGen@ICANN88, 2027 NomCom input.
- Sep 9 ICANN blog "Chair's Blog: September Board Workshop Preview" (Sep 2, with the Sep 4–6 LA workshop agenda) confirmed the Board received an update on the New gTLD Program 2026 Round; "the 15-week application submission period closed on 12 August 2026, marking a significant milestone."
- Sep 8 fyI email to the GNSO Council lists two relevant public-comment deadlines:
- TSG on gTLD Integrations with Alternative Naming Systems — closes Sep 21 (today)
- DNS Abuse Mitigation PDP 1 Initial Report — closes Sep 28
- ICANNWiki Reveal Day formal schedule: "no later than 9 weeks following close of application submission period" — close was Aug 12 → 9 weeks = Oct 14 is the upper bound. The mid-Sep window for ICANN's separate Reveal Day date announcement has closed without one; if ICANN meets the Oct 14 ceiling, expect an announcement in the next ~3 weeks.
Critical post-rollover fact for the decentralized-DNS stack: DNSSEC-validating resolvers are the universal choke point. Any naming system using DNSSEC anchoring (ENS DNSSEC import, Namecoin via ncp11, Handshake via resolver trust) inherits the dependency. Decentralized alternatives not using DNSSEC at all (GNS, PKARR/PKDNS, Tor .onion, Yggdrasil IPv6, Namecoin P2P mode, Slashtags) are unaffected. This is the only scheduled global DNS event in 2026.
Cross-reference: Overview - Decentralized DNS; Sep 14 weekly §2; Aug 31 weekly §"KSK rollover."
3. Pubky ecosystem — three tagged releases in 7 days
The Sep 7 and Sep 14 weeklys were tracking an extended release plateau in the Pubky stack (pubky-homeserver on v0.11.0 since Aug 19, pubky-app on v1.7.0 since Aug 13, pkarr on v8.0.1 since Aug 31). All three plateaus ended in the Sep 14–21 window:
pubky-homeserver v0.12.0 — released 2026-09-14 09:52 UTC (commit fdf3786; missed by the Sep 14 weekly which had captured only the Sep 11 main-branch commits, not the tag). Tag carried BREAKING CHANGE labels. Major contents:
- BREAKING: DockerPostgres::shared() shares Postgres instance but isolates databases; pubky-test URL query param removed (ef250ee, PR #500 by @86667)
- BREAKING: Docker builds now default to homeserver instead of testnet (pass --build-arg BUILD_TARGET=testnet for testnet image) (cf23bea, PR #594 by @andrei-21)
- SDK: two-stage auth flow made publicly available (3e9b933, PR #586 by @dzdidi)
- Homeserver: configured PKARR relays enabled for republishing (2275d06, PR #580 by @andrei-21) — the PKARR relay republish feature is now in production
- SDK: path-addressed requests (8d351b5, PR #546 by @MCarlomagno)
- Homeserver: metrics for cookie auth and pubky host usage (f8e7418, PR #552)
- Homeserver: Retry-After header on HTTP 429 (d508f5c, PR #548 by @ok300)
- CLI: homeserver cli (c81cac6, PR #451 by @SpontaneousOverthrow)
- Homeserver: read_timeout on Pubky client (bb95ecd, PR #599 by @ok300)
- Testnet/Homeserver: rate-limit sort before evaluating (21c8740, PR #573)
- Docs: Cloudflare tunnel guide (2ffb99f, PR #534)
pubky-app v1.10.0 — released 2026-09-18 19:27 UTC (commit 58f83e1; tagged by @secondl1ght). 45+ PRs in the v1.10.0 release. Dominant authors: talosmachina (UX fixes), secondl1ght (PWA + release), infin1t3 (caching, follows, undo). Major contents:
- PWA service worker reworked (#2550) — registered from app code so failures are handled
- Undo on reposts and collection shares (#2358)
- OAuth sign-in bounded on sign-out (#2562) — sign-out always finishes
- 507 Insufficient Storage explained in composer (#2565)
- Streams pagination from Nexus cursors, not indexed_at (#2552)
- Failed reply doesn't destroy the draft (#2572)
- Reply mention completion at caret, not just at end of value (#2580)
- Sign-in prompted on expired session write failure (#2577)
- Visual feed unblocks once missing file metadata settles (#2579)
- Notification preview truncated by grapheme (#2575)
- Character limit obvious at the limit (#2564)
- cypress e2e limit counted in utf-16 units like the app (#2583)
- Agents: unified agent entry point and harness adapters (#2533) — agent discovery UX
- Tags: unified local-first caching + viewport TTL refresh (#2486)
- Collections: copy-link action (#2520)
- Profile: viewer-aware follow state fetch (#2474)
- OG metadata: blocked-IP targets treated as expected fallbacks (#2559); crawler escape sequences stripped from route ids (#2557)
- Rate-limit: coalesce duplicate Nexus revalidations, report 429 once (#2558)
pubky-app v1.9.0 — released 2026-09-17 11:08 UTC (commit e688c9e; tagged by @catch-21, verified by @Orlandohub). The Sep 17 v1.9.0 release was followed 28 hours later by the Sep 18 v1.10.0 — a deliberate v1.9 → v1.10 hot-fix-then-feature pattern.
pkarr — still v8.0.1 (Aug 31, commit 938a938) as latest tag. Trunk activity since v8.0.1:
- Sep 18 — ci: reuse shared Context7 workflow (#311)
- Sep 16 — Merge pull request #312 from pubky/chore/track-ci-workflows-main; chore: track ci-workflows main
- Sep 15 — deps: bump the cargo-dependencies group with 8 updates (#310); ci: refresh Context7 on version tags (#308); chore(deps): update rustls to 0.23.45 (#309)
- Sep 7 — chore: add 7-day Dependabot cooldown (#305); chore: pin ci-workflows to v1.0.0 (#300); dependabot + CI bumps
The trunk is dominated by shared-ci-workflows migration + dependabot. The next tagged release is not imminent — Sep commit count is dominated by dependabot + CI workflow pins, not feature work. The Sep 14 weekly's reading of "team is in SDK stabilization + CI workflow consolidation" continues to hold.
Cross-reference: PKARR; Sep 14 weekly §"PKARR ecosystem — v8.0.1 breaks the Aug 19–Sep 7 tagged plateau"; Sep 7 weekly §"Pubky plateau CONFIRMED."
4. ENSIP-31: Payment Preferences — recipient-side chain routing at the protocol layer
ENSIP-31: Payment Preferences — Standards, ENS Development, 0 replies, Sep 17 by nxt3d (Unruggable Labs / Premm.eth). Forum: https://discuss.ens.domains/t/ensip-31-payment-preferences/22431. Draft PR: ensdomains/ensips#87.
The problem: an ENS name can resolve a receiving address on many chains, so knowing the name is not enough. The sender still has to pick the chain, and the recipient's answer often depends on the token. Today there is no way to learn that preference from ENS — wallets guess, or the two sides sort it out over chat.
The proposal: let the recipient publish an ordered, token-specific list of preferred chains through their ENS name. A wallet can read the list before choosing a chain, then resolve the receiving address on that chain exactly as it does today.
Worked example (from the ENSIP): alice.eth publishes that for USDC they prefer Base first, Ethereum second. A wallet asked to send them 20 USDC reads that record, picks Base, and resolves their Base address as normal.
Storage: ordinary ENSIP-24 data record with key like payment-preference[<multichainTokenHash>]. No new resolver methods.
The open question (worth tracking) — how the Multichain Token Registry fingerprints a token: - Symbols such as USDC are not canonical - Contract addresses are canonical, but each address identifies a token on only one chain - Once a token exists across multiple chains, there is no single canonical identifier for the multichain token as a whole - ENSIP-31 currently addresses this by hashing an immutable snapshot of its chain-specific token representations - The author is "very open to other approaches for identifying a multichain token"
Why this matters for the dDNS stack: this is the first ENSIP in 2026 to standardize recipient-side routing intent at the protocol layer, complementing the resolver layer (ENSIP-24, CCIP-Read, etc.) and the identity layer (ENSIP-26: ENS Native AI Identity, ENSIP-27: Agent Card Schema). Combined with Nostr NIP-05 (which already bridges NIP-01 pubkeys ↔ DNS names ↔ ENS via pkarr) and Nostr NIP-17 (stealth addressing, ongoing NIPs PR #2471 thread per the Identity weekly), the decentralized naming stack now has explicit standards for: - who you are (ENS name ↔ Ethereum address ↔ pkarr record ↔ Nostr pubkey) - what agent you are (ENSIP-26, ENSIP-27, ERC-8004, ENSv2 plugin for MetaMask Agent Wallet v0.8.0) - how to find you across chains (ENSIP-31) ← new in W39 - how to pay you privately (Stealth Address Resolution ENSIP, ongoing — see Sep 14 weekly)
Cross-reference: ENS §"ENSIPs in flight"; Newsletter #120 §"ENSIP proposes payment preferences"; Sep 14 weekly §"ENSIP Stealth."
5. ICANN TSG public comment closes TODAY (Sep 21) — the only formal venue for alt-naming coexistence
Initial Report of the TSG on gTLD Integrations with Alternative Naming Systems — public-comment submission window Aug 10 – Sep 21, 2026.
The scope (per ICANN): "This proceeding seeks input on the initial report by the Technical Study Group (TSG) on generic top-level domain (gTLD) Integrations with Alternative Naming Systems. The TSG was convened to study whether a gTLD can be integrated with the same domain name in an alternative naming system in a secure and stable manner. The report focuses on the potential impact to the security and stability of the Domain Name System (DNS)."
Why this is the single most-important policy event of Q3 for the decentralized-DNS stack:
- It is the only formal ICANN venue open in Q3 2026 that specifically addresses whether a gTLD string can coexist with the same string in an alternative naming system (blockchain, mesh, DHT-based).
- The output shapes whether .eth, .crypto, .x, .wallet, .bit, ENS subdomains, Handshake TLDs, etc., can be referenced from gTLD governance as "compatible" — and whether root-zone collision risks are formally acknowledged.
- The TSG was a community-government initiative; the public comment is the only input mechanism, and closes Sep 21.
For the decentralized-naming ecosystem, the substantive questions are:
1. Whether ICANN formally distinguishes between shared-string (e.g. .eth as both an ENS namespace and a hypothetical future gTLD) and adjacent-string (e.g. .wallet as Unstoppable Domains) coexistence.
2. Whether ICANN accepts the operational-security reasoning that the alternative-naming system can be authoritative for its own namespace even when the gTLD exists in parallel (Handshake's claim; ENS's DNS-import claim is the inverse).
3. Whether the Name Collision Observatory (referenced in the Aug 31 weekly) handles blockchain-TLD strings the same way it handles traditional IDN gTLDs.
Operational status Sep 21: public-comment submissions tracked by ICANN public-comment dashboard show Sep 21 = closing date, with Sep 19/20 submissions visible. The submitted-comment count is not visible from the public dashboard at write-time; expect the TSG to publish its next-stage report (incorporating public comments) within 4–8 weeks.
Cross-reference: Overview - Decentralized DNS §"ICANN TSG on Alt-Naming"; Aug 31 weekly §"ICANN Name Collision Observatory"; ICANN public-comment proceeding URL above.
6. ENS DAO Newsletter #120 (Sep 15) — the most DAO-content-rich of Q3
ENS DAO Newsletter #120 published Sep 15, 6:47 PM by estmcmxci (per the forum thread metadata). The newsletter is bi-weekly on Tuesdays at 11 AM ET per the DAO-Wide category header. Substantively richer than #119 (Sep 1) and #118 (Aug 15). Highlights:
Updates from ENS Labs:
-
ENS transparency filing (Blockworks report) — ENS Labs filed a Blockworks report on governance, supply and operations.
$ENSholders can delegate votes on protocol and treasury proposals, but the filing says they have no dividend or revenue-distribution rights. Filing → Blockworks. This is investor-protection disclosure, signaling ENS Labs is preparing for institutional access. -
ENS as Registry Layer for Tokenized Assets — ENS Labs published a blog post describing how ENS could link an asset's official contracts, issuer data, and documentation under one name across networks. ENSv2's hierarchical registries let issuers organize and manage asset families. Blog: ENS Blog: ENS as a Registry Layer for Tokenized Assets.
-
One-Click Registration — ENS registrations are now one click in the ENS App: choose a name, select a payment option, set up your profile in one streamlined flow. A guided walkthrough covers the full experience — from name selection to an instantly usable ENS profile.
-
Name Activity Notifications — User research on the ENS app found that "fear of losing control over one's name" was a recurring concern. The ENS App beta now has notifications to monitor activity on registered names, aimed at improving name management and security. The same feature set adds proactive expiry notifications to track renewal deadlines.
-
ENS Describes Namespace as Coordination Layer Across 100+ Chains — ENS published a post describing its namespace's evolution from human-readable addresses to broader infrastructure. The post states ENS now connects users, apps, agents, protocols, contracts, records, and chain metadata across more than 100 chains, framing naming as coordination infrastructure.
-
ensjs PR #377 points Sepolia at the clean hackathon testnet deployment — covers ENSv1 and ENSv2. Resolved ambiguous mappings via ensjs patterns + onchain cast checks.
tscand live Sepolia reads pass. -
ens-contracts PR #572 (adraffy) — DNSSEC ancestor inceptions stored onchain. Updates DNSSEC and DNSRegistrar contracts to store ancestor inceptions per
(node, type)onchain. Adds a newgetInception(name, type)getter while keepinginceptions(node)as a backwards-compatible fallback, and emits anInceptionChangedevent on_claim(). This is the change Sepolia has been waiting for to make DNSSEC import trust-anchored (the [DNSSEC oracle replacement proposal] was flagged by Sep 14 weekly as "security-critical; under-specified for DNSSEC trust anchoring"). -
ens-contracts PR #573 (hiddentao) —
.eth resolver deploy order bug fix. Setting the.ethresolver could revert or silently fail after registrar ownership transferred toRegistrarSecurityController. The fix checks the registrar's current owner and routes the call through the controller when needed, making the step order-independent. Testing on a fresh Sepolia deploy confirmed the fix. -
ENS Docs PR #589 (schmidsi) — adds
.lockerto the custom-TLD implementations table, including its registrar address and Etherscan link. Registrar ownership verified at block 25925109.
DAO-Wide Headlines:
- Blockful September delegation incentive pool 8K ENS — final month of the program.
- SafeNotes Shutting Down — built by former secretary limes.eth (January 2024) to annotate Working-Group multisig transactions; Meta-Governance decided not to continue supporting.
- ETHRome 2026 — 40-hour coding sprint, 40 builders, sponsors including Ethereum Swarm.
- Blockful + anticapture analysis identifies premium sales as a new ENS DAO revenue pillar: $113K in August after 3 months of growth, offsetting declining new-registration revenue.
- ENS Simocracy experiment — 110+ proposals from 60+ participants; Protocol Labs + Fire Eyes distributing $10K. Stronger engagement than on the ENS forum.
Meta-Governance:
- MetaGov Term 7 Index tracks signer rotation, SPP3 streams, compensation, endowment fees, and delegation rewards. Its 2-of-4 operating Safe includes the ENS DAO Timelock as a signer.
- SPP3 selects Grails team for marketplace RFP — pending onchain vote + KYC. Grails will operate under Nomentum.
- October Funding Window outlined — continuity, compensation, growth, grants, community work. Stewards favored shared hackathon outreach with Labs and objective-based travel funding (incl. DevCon).
- Endowment NAV reaches $93M, August strategy earnings $223K, 3.08% blended APY. Rebalancing ETH toward stablecoins; custody of the endowment Safe moved to the Foundation.
- ENSIP-28 (Name Owned Accounts) — verification rules update; authors will publish a forum breakdown for feedback.
- PUR #10 revised — KPK will replace the Endowment's Zodiac Roles module with a patched
v2.1.1.1carrying PUR #10 permissions. No signatures needed; awaits Blockful verification. - Steakhouse August 2026 ENS Financial Report Slides published — broader financial perspective on ENS DAO (vs endowment-focused monthly reports). Dune Dashboard + current documentation linked.
Ecosystem:
- ENSIP-28: name-owned accounts — Unruggable Labs / Premm.eth. Lets names list accounts per chain via ENSIP-24 data records. Verification out of scope; alternatives include indexed addresses and subnames.
- ENSIP proposes payment preferences — see §4 above (ENSIP-31).
- ENSIP-X: stealth resolution — Draft maps ERC-5564 stealth meta-addresses to ENS names, returning a fresh address per payment. Gateway results verified onchain. (ensips PR)
- ENSIP proposes text-record attestations — Thread refining how clients scope trust and handle key rotation, name expiry, and potential takeovers. (ENSIP: Text Record Attestations)
- Blockful Year 2 plan — six services under guarantees; advances referral, short-name, Governor Nexus work.
- ENSv2 plugin for MetaMask Agent Wallet v0.8.0 — see §7.
- Namespace Releases ENSforge SDK — TypeScript SDK with intent-level actions for ENSv1 and ENSv2. v0.3.1 offers Promise and Effect APIs under Apache 2.0. (ensforge)
- ENS Forge adds HCA support ahead of ENSv2 rollout — namespace_eth announcement.
Newsletter footer: "Posts older than 4 weeks are archival—browse cautiously, as links may..."
Cross-reference: ENS; ENS DAO Newsletter #120 directly via the forum post (link in §6).
7. ENSv2 plugin for MetaMask Agent Wallet v0.8.0
Package: @estmcmxci/mm-plugin-ensv2 v0.8.0 — published Sep 15 per Newsletter #120.
What's in v0.8.0: - Sepolia ENSv2 resolution - ENSv2 registration - ENSv2 records (text, address, contenthash per extension) - Primary names (ENSIP-5 + ENSv2 equivalent) - ERC-8004 agent identity — the agent-identity layer
Why this matters:
- It's the first ENSv2 SDK path through the MetaMask Agent Wallet CLI, which is the high-profile MetaMask surface for agentic infrastructure.
- Sepolia-only — mainnet blocked on the audit close + ENS Labs + DAO go/no-go from Oct 26 onwards.
- ERC-8004 integration is the first agent-identity-class protocol hook into ENSv2 (the ENS-side counterpart of the [ENSIP-26 ENS Native AI Identity] (Mar 13) and [ENSIP-27 Agent Card Schema /.well-known/agent.json] (May 27) proposals).
Cross-reference: ENS §"ENSIPs in flight"; Newsletter #120 §"ENSv2 plugin for MetaMask Agent Wallet."
8. DNS-AID — draft-02 still current, expires Nov 28
draft-mozleywilliams-dnsop-dnsaid-02 — "DNS for AI Discovery", May 2026. Expires 28 November 2026. Authors: Mozley, Williams, et al. Working group: dnsop. Reference implementation: dns-aid/dns-aid-core at v0.4.8+. Public site at dns-aid.org.
Mechanism (unchanged from May 2026): uses SVCB records for connectivity + metadata, a well-known entry point using DNS-SD labels into an organization's agent index, and optionally DNSSEC + DANE TLSA records for trust and security.
Three discovery use cases:
1. Known Agent (SVCB record query for agent-name.example.com)
2. Known Organization (_index._agents.example.com)
3. Known Capability (out of scope, can be derived from #2)
ALPN additions requested for IANA registration: mcp (Model Context Protocol), a2a (Agent-to-Agent).
Status this week: no new draft. Mid-Sep expected for new IETF submission per the Sep 14 weekly's "mid-Sep announcement window" — that window has now closed without a new draft. The next natural milestone is draft-03 in late October / early November ahead of the Nov 28 expiry. If no cut, the working group loses a meeting cycle.
Cloudflare Agent-Readiness checker (Aug 24 weekly) still enforces draft-01 expectations without acknowledging the breakage — the Enforcement-of-draft-01 issue remains unaddressed.
Cross-reference: Overview - Decentralized DNS §"DNS-AID"; Aug 3 weekly §"DNS-AID — naming layer for the agentic web"; Sep 14 weekly §"DNS-AID — quiet, draft-02 expires Nov 28."
9. GNUnet / GNS, Namecoin, Handshake — release plateaus (GNUnet remains experimental)
- GNUnet / GNS — still 0.29.0 (Aug 20) as latest release per gnunet.org news. No 0.29.1 patch release, no libgnunetchat update since 0.8.0 (Jul 18). GNS protocol break vs 0.28.x still in effect. No new release; experimental software.
- Namecoin — no Namecoin Core tag since nc31.1. Bitcoin Core upstream sync merges continue (e.g. #36161, #36164, #36169, #36123, #36130, #36163, #36166). ncp11 + ncp11 + ncgencert HTTPS-in-stock-browsers stack unchanged. Stable plateau.
- Handshake — hsd (
handshake-org/hsd) still last commit 2025-08-22 (698e252 Merge PR #944 from 'nodech/fix-partial-open') — >1 year stale as of Sep 21 (30 days past the Sep 14 weekly's "1 year stale" milestone). No v3.x tag. PR #952 (long-open hard-fork proposal) still not landed. hns-rs (handshake-rs/hns-rs) still v0.4.1 (Sep 1) as the latest tag — no v0.4.2 or v0.5 in the 20-day window. The Sep 14 weekly's "Handshake core protocol development is effectively paused" reading continues to hold.
Cross-reference: GNS; Namecoin; Handshake.
Cross-cutting context
- ENSv2 mainnet deploy clock is mechanical but unresolved:
- ✅ Sep 14 — competition closed on schedule
- 🔴 Sep 20 — ENS Labs resolved all Critical/High/Medium/Low reports (deadline was yesterday; outcome not publicly posted)
- Sep 28 — Immunefi results frozen
- Sep 29 — final 48-hour dispute window closes
- Oct 26 — payment + public results publication
- After Oct 26 — ENS Labs + DAO go/no-go on mainnet (separate governance path, no published calendar)
- Decentralized DNS ecosystem status Sep 21, 2026:
- Active shipping: ENS (Labs: Newsletter #120, ENSIP-31, DNSSEC inception PR, deploy-bug fix, MetaMask Agent Wallet plugin; DAO: Blockful + Endowment + Simocracy); PKARR ecosystem (pubky-homeserver v0.12.0, pubky-app v1.10.0 + v1.9.0, pkarr v8.0.1 + trunk CI consolidation); hns-rs (v0.4.1 protocol line); Nethermind Surge (rollup framework).
- Plateau: GNS / GNUnet 0.29.0; Namecoin nc31.1; hsd (truly dormant, >1y); pkarr tagged (dependabot-only); ENS Mainnet v2 (Sep 20 resolution deadline was yesterday).
- Quiet / stale: DNS-AID (no new draft, Nov 28 expiry); Handshake PR #952 (>1 year stale); ICANN Reveal Day date (waiting on ICANNWiki formal announcement).
- Closing today: ICANN TSG on gTLD Integrations with Alternative Naming Systems — Sep 21.
- Closing Sep 28: DNS Abuse Mitigation PDP 1 Initial Report.
- KSK rollover is the only scheduled global DNS event in 2026; Oct 11 is the hard cutover. Decentralized alternatives not using DNSSEC (GNS, PKARR/PKDNS, Tor .onion, Yggdrasil, Namecoin P2P mode, Slashtags) are unaffected.
- Sep 21 = today's TSG close: the single highest-signal policy event for the dDNS stack in Q3 2026. Output shapes whether
.eth,.crypto,.x,.bit,.wallet, ENS subdomains, Handshake TLDs can be referenced from gTLD governance as compatible.