ENS started as a way to make blockchain addresses readable. Today, the same namespace connects users, apps, agents, protocols, contracts, records, and chain metadata across 100+ chains.
That’s how naming becomes coordination infrastructure.
Read: ens.domains/blog/post/iden…
ENSv2 makes the hierarchy of names explicit onchain.
Instead of every name living in one flat registry, each name can define its own registry, resolver, and rules for the namespace below it.
Learn more: ens.domains/blog/post/ensv…
The feature everyone’s been asking for is finally here.
@gregskril walks through proactive notifications in the App, so you can track expiries, catch reminders, and renew before it’s too late ⤵️
A contract address can tell you where a token lives. It can’t tell you the full story of what it represents, who issued it, or where to find its latest information.
That’s the role ENS can play as a registry layer for tokenized assets.
Read more:
