ERC-8004 bindings are now visible on @OpenSea.
The relationship between an ENS name and its agent can be viewed directly on the OpenSea asset page.
Because the agent is bound to the ENS NFT, ownership and control transfer with the name.
🧵3/3
Your @ensdomains name can now be a verifiable AI agent identity.
Using ERC-8004, ENSIP-25, and ENSIP-26, an ENS name can advertise metadata, MCP endpoints, and agent capabilities that AI applications can discover and consume.
We built a simple interface to make this easy 👇
Try it out:
https://t.co/WeQxSRI9Tt
Full walkthrough:
https://t.co/YFfAzQyeHh
Learn how to:
• Register an ERC-8004 agent
• Link it to an ENS name
• Publish ENSIP-25/26 metadata
• Expose MCP endpoints
• View the binding on OpenSea
🧵2/3
@adraffy@estmcmxci Do you have any other recommended reads down this path of thought? This is fascinating to me - it's basically how I have lived my life for the past 15 years.
This proposal seeks to create clearer operational ownership within the DAO and facilitate initiatives to move the DAO forward.
It focuses on expanding participation across the wider Ethereum ecosystem. We would like to get this in front of as many people as possible.
ENS DAO is considering a pilot to replace Working Groups with a Coordination Layer focused on execution, contribution, and ecosystem programs.
The structure is bounded by transparency requirements, timelocks, and delegate veto.
Read and discuss ↓ https://t.co/foUG8p9Ebx
We have special guests and we will talk about Agent NFTs.
Our guests: @CodinCowboy from @opensea, @nxt3d the author of ERC-8217 and adapter8004 and our developer @YigitDuman 🔥
Set your reminders and join us!
https://t.co/Ru4YTPCFNV
Scope: Agent identity for now with potential to expand scope iteratively over time.
They acknowledge that whilst they are a bigger player in this space, adoption is vital.
🧵 2/n
@ICANN Contracted Parties Summit - an ongoing thread.
1. James Bladel from @GoDaddy is on stage talking about their Agent Name Service (ANS) - an open standard w/ open source SDKs.
🧵1/n
ENS is a DAO (@ENS_DAO) . If the community have a compelling justification for this, they can and should write an updated registrar controller/Oracle and submit a fleshed out and compelling proposal.
I'd support something that demonstrably improves ENS.
@diamond__eth@ensdomains@garypalmerjr The on.eth registry is a source of metadata about blockchains.
If you imported https://t.co/WqfbKdAfYk to ENS, a client wanting to send funds to mydomain.com@base could resolve the ENS cointype for base from the registry and resolve https://t.co/WqfbKdAfYk subject to ENSIP-9
If you'd like to dive a little deeper into the technical implementation of the on.eth chain registry resolver, I've written some documentation 🫡
@ensdomains@ENS_DAO
https://t.co/F2ZdrtaOhH
How will vitalik.eth@base resolve once apps support interoperable addresses?
The ENS name resolves the account, while the chain suffix resolves the execution environment through the on.eth chain registry.
Both combine into a single interoperable address.
@brando_sui@Mawuko@ValidatorEth@ensdomains Watch this space. The on.eth registry can be used to store any chain metadata, including ENS cointypes, and ERC-7930 Interoperable Addresses to aid in the resolution of chain specific addresses.
Ethereum is no longer a single execution environment. It is an ecosystem of chains.
But chain identities today live in GitHub files, client-side mappings, and app-specific logic. There is no shared source of truth.
on.eth introduces one. 🧵