一名 Web3 以及 ENS 的用户，期待中文世界可以更加了解 ENS 和 ENSDAO。
Joined January 2021
- Tweets1.5K
- Following529
- Followers1.2K
- Likes3.9K
liubenben.eth retweeted
以太坊域名服务 ENS 宣布，ENSv2 已在以太坊主网上线，新协议与新版 ENS App、ENS Explorer 同步推出。ENSv2 允许每个名称为其下级名称设立独立注册表，并提供更细的权限设置，可由多方共同管理同一命名空间。已有 40 余个团队完成 v2 适配，包括 1inch、Aragon、Arbitrum、Jumper、Lighter、MetaMask 和 Safe。现有 ENS 名称继续有效，无需重新注册；符合条件的 .eth 名称可选择升级至 v2。ENS 还同步发行 ENSv2 纪念 NFT。wublock123.com/news/ensv2-is…
liubenben.eth retweeted
ENSv2 is live on mainnet! Migrate your names at app.ens.domains and you will eligible for this super cool commemorative NFT!
ENS has been my life for the last decade and I'm so proud of this team for bringing the next version of ENS to make the foundations for the future of the internet.
Let's go 🚀
liubenben.eth retweeted
There are a few moments in ENS history that are as momentous as this. We’ve been building for almost 10 years already and this is really the foundations of the next few decades where a programmable, permisionless naming system will be required to shape the next sovereign internet
The vote to activate ENSv2 on Ethereum mainnet is now live.
This is a major step toward launching the next generation of ENS, with the decision in the hands of the DAO.
Read the proposal and vote ⤵
ens.gov.blockful.io/proposal…
liubenben.eth retweeted
The vote to activate ENSv2 on Ethereum mainnet is now live.
This is a major step toward launching the next generation of ENS, with the decision in the hands of the DAO.
Read the proposal and vote ⤵
ens.gov.blockful.io/proposal…
liubenben.eth retweeted
gm, we're the ENS Foundation 👋
Our mandate: represent ENS at ICANN, IETF and W3C, pursue stewardship of the .ens TLD, engage on policy, and protect the brand, alongside @ensdomains and the ENS DAO.
Here's who's behind it 🧵...
liubenben.eth retweeted
1/
🚨 New: ENS has published how pricing, discounts and the grace period change with ENSv2.
If you own a .eth name, this affects you. Here's what it means, with examples for non-technical people 🧵
liubenben.eth retweeted
Back from @Sibos.
8 years ago when Consensys attended Sibos, Ethereum was considered to be a curiosity. (It was also the same week as Devcon Prague, so I opted for the cypherpunks over the suits).
This year almost every major bank and financial institution was pitching tokenization or stablecoins, and I left SIBOS feeling very optimistic about ENS and our place in the industry. Some notes:
1). The pitch has converged on the two things only blockchains really deliver: 24/7/365 markets and settlement that's near-instant. Nobody's debating if tokens and blockchains are the right stack. Clients and customers are actually demanding it. The big questions are how it should be structured and who gets to run it.
2). Maybe I’m projecting, but I couldn’t help but notice an underlying current of anxiety. (Maybe it was a panel literally titled, "Can tradfi fix the experience before DeFi wins the race?”)
Imaging being a specialized infrastructure provider like a CSD watching Coinbase, Robinhood and Stripe verticalize the financial stack (see: Coinbase’s CFTC approval for its own USDC-native clearinghouse with 24/7 settlement).
If you can issue, trade and settle onchain, where does that leave the middle?
3). The Standards Forum discussions around identifiers were the most natural fit for ENS. TradFi runs on ISINs and LEIs and identity data lives in these arcane formats like ISO 20022. One of the creators of this standard described what he does as "creating an esperanto for finance," which is honestly a good description of what ENS does for onchain identifiers.
ENS announced on Monday that we are working with @GLEIF to bring LEIs into ENS names, so the work is already happening.
teapawt.net/ensdomains/status/2104…
But we also need ENS to be incorporated into ISO standards. The syntax of onchain naming must be incorporated into the syntax that all banks already use.
4). Swift is building too: a ledger, an orchestration layer, and an interbank liabilities registry. And it’s running on Besu (Ethereum ftw!). ENS being part of the standards means its easier to translate when Swift's ledger begins gaining adoption among its partner institutions.
And one final note: No other conference puts you in a room with the people actually running these projects and gets you real answers on the spot. Sibos is remarkably accessible. Thank you @swiftcommunity for having us.
ENS Labs and @GLEIF are exploring how organizations can link their ENS name to a verifiable Legal Entity Identifier (vLEI), creating one persistent, verifiable identity onchain.
Learn more ⤵
ens.domains/blog/post/ens-gl…
liubenben.eth retweeted
We'll also keep maintaining every item from our original proposal, including:
- Anticapture, to monitor the security and health of ENS governance
- The ENS governance front-end, making it easier for delegates to vote on ENS proposals
- The Incentives Program, aiming to bring more delegated $ENS to active governance participants, making the DAO more secure
liubenben.eth retweeted
so once a year, the biggest payments and identity providers get together in geneva to determine the future of digital identity.
by the end of 2026, every country in the EU is required by law to launch their own digital wallets.
how these wallets and credentials should interact and work with each other was a hot topic, alongside the obvious focus on agent identity.
the conference was strictly governed by the chatham house rule, so you won’t find any quotes or people’s names in the recap.
this doesn’t make them less relevant, though!!
the people were great
full recap ⬇️
GDC 2026 brought together conversations around digital identity, payments, AI agents, credentials and tokenized assets.
Across all of them, the same infrastructure questions kept coming up: identity, trust, continuity and interoperability.
Here’s the recap from @mely_jpg 🧵
liubenben.eth retweeted
ENS adoption doesn’t always look like another .eth registration.
ENS is the naming protocol, .eth is one namespace within it. DNS names can be ENS names too, because ENS was designed to extend the internet’s existing naming infrastructure rather than require everyone to replace their names.
That’s why projects can build on .eth subnames, like base.eth and uni.eth, or use DNS names, like world.id. These are different namespaces using shared ENS infrastructure, not separate naming protocols competing with ENS.
When a naming service independently invents a suffix, issuing those names onchain doesn’t establish authority over that suffix in DNS. Separate systems can end up assigning the exact same name to different people. That creates confusion about whose name an app is resolving, with real consequences when names are used to send money. (.crypto, .sol, .wallet, .agent....)
ENS takes a different approach: integrating with DNS is explicitly part of its constitution. DNS compatibility isn’t a distraction from the protocol’s mission. It’s part of that mission.
I’ve been working behind the scenes with existing web3 naming services to encourage this approach. For projects that already launched standalone namespaces, an ENS/DNS bridge can give their communities a path into shared infrastructure under an existing DNS domain. That’s the progress I’m highlighting.
This goes hand in hand with encouraging apps to support the ENS names people already have. Connecting more naming communities to ENS and making existing ENS names usable in more apps are complementary goals.
I’m not asking everyone to register another name. I’m advocating for projects to build naming systems that work together.
Welcome .hl users to ENS and the global namespace. 🤝
.@hlnames has integrated ENS to power a universal namespace for the @hyperliquidx ecosystem.
In choosing ENS, HL Names has made it easier to navigate the Hyperliquid ecosystem and beyond ⤵
liubenben.eth retweeted
This is how you launch a namespace.
@hlnames imported a DNSSEC enabled DNS name (hl.hn) into ENS.
No protocol fee. Permissionless. Resolves wherever ENS already works - most wallets and dApps and in DNS.
alice.hl → alice.hl.hn
Tap into the global namespace instead of inventing a TLD out of thin air that collides if ICANN later issues the matching string.
.@hlnames has integrated ENS to power a universal namespace for the @hyperliquidx ecosystem.
In choosing ENS, HL Names has made it easier to navigate the Hyperliquid ecosystem and beyond ⤵
liubenben.eth retweeted
Introducing CitizENS: a new series spotlighting the people building, improving, and shaping ENS.
First up: @estmcmxci, whose work helped make DNS imports dramatically cheaper.
What makes a name trustworthy? ↓
liubenben.eth retweeted
ETHShanghai 还有三天多就开始啦！由 @ETHPanda_Org 社区联合多家合作方、赞助方一起组织推动的免费公益技术交流活动，每年一次，中国大陆最大的以太坊活动！
主要交流合法合规的区块链技术、行业前沿进展。本期主题是以太坊文艺复兴，以重新思考我们从哪里来、失去了什么、AI x Web3、我们到哪里去为主线，穿插以太坊生态的最新进展。
我本人将出席、组织下午的密码朋克、密码学 Panel。将跟密码学专家、密码朋克们一起为大家解读：
1. 密码朋克是什么？
2. 三次密码战争（Crypto Wars）？
3. 最新密码学和加密动态？
4. 加密技术以及在以太坊的应用？
等等。还在设计中，感觉很多可以聊的，ZK、抗量子等等等等，欢迎你留下感兴趣的问题。
欢迎上海的朋友报名面基！
liubenben.eth retweeted
After nearly three years as General Counsel of ENS Labs, the ENS Foundation's Board has formally appointed me Executive Director and Chief Legal Officer. The tokenholders voted the Foundation a serious mandate. Here's what we're built to do. 👇
liubenben.eth retweeted
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/identi…
liubenben.eth retweeted
The latest round of rewards for $ENS holders who delegate to Active Delegates has arrived.
This month, thanks to 17% growth last month, a surprise: 3,000 more $ENS to incentivize more delegations.
A pool of 8K $ENS will be distributed to those who delegate their $ENS and help improve ENS DAO's security.
If this growth keeps up, incentives could increase: from 10K ENS up to 30K $ENS 👀
Start delegating your $ENS NOW and check out Active Delegates, link below 👇
incentives.ens.blockful.io/
