🌩️ Cloudflare chaos sparks decentralized demo

At a recent hackathon featuring 685 projects, approximately 90-100 teams integrated ENS into their builds, signaling a shift in how developers view naming services. **Key Development:** - ENS is evolving beyond simple user experience improvements - Now being used as infrastructure for identity coordination, communication, and cross-platform interoperability - Winners to be announced soon **What This Means:** The high adoption rate suggests developers are treating ENS as fundamental infrastructure rather than an optional feature. Teams are building ENS directly into their applications' core functionality for identity management and user coordination. This follows previous hackathons where ENS saw strong integration, including projects ranging from retail payment systems to physical authentication and AI assistants that display ENS names during transactions.

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.*

**ENS is evolving beyond personal naming** to include smart contract identification, making decentralized organizations safer and more user-friendly. **Key developments:** - DAOs can now name their smart contracts using ENS - Makes contracts more **legible and easier to integrate** - Enhances both **user experience and security** for Ethereum users **Leading the charge:** - @nounsdao pioneering contract naming adoption - @enscribe_ developing tools for easy contract naming - ENS_DAO supporting "Contract Naming Season" initiative This expansion transforms how users interact with smart contracts by replacing complex addresses with human-readable names, similar to how ENS already works for wallet addresses.

**ENS becomes core Ethereum infrastructure** following Devcon Argentina 2025. Key developments: - **Onchain identity now essential** for Ethereum ecosystem - Builders adopting ENS across **agents, L2s, and dApps** - ENS serving as **primary naming layer** for real-world events - Meeting growing demand for **decentralized identities** and websites The consensus from Buenos Aires is clear: ENS has evolved from optional to **fundamental infrastructure** for Ethereum's next phase of growth.