NameHashLabs.eth

Agent identities is going to be a super fun and hard problem for software in the coming years. Most agentic systems today assume that the agent can do everything the user can do, and just operate as an extension of that user. This has worked well and is how most auth has worked for cloud software, and it has made integrations super easy over time. But then comes along systems like Openclaw, and suddenly we get a new view into what becomes possible with agents that can operate on their own. And when you have many of them running in parallel. You start to work with them like a colleague, not just as an extension of what you do. But of course this now introduces an all new complexity than the traditional approach. What if you want an agent to access only a small subset of your data? What if you want an agent to have its own sandbox to operate in without any risk of a blast radius if it goes off the rails? What if you want to create an agent that can work with others, without you seeing everything it’s doing? For all of these cases, agents will start to need their own identities inside of platforms. To do this, we likely will need new mental models for how we delegate controls and access to them, how you handle authentication, who gets to manage them in an organization and so on. Lots to figure out in this space right now.

A quick update on ENSv2: we have made the decision to deploy ENSv2 exclusively on Ethereum L1 and to cease development of Namechain. To be clear, ENSv2 will still ship. The only thing that’s changed is that instead of deploying ENSv2 on our own L2 stack, it will be deployed on L1. It is important to note that ENSv2 is ultimately an upgrade to ENS as it exists today — it’s still ENS! Regardless of where it ultimately gets deployed, it does not fundamentally change ENS the protocol nor does it change any part of our mission and ultimate goal of building the identity layer on Ethereum. The design for ENSv2 was always intended to work fully as designed, whether deployed on L1 or L2. Our product roadmap does not change. We have detailed progress on the ENSv2 Hub to show what exactly v2 will mean for you, and what the team has been building: giving each name its own registry (making your .eth names more powerful and customizable to your own rules!), building two brand new apps from the ground up (both deployed to testnet this week), and much more. I am so excited for this release (soon!) and think it will completely change the way you interact with your own ENS names. The timing of this decision coincides with a broader discussion about the role of L2s in Ethereum. I continue to believe that L2s play a vital role in extending the value of the world computer that is Ethereum, and ENS will continue to support as many chains as possible. In fact, very soon anyone will be able to register a .eth name regardless of which EVM chain they are on — meaning that even if your assets live on Optimism or Arbitrum, it’s a one-click process (no bridge, no gas tokens). We also continue to believe in a multi-chain world beyond EVM chains (a reminder that ENS has and always will support your addresses across major chains like Solana, Bitcoin, and more). We have published the detailed rationale for the decision to stay on L1 on our blog, and I encourage you to read it (in the QT here!) The .eth stays on 🫡

Received an notification of having received ether on an address of mine (real ether, albeit very little). Went on to check and it was trying to mimic another address of mine (!) and it had cloned 12 characters! 4 in the beginning and 8 (!) in the end! Dedicated phishing attack!

LATEST: Ethereum just processed a record 2.89M daily transactions, the highest in its history.