Community and Ecosystem @ensdomains validator.uni.eth validator.base.eth validator.gemini.eth
United States
- Tweets 26,453
- Following 3,150
- Followers 14,655
- Likes 171,162
Pinned Tweet
Ethereum Name Service is a protocol that enables users to register human readable domain names for their crypto addresses, making sending and receiving TXs more user friendly. ENS is multi-chain, with .eth working across 100s of coin types, including BTC, SOL, EVM L2s, + more.
232
92
608
59,763
validator.eth retweeted
Pragma Tokyo 🇯🇵 | September 26 ∙ 12:20pm
From Names to Namespaces: When the Reader Is a Machine with @jefflau of @ensdomains.
A look at what naming systems need to do when machines become the readers.
1
7
1,644
validator.eth retweeted
As agents become economic actors, they need identities that survive changing keys and can be independently verified.
At Pragma Tokyo, @JeffLau of @ensdomains presents Namespaces as a foundation for verifiable identity and delegated authority.
2
21
2,522
Claim site is live. If I was able to save your NFTs, you can now reclaim them. You will have to revoke the PaymentProcessor approval first, if you haven't already.
You may also opt to donate as part of your transaction.
nftsaresafu.xyz/
179
282
1,221
67,756
validator.eth retweeted
Wallets that revoked their Magic Eden / Limit Break Payment Processor approvals before the attack kept $3.9M in NFTs and tokens safe, including 70 Bored Apes and 220 WETH.
Make sure to check if you're safe: revoke.cash/exploits/magic-e…
11
19
93
11,415
validator.eth retweeted
a short update on the limit break / magic eden incident response
as a reminder, no @opensea systems or contracts are affected
> known-impacted ERC721 NFTs have been flagged on OpenSea & cannot be sold
> newly exploited NFTs are automatically flagged (limiting exploiter access to offers)
> users with open approvals will see a banner on opensea.io with links to revoke on @RevokeCash
we’re continuing to do all we can to help limit the impact of the industry incident on as many users as possible
thanks to @0xQuit & @RevokeCash for their work & support on this
we're aware of a security incident affecting Magic Eden & Limit Break
the team is working to make sure that these items are not able to be re-sold on @opensea
so far over 3,000 items have been marked as stolen & prevented trading
@RevokeCash have an exploit checker live here to see if you've approved your assets for ME here:
revoke.cash/exploits/magic-e…
note: all approvals to OpenSea are safe
48
37
213
35,943
validator.eth retweeted
workemon.eth presenting @ensdomains at @ETHGlobal Tokyo right now
5
10
50
2,268
At 9AM EST today somebody abused a bug in Payment Processor V2 to steal 10 Meebits, 50 Otherdeeds, 10 WoW, and 235 Desperate Apewives.
It wasn't until over 12 hours later that somebody reported it to me, and upon digging in I realized that a great many NFTs were subject to the same exploit.
I got in touch with the team over at LimitBreak and they quickly paused Payment Processor V3, which was subject to the same exploit. Unfortunately, V2 was not pausable, so the only path towards protecting affected assets was to run a whitehat operation.
Similarly, V3 on ApeChain is temporarily in a state where it cannot be paused, so ApeChain assets approved to V3 needed to be saved as well.
All in all, we rescued 23,155 NFTs worth north of $5.7M USD.
We later discovered that a similar exploit could be used in reverse to steal WETH. 660 WETH was at risk, which we unfortunately were not fast enough to recover. Apologies to those affected.
Shout out to @Boomskite for flagging the initial exploit tx to me, and @coffeedev @0xjustadev and @whiteoakkong for acting quickly and assisting with the recovery.
All NFTs are safely relocated. Soon, owners will be able claim them back after revoking the exploitable approvals.
Addresses to revoke below.
6
26
1,601
validator.eth retweeted
🚨 Limit Break Exploited 🚨
Ever traded NFTs on Magic Eden's Ethereum marketplace? Your wallet probably still approves Limit Break's Payment Processor, which now has a known vulnerability.
Check if you're exposed and revoke:
revoke.cash/exploits/magic-e…
63
271
796
214,679
validator.eth retweeted
Heading to @KBW2026 next week? 🇰🇷
We’re bringing ETHGlobal Happy Hour to Seoul on Sep 29 from 6–9PM!
Special thanks to our partners: @ensdomains @ethconf @0G_labs @UniswapFND @1inch @hedera @Yellow @worldnetwork @jumperapp
RSVP: luma.com/ethglobal-happyhour…
2
13
59
6,993
RT @ensdomains: Tokyo, we’re coming 🇯🇵
ENS will be at @ETHGlobal Tokyo this weekend with $10K in prizes, an ENSv2 workshop, and a talk at…
8
66
RT @ensdomains: Not every ENSv2 subname needs its own token. Some can live as records in a resolver; others can have separate owners, permi…
9
78
RT @ensdomains: Most tools abstract away how ENS actually works. The Explorer lets you see the protocol in full.
@gregskril walks through…
6
78
validator.eth retweeted
Bring friends, earn together. The Fluidkey Referral Program is live ✨
To get started head to the app's + section!
1
3
16
969
validator.eth retweeted
join eggy and 1985 for the inaugural ens turbo bull power hour (working title)
nitter.net/i/spaces/1DxLdZaRpBLxm
7
7
22
877
RT @mely_jpg: so once a year, the biggest payments and identity providers get together in geneva to determine the future of digital identit…
12
4
RT @ensdomains: GDC 2026 brought together conversations around digital identity, payments, AI agents, credentials and tokenized assets.
Ac…
10
76
validator.eth retweeted
🎥 going live with @gregskril (and co-host @clawdbotatg)
🫡 he is a true sloperator!
⚙️ we'll learn about him and his stack
📋 will also ask about ENS v2 and other cool things
🤖 research says he is a "prolific shipper of tiny weird apps" nitter.net/i/broadcasts/1vJpPNWqd…
8
8
45
7,341
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 ⤵
11
11
82
3,917