Resolving ENS names in onchain reports is invaluable to payment managers!

**ENS is moving forward with ENSv2 deployment in 2026**, incorporating key improvements to Layer 2 interoperability and user experience. **Key developments:** - ENSv2 will launch this year as planned, with most engineering resources focused on core features - New architecture enables **cross-chain stablecoin purchases** and single-step registration - L2 integration learnings are being applied to simplify multi-chain functionality for end users **Technical improvements:** - Shift from flat registry to **hierarchical system** where each name has its own registry - Enables flexible ownership models and fine-grained permissions - New ENS Explorer provides full transparency across historical data and ENS versions - Redesigned dashboard offers clearer view of names, settings, and activity **User impact:** - Upgrading to ENSv2 will be simpler than previous migrations - System remains built on Ethereum's decentralized foundation - Enhanced multi-chain support while maintaining backwards compatibility The update represents a significant architectural evolution while preserving ENS's core commitment to decentralization and user control.

The Ethereum Name Service has launched public alpha versions of two new platforms: - **ENS App** ([app.ens.dev](http://app.ens.dev)): Streamlined interface for everyday users to register names and manage their web3 identity - **ENS Explorer** ([explorer.ens.dev](http://explorer.ens.dev)): Advanced tool for ecosystem builders requiring precise ownership controls These platforms represent ENS's evolution from simple address replacement to comprehensive identity infrastructure for web3. Both tools will officially launch alongside ENSv2. The team conducted in-person user testing at Devconnect in Buenos Aires and is continuing to gather feedback during the alpha phase. **Try the alpha versions today** and help shape the future of web3 identity management.

**ENS Doubles Down on Ethereum** The Ethereum Name Service has announced that ENSv2 will deploy exclusively on Ethereum, rejecting multi-chain expansion. **Key Points:** - ENSv2 will remain solely on Ethereum's mainnet - The upgrade process for existing names will be simplified compared to previous versions - ENS cites Ethereum's decentralization and security as core reasons for the decision - No plans for deployment on Layer 2s or alternative chains This decision reinforces ENS's commitment to building on what they consider the most secure and decentralized blockchain infrastructure available. The team emphasizes that the upgrade path will be more straightforward for users than past transitions. [Read the full announcement](https://ens.domains/blog/post/ens-staying-on-ethereum)

The ENS Manager app has introduced a highly anticipated feature: **built-in expiration notifications**. **Key Features:** - Set up reminders through multiple channels: email, Telegram, or browser notifications - Never lose your ENS domain to accidental expiry - Notifications work directly within the app at [app.ens.domains](http://app.ens.domains) **Additional Context:** This builds on existing ENS Manager features, including the ability to register and extend names by selecting exact expiration dates for more precise domain control. The notification system addresses a common pain point for ENS users who may forget renewal dates and risk losing valuable domain names.

**ENS is gearing up for its v2 launch** by requiring developers to update their libraries and applications. Key requirements for ENSv2 readiness: - Update ENS libraries to latest versions - Ensure apps resolve names via **CCIP-Read protocol** - Verify **L2 compatibility** for name resolution - Implement Universal Resolver support The Universal Resolver serves as the foundation for ENSv2, enabling cross-chain name resolution and improved functionality. **Why this matters:** ENSv2 represents a significant upgrade to Ethereum's naming infrastructure, expanding beyond simple address mapping to comprehensive web3 identity management. Developers should review the [ENSv2 readiness documentation](https://docs.ens.domains/web/ensv2-readiness/) and test their applications now to ensure seamless transition. *Action needed: Update your ENS integrations before the v2 launch to avoid service disruptions.*