Namespace

@614D05 🫡

@namespace_eth Building the tools we all need. Huge thanks for your work guys 🙏 📖

As ENS becomes more crucial to the AI agent economy, devs need a simple way to use it. Register names or subnames, add addresses, update records, set contenthash. All in 5 minutes with enscomponents.com. 🥷

one step closer to a complete, agent-ready toolkit that covers full ENS support - from simple name resolution to spinning up a custom namespace 🥷 🫡

And as always, give us some dopamine hits in the form of likes, comments, and retweets. 🫡

ENS should be easy to integrate. For everyone. That's the mission - a complete, agent-ready toolkit that covers full support, from simple name resolution to spinning up a custom namespace. Resolvio → resolution API: resolvio.xyz ENS Components → UI kit: enscomponents.com Namespace app → Subname management: app.namespace.ninja ENS MCP → AI agent layer: github.com/thenamespace/e… This is the stack. But more is coming. Stay tuned.

🚨 Announcing Resolvio 🚨 A lightweight, high-performance ENS resolution API. Free, open source, no API key needed. Bulk resolution, built-in caching, agent-ready, and more... Let's dive in 🧵 resolvio.xyz

we will name *every* crypto user.

@614D05 @EthCC

@namespace_eth @EthCC Recommend!! Both of these guys know what's what! Tech talk or beer o'clock Fighting the name game and winning! 🙏 📖

our team will be at @EthCC come say hi 👋

My semi-hot take on ENS and TLDs is this: ENS should apply for a TLD string that clearly communicates "identity" (think .id), enable registrations across all blockchains, and expand beyond the Ethereum ecosystem. (I know .id is taken - using it as an example in this post). ENS can become an 'Everything' Name Service with .eth as a premium domain/identifier for Ethereum-aligned ecosystems, and another TLD (.id) for everyone else, while the protocol remains the same. This is what we wanted to do with @namespace_eth, but unfortunately, we had to give up on the idea for a number of reasons - mainly too much overhead for a small team with a limited budget.. and raising external funding would push us toward a purely profit-driven path, which would compromise the work we do for ENS right now. However, I still believe that operating TLDs through ENS as the core Web3 (domain) naming infrastructure is how we solve the biggest problem - universal resolution! This is how we move from “what’s your address?” to “what’s your username?”, where that username holds *all* your crypto addresses across *all* chains. This is a huge barrier to global mass adoption. Most teams today are solving this UX challenge through chain abstraction, PayFi apps tie wallets to phone numbers, or siloed usernames stored in databases - while ENS-powered domain/username could be universally used, applied, and accepted on every chain, wallet, and app. And the greatest part is - all these TLDs would still use ENS protocol as the underlying 'identity/profile' standard that everyone plugs into and abides by. With or without our own TLD, there should be an active and dedicated effort to collaborate with existing TLD owners in the blockchain space (and beyond) to communicate the value proposition ENS could bring, and invite them to claim their TLD's ownership in ENS and build on top of it. Their domains would inherit everything .eth has today - all properties, functionality, all ENSIPs for programmability, 1,000+ partnerships and integration support that ENS has, and continuous innovation we do (like the fact that ENS domains are becoming AI agent identities, etc.), and most importantly, we solve the universal resolution standard. The alternative would be - they start from scratch? There are many blockchain companies applying to run their own TLDs, which I generally think is a good thing. However, they'll soon realize that operating a universally accepted naming service is a lot harder than it looks... without a dedicated team, ecosystem builders, and without further fragmenting the space and creating more walled gardens (even if ICANN-compliant). ENS has far too strong network effects; it can be the distribution layer for TLDs entering Web3 rather than a competitor, offering access to its 1,000+ integrations network to tap into and helping solve the cold start problem. One domain (any TLD) → resolves everywhere. Universal naming/identity layer. But anyway, this post makes me extremely happy. It hits all the right points. Kudos to @aurbelis and the ENS Labs team. Excellent work!

Naming on the internet is changing. But the rules governing it haven’t caught up. ENS Labs just submitted a public comment to ICANN on “name collisions,” and it highlights a deeper issue with how naming is still being approached. Here’s why it matters. ↓

ens maybe?