Namespace @namespace_eth

try it: resolvio.xyz it has bulk resolution and caching built in. free to use. no api keys required. use ours or self-host your own. agent-ready 🤖 tell Claude: "hey, implement ens resolution using resolvio.xyz" and you're good

17M ENS resolutions served 🫡 we built Resolvio mostly because we were annoyed that we had to reimplement ENS resolution from 0 for every new product. resolving ENS names should be a piece of cake. and now it is.👇

Congrats to ENS x AI group crossing 200 members 🥂 See you at 500 members 🫡

Builders are shipping ENS agentic infra: → Adapter 8004 for record control → Skill standardization → New paths for interoperability This strengthens ownership guarantees, making ENS programmable for AI apps. Join this week’s call. discuss.ens.domains/t/ens-x-ai-tel…

Some of my perspective on where the @ethereumfndn is going. First of all, this is only my own view. The board is not just me, and I have no extra special powers on the board that the other board members do not. @aerugoettinea is the one executing much of this transition. My input has been largely on technical questions. The board is in the process of expanding, and my own power within the org will continue to decrease, which is honestly what I want. The 2025 era brought many important improvements to EF and its ability to execute. Many issues were resolved, and EF continues to benefit from its improved efficiency and greater focus on concrete goals to this day. And so with those problems resolved, early this year, the largest remaining hole that I perceived was something different nagging at me: I would regularly spot people saying things like "vitalik says these beautiful things about ethereum needing to be decentralized, and have privacy, and be a sanctuary technology, but why do the EF's actions not reflect that?" Now, you may have been hearing something different. You may not have been sensing a feeling of crisis at all, and maybe were hearing people saying that finally we were taking execution and BD seriously and the main task for us is to keep going that way and be even better and faster. Then probably there is genuine difference between you and me, in what kinds of criticism I take most seriously, and what kinds of critics through their criticism are most able to make me feel pain. As an analogy, let's briefly switch over to a different domain. One belief you can have about Google is that it is a success story, and has brought a lot of good to humanity in organizing the world's information. Another belief you can have about Google is that they had a beautiful idealistic beginning, but at some point the corruption of mainstream corporate attitudes seeped in, and they slowly bit by bit completely abandoned the "don't be evil" slogan. My belief on Google specifically is probably somewhere between the two. BUT, if you had taken me back in time to ~2008, and offered me a button to press to make Google one or two standard deviations more "dogmatic", eg. give Richard Stallman permanent veto power over some key policies, I would immediately press it. Why? Because a choice for one company is not a choice for the world, or even one country. Google existed and exists in the context of a technology industry generally drifting away from early idealistic don't-be-evil roots and toward greed for financial gain, totalizing visions of accelerated superintelligence, infiltration by sociopaths, and craven capitulation to (or worse, active participation in) government pressure for ideological control, surveillance and war. And so *one company* doing something different, positioning itself to be what George Bernard Shaw calls the Unreasonable Man, resisting the trend of the times, would have been better for freedom, balance of power and stability of society as a whole, than *all* large companies bending to dominant trends. This is a part of my version of pluralism. This line of thinking is not just mine, but I also is not too far off from what Aya and others had in mind with the Mandate. Now how does this all get to the role of the EF? EF is not a "center of Ethereum", rather EF is "one node, with a defined purpose, alongside other nodes". We've always said that the EF should be the latter, but many in the Ethereum ecosystem (and even within the EF) wanted us to be the former. Now, we are taking action to ensure that we will be the latter. This is particularly important because EF is a limited organization, with limited resources and limited organizational capacity. The EF has only ~0.16% of all ETH (less than many other individual ETH holders), whereas among other blockchains it's common for "the central foundation" to have 10-50%. Fiscally, the EF was originally designed to fulfill a limited work scope defined in the token sale docs and other pre-launch materials (building the chain software; getting through Frontier, Homestead, Metropolis, Serenity), which was fully completed in 2022; it was not designed to be an eternal steward. And so today, the EF is choosing to use its remaining resources to pursue longevity over breadth (yes, this means we sell less ETH). The EF focuses *specifically* on those activities critical to the success of ethereum as a censorship/capture-resistant, open, private and secure system, that would not happen otherwise. This means making hard choices, and in some cases even activities that we highly approve of and people that we highly respect becoming outside of the EF. People of great technical talent, public respect and even alignment with the mission and CROPS being outside of the EF is in fact necessary if we want important tasks to be able to attract outside capital. This also means the EF taking opinionated stands culturally. This is all intended in cooperation with all other parts of ethereum. We recognize that many other parts of the ethereum world highly respect CROPS and related values. But highly respecting is not the same as choosing to specialize and totally dedicate to a domain (Compare in a different domain: I think reducing animal cruelty is important, and I like vegan food, but am not full unconditional vegan myself) EF is still in a transition period, and we expect its new long-term form to stabilize over the next few months. What are the guiding principles of this new form? Again, I am only one person, but I can give my answer from a technical perspective (there are also critical non-technical aspects). At the core, *Ethereum must be impressive*. We are living in an age of highly intelligent AI and all kinds of other technological acceleration. "Status quo EVM, with a hard fork or two a year to optimize for short-term needs of users" is not interesting. To some, "impressive" means: 250ms latency and 1M TPS. I think Ethereum trying to go that route is a mistake. Being as fast and as scalable as possible, and only a small epsilon more decentralized than the others, is a route to mediocrity, and if we try it we will lose. I think Ethereum should scale. But I think Ethereum should strive the hardest to be deeply impressive in a different dimension: the CROPS dimension. This means things like: * Provably bug-free Ethereum. This is a goal that all cybersecurity researchers would have thought is absurd and impossible, up until roughly 6 months ago. Now, it's on the cusp of being possible, thanks to AI-assisted formal verification. So we should be frontrunners in doing this. * Available chain consensus. Ethereum is, and with lean consensus will cotninue to be, the ONLY chain that has both (i) traditional-BFT style properties that it's safe under asynchrony up to a high level of fault tolerance, and (ii) the bitcoin PoW-style property that under synchrony it's safe up to 49% attackers. As far as I can tell, literally no other chain has this or is planning for it; bitcoin goes for (ii) only and most other chains go for (i) only. Some will remember I fought hard for this, Unreasonably insisting that it is not OK for ethereum to rely on social consensus and hard forks to rescue ethereum from 34% of nodes going offline. It's OK for chains like hyperledger, bnb, solana, tempo, etc. It's not OK for bitcoin or ethereum or eg. zcash. * Intermediary minimization. The fact that smart contract wallets, protocols like railgun, etc have to send transactions through intermediaries to get included onchain is honestly embarrassing, and it's a constant point of fragility. Hence the work on FOCIL and EIP-8141 (and 7701 and years of work before) to make transaction sending intermediary-minimized with public mempool and strong inclusion properties, in a truly general-purpose way, that covers not just eg. secp256r1, but also privacy protocols and much more. Kohaku is pushing intermediary minimization at the user layer, pulling Ethereum away from the dystopian status quo world where our wallets don't even verify the chain, send our private data out to a dozen third-party servers, and toward a brighter CROPS future. Some of these goals are Unreasonable - maybe Ethereum would be "fine" getting only 50% of the way - what if we depend on intermediaries, but make it easy to switch? But going 50% of the way would not make Ethereum Deeply Impressive in the CROPS way. So we push for 100%. Fortunately all these goals are compatible with high TPS, this is a major focus of research (esp. on scaling the state). Well-designed L2s can also help, especially L2s optimized for specific applications (eg. high-volume trading, privacy...). These goals are even compatible with significantly lower slot times, thanks to Raul's work on erasure-coded P2P, and many other optimizations. The most high-value "product" of the ethereum blockchain, financially speaking, is ETH the asset. Ethereum secures $250 billion of ETH. The types of properties of Ethereum that I mentioned above are very good for ETH the asset. Nearly 90% of my net worth is in ETH, and most of the remainder is ~$40m of onchain fiat of which every dollar has already been allocated for some open-source biotech or software or hardware initiative. That said, there are aspects of supporting ETH the asset - *necessary* aspects even - that are outside the scope of the EF. This is where we need other heroes (some of whom hold more ETH than the EF does) to step in and help. EF has been recently thinking more about how it will relate to other such organizations, and give them needed initial support. EF will be a smaller ship than in previous years, a more opinionated one - in some cases more opinionated in ways that might be difficult to comprehend - but a longer-lasting one, and one suited to making sure that ethereum brings something meaningful to the world. We are grateful to all those inside and outside the EF who are helping to make this happen.

source:@namespace_eth

Demo 👇 Make your app's resolution ENSv2-compatible in 1 minute. No coding. Only natural language. And vibes ✨

100+ devs tested offchain subnames 20+ teams use them in production and i still get asked "but can it scale?" 850k+ subnames issued. 17M resolutions served. 0 contracts deployed. that's the whole point. if you're considering adding ENS.. go talk to @namespace_eth -🥷🥷🥷-

@jaestips_eth These are only for those that had been minted on our platform.

collections.eth is climbing up the ranks! very quickly!

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 ↓ discuss.ens.domains/t/temp-check-e…

ETHGlobal just killed one of the biggest bottlenecks in hackathons: the “empty repo” rule. For the first time, builders can bring existing products, open-source repos, and real startups directly into the hackathon itself. That changes the role of the hackathon entirely. Hackathons stop being isolated weekend demos and start becoming the acceleration layer for actual products. You can now: - continue your previous hackathon project - ship new features for your product - contribute to open-source infra you actually use - build something for some public goods protocol This is the right evolution for hackathons. Imagine spending a weekend: - contributing directly to open-source infra already used by millions - writing and implement your ERC draft you've been thinking about - finishing the ENSIP for @ensdomains you started weeks ago - coding a specialized @Uniswap V4 hook for some DeFi protocol - building a custom policy template at @namera_ai for your agent - contributing to Helios or Reth, and @VitalikButerin likes you :] - writing an MCP server for a protocol with no agent interface yet - etc. etc. etc. anything goes.. - or simply continue building your own product/startup. That’s a much healthier model for everyone. Less disposable demos. More compounding. More open-source contributions. More products that survive after the hackathon ends. It's less like: “build something random in 36 hours” and more like: “move meaningfully forward over a weekend.” Honestly, one of the most exciting emails I've received recently.

we will name *every* crypto user.

buildwithfern.com/agent-score/co…

Our docs are rated A (96%) on agentic consumption readiness. Meaning, they are ripe for AI agents to start building with ENS.

Hey, you don't have to deploy contracts or build custom infra to add ENS names or subnames to your app. Just letting you know. @namespace_eth (wink wink)

Most teams think ENS is just a vanity feature. It’s not. It’s a UX, identity, and trust layer for your product. With subnames, every user can have a readable identity like alice.yourapp.eth without you building naming infra from scratch. That means: - cleaner onboarding - safer payments - better trust - no transacting anxiety - universal accounts If you’re building a wallet, app, or chain ecosystem, this is much more practical than people assume.

Web3 made everyone be their own bank and then gave them account numbers like: 0x8f3a9y2c1e4bm9op32jKp... lol what's even better, every "bank (blockchain)" has their own unique account numbers and, get this if you accidentally send money from one bank to another bank using their account number you lose all the money. ===---===---===---===---=== ♪🎶🎵 financial freedom 🎵🎶♪ ===---===---===---===---=== we can't expect mass adoption like this... but man, if only there was a way to fix this.. to have one universal web3 username that stores aaalll of your wallet addresses 🤔

app.namespace.ninja/offchain?activ…

There is a new tab on our app 👀 => Build with AI check it out 👇

Namespace App already has clear signing, each action gives you a summary of what actually happens.

Ethereum Foundation @ethereumfndn

3 weeks ago

0/ Clear signing is now live. An open standard to end blind signing, making human-readable transactions default. This effort brings a major UX and Security upgrade to transaction signing on Ethereum.

160 443 2K 322K 360