ENSv2 was activated today and I'm proud to be part of the biggest upgrade of @ensdomains in its history! It's not only the smart contracts that have been redesigned and rewritten to lay the foundation of the open naming layer for the internet: a flexible permissions system, an extensible and configurable tree structure and more. There are also two new apps, the manager and explorer, which will give the two distinct user groups, normies and power users, the interface they need. On top of that, and here is my personal contribution, we made sure that wallets and apps which integrate with ENS not only become ready for ENSv2 but also deepen their integration: Use the Universal Resolver, support DNS-imported names, do offchain resolution and many more technical integration details. The ENS integrations ecosystem got an upgrade too 💥. Shout out to the world-class devrel team: Greg (@gregskril), Kevin (@workem0n) and Yash Goyal (@yash_goyal_dev) who made sure that every major web3 library, all important wallets and most apps are ENSv2 ready with tailored support and extensive pull requests, concise and complete documentation, automated test suites and a CLI that agents and humans love, all while traveling the world enabling hackers at @ethglobal and other hackathons. I'm also grateful to be working under the leadership of Nick Johnson (@nicksdjohnson), Jeff Lau (@Jefflau), Katherine Wu (@katherinewu) and Dom (@domicoeth) who had to take some tough and controversial decisions like ditching NameChain or postponing the launch until we were 100% sure it was ready. Nothing worse than a rushed launch. If you are an app developer and you are not sure if your app is ENSv2 ready, don't fret: ENSv2 names will continue to be resolvable through the documented V1 resolution paths. And being fully ENSv2 compatible is, 90% of the time, simply updating to the latest version of your favorite web3 library. If your app has writing capabilities like registering a name, setting a text record or managing subnames, more work is needed. Head over to the ENSv2 documentation to find out more or reach out. We're happy to assist.