ENS Evolves Beyond Address Naming Into Cross-Chain Coordination Layer
ENS Evolves Beyond Address Naming Into Cross-Chain Coordination Layer
🔗 ENS becomes coordination infrastructure
ENS is expanding beyond its original purpose of making crypto addresses readable. The naming system is becoming shared infrastructure that allows identities and execution environments to be referenced consistently across different blockchain systems.
Key developments include:
- on.eth registry: A canonical, on-chain registry for chains like Base, Arbitrum, and Ethereum that allows applications to resolve chain identities through ENS using verifiable data
- DNS twins: Users can now use existing DNS domains as ENS names onchain through Doma, eliminating the need to mint new .eth names
- Governance structure: The ENS DAO maintains ownership of the namespace while operational management will be delegated to a multisig, with chain operators eventually controlling their own metadata
The shift addresses a critical infrastructure gap: without a shared registry, interoperable naming remains fragile as wallets and applications maintain separate chain mappings that can drift. By positioning ENS as the registry layer for cross-chain coordination, the system aims to provide verifiable, on-chain data that works across wallets, apps, exchanges, and the web.
Because on.eth is shared infrastructure, governance matters. The ENS DAO remains the owner of the namespace, ensuring neutrality and long-term alignment with Ethereum’s coordination layer. Operational management will ultimately be delegated to a dedicated multisig. The multisig
ENS was introduced to make addresses readable, but its role has steadily expanded beyond that initial use case. It is evolving into a shared naming layer that allows identities to be referenced consistently across systems.
Without a shared registry, interoperable naming remains fragile. Wallets and applications maintain their own chain mappings, and those mappings can drift. An on-chain registry changes that dynamic. Chain identities resolve through ENS itself using standard resolution flows and
DNS twins extend ENS to the existing internet namespace. If you already own a domain, you do not need to mint a new name. Your domain can now function as an ENS-compatible name onchain.
on.eth is a canonical, ENS-native registry for chains and their associated metadata, covering networks such as Base, Arbitrum, or Ethereum. Instead of asking off-chain databases what “base” means, applications can resolve it directly through ENS using verifiable on-chain data.
ENS began by naming accounts. on.eth expands that vision to naming execution environments. In an increasingly interoperable blockchain ecosystem, coordination across execution environments becomes infrastructure. on.eth positions ENS as the registry layer for that
Launching a new .whatever namespace is easy. Building naming infrastructure that works across wallets, apps, exchanges, and the web is much harder. Why ENS chose to extend the existing internet namespace instead of inventing new roots ⤵️ ens.domains/blog/post/ens-…
Your ENS name does not have to end in .eth. If you already own a DNS domain, you can now use it as an ENS name onchain. DNS twins are now live through Doma ⤵️
Today, DNS meets ENS on mainnet. DNS twins are live! Tokenized DNS domains on Doma Protocol can act as @ensdomains compatible names. Find your name twin here: doma.xyz/ens
ENS Explorer Launches to Navigate Increasingly Complex Name Configurations
ENS has released the **ENS Explorer**, a dedicated tool designed to provide visibility into the protocol's growing complexity. As ENS names have evolved beyond simple labels, they now involve multiple components: - Different contracts and resolvers - Permission structures - Subname configurations - Cross-application behaviors The Explorer surfaces key information including control settings, resolution paths, historical changes, and protocol context. This allows users and developers to understand how names are configured and how they reached their current state. Key features include: - Dedicated resolver pages for inspecting how ENS data is served - Support for flexible setups where multiple names share records through a single resolver - Automatic wallet balance refreshes when switching views - Enhanced social sharing with richer preview cards The tool aims to serve as a source of truth for ENS, using accurate protocol terminology and surfacing technical details that management interfaces alone cannot provide. [Read the full deep dive](https://ens.domains/blog/post/ens-explorer-deep-dive)
🧶 Crocheth Wins Runner Up: Wearable Balaclava Becomes Onchain Identity
**Crocheth** secured a $500 runner-up prize for creating crochet balaclavas that function as onchain identities. **Key features:** - Embedded ArUco markers that resolve to ENS subnames on Base (e.g., midnight.croch.eth) - NFC wristband authentication - ZK privacy pool enabling anonymous transactions - Physical wearable doubles as fully functional blockchain identity The project transforms traditional craft into a privacy-focused identity solution, combining physical fashion with decentralized technology.
Groundtruth Launches Verified Intelligence Map with Human and AI Agent Collaboration
**Groundtruth** introduces a verified intelligence mapping system where humans and AI agents work together to report world events. **Key Features:** - Humans verify identity through World ID - AI agents use ENS domains and ERC-8004 reputation scores - Agents like reuters-monitor.kris0.eth submit intelligence reports - Readers pay $0.005 USDC per report via x402 nanopayments - Includes an MCP server for easy integration The system creates a collaborative news ecosystem where both human and autonomous agents contribute verified information. Payment happens through micro-transactions, making individual reports accessible at minimal cost. This builds on recent developments in onchain AI agents, including Ghost in the Machine, which stores fully autonomous agents as ENS text records with transparent states and memories.
npmguard Wins $1000 Prize for AI-Powered Package Security System
**npmguard** by @iamtguy has secured third place and $1,000 in a recent competition for its autonomous npm package security solution. **How it works:** - New npm package versions are automatically analyzed through an AI audit pipeline - Security verdicts are published onchain using ENS subnames - Developers can query packages (e.g., axios.npmguard.eth) before installation **The problem it addresses:** The tool creates a trust layer for the npm ecosystem, which has previously suffered from security incidents affecting billions of downloads through malicious code. By combining AI-powered auditing with blockchain-based verification through ENS, npmguard aims to provide developers with an additional security checkpoint before installing dependencies. The system leverages ENS's hierarchical naming structure to create queryable security records for individual packages.
ENS Subdomain Becomes Programmable Wallet with Privacy Features
**Kondor** won second place ($1,500) at a hackathon for transforming ENS subdomains into programmable wallets. The project allows users to: - Set token policies through a visual flow builder - Execute operations like swap, lend, forward, and route through Railgun - Generate fresh, unlinked addresses for enhanced privacy The innovation uses a **custom resolver for stealth addresses** - each time the subname resolves, it creates a new address that can't be linked to previous transactions. This builds on ENS's existing subdomain functionality, which lets users create multiple identities under their .eth name (like vault.yourname.eth or wallet.yourname.eth). The Kondor project adds programmable wallet capabilities and privacy features to these subdomains. [Learn more about ENS subdomains](https://support.ens.domains/en/articles/8883890-how-to-create-subnames)