ENS Launches registerAgentIdentity() for On-Chain Agent Verification

ICANN has launched a technical study group to examine how generic Top-Level Domains (gTLDs) can integrate with alternative naming systems like ENS. **Key Context:** - ICANN's next round of gTLD applications opens in April 2026 - ENS is actively preparing for this expansion by protecting its brand and exploring partnerships with registries - The study represents a significant step toward potential interoperability between traditional DNS and blockchain-based naming systems **What This Means:** The technical study group will explore how established internet naming infrastructure could work alongside decentralized alternatives. This could pave the way for greater integration between traditional domain names and blockchain-based systems. ENS has been positioning itself strategically for this development, working to bring more ENS features to domains as the internet's naming layer continues to evolve. Learn more about the study group: [ICANN Blog Post](https://www.icann.org/en/blogs/details/gtld-integrations-with-alternative-naming-systems-technical-study-group-underway-09-06-2026-en)

Nick Johnson, lead developer at Ethereum Name Service, has been selected as one of seven members for ICANN's Technical Study Group. The group will assess how onchain names and the traditional Domain Name System (DNS) can work together securely. **Key Points:** - ENS secures representation in shaping the future of internet naming systems - The study group will explore integration between blockchain-based naming and traditional DNS - This marks a significant step toward potential interoperability between web3 and traditional internet infrastructure The selection comes as ENS continues to expand its role in decentralized naming systems. The organization has previously engaged in public discussions about domain naming standards, including criticism of competing services like Unstoppable Domains. ENS operates similarly to DNS but uses Ethereum blockchain technology to map human-readable names to cryptocurrency addresses and other identifiers.

**ENS is evolving beyond individual users** as organizations, applications, and institutions begin integrating onchain identity into their infrastructure. **Key developments:** - Major organizations are now actively implementing ENS for their operations - Cross-platform adoption makes identities universally connected across wallets and applications - Users gain portable identities that work seamlessly across ecosystems and payment networks **Why it matters:** This shift transforms ENS from a personal naming tool into public infrastructure that millions interact with daily. Read the full analysis: [ENS Blog](https://ens.domains/blog/post/onchain-identity-is-becoming-public-infrastructure)

**Turkey makes blockchain infrastructure move** The Republic of Turkey's Directorate of Communications registered **cbiletisim.eth** as its official decentralized identity through the Ethereum Name Service (ENS). **Key details:** - First government entity to establish an official onchain identity using ENS - Part of broader initiatives in AI, blockchain infrastructure, and digital sovereignty - Spotted at Turkey's Directorate of Communications headquarters in Ankara **What this means:** This marks a practical step in government adoption of blockchain technology for digital identity management. Turkey is using the same naming system that maps human-readable names to blockchain addresses. The move demonstrates how traditional government institutions are exploring decentralized infrastructure alongside their existing digital systems. [Official announcement](https://www.iletisim.gov.tr/english/duyurular/detay/press-release-digital-transformation-breakthrough-building-the-future-of-our-communication-ecosystem-via-ai-and-blockchain-technologies)

**ENS is upgrading its resolver system with ENSv2** The Ethereum Name Service is introducing a Universal Resolver - a single smart contract that can resolve names across multiple environments: - ENSv1 names - ENSv2 names - Layer 2 networks - Offchain names via CCIP-Read **What developers need to know:** Applications using ENS should update their libraries to ensure compatibility with the new Universal Resolver. The system uses CCIP-Read protocol to fetch data from L2s and offchain sources. This consolidation simplifies the resolution process by eliminating the need for separate resolvers for different name types and networks. Developers can find implementation details in the [ENSv2 readiness documentation](https://docs.ens.domains/web/ensv2-readiness/). **Action required:** Review your ENS integration and update libraries to support cross-chain resolution.