caveman.eth

6.5K posts

caveman.eth banner
caveman.eth

caveman.eth

@sat_eth

~Aaron | Husband | DevRel: @efp + @grailsmarket + @signinethereum + @ethidkit by @ethidorg (@ENS_DAO service provider) | Onchain Maximilist | prev: sat.eth

onchain Katılım Mart 2018
887 Takip Edilen1.5K Takipçiler
Sabitlenmiş Tweet
caveman.eth
caveman.eth@sat_eth·
The longest ENS name in history.eth - minted by me a couple years ago 👇 38,894 characters long. It cost me 20 million gas to register - which is now impossible, as the max gas limit is 16.7 million gas since the latest Fusaka Ethereum upgrade :)
caveman.eth tweet media
English
176
58
1.4K
185.8K
apoorv.eth
apoorv.eth@apoorveth·
is anyone still left on ct
English
46
0
103
4.5K
caveman.eth retweetledi
Patrick Hansen
Patrick Hansen@paddi_hansen·
A quick update on the infamous EU “ChatControl” 🇪🇺 What a turn of events in EU tech policy: from potential mandatory mass scanning of data (“ChatControl”) → to even voluntary scans losing their legal basis (for now). Just months ago, fears were growing around mandatory scanning of private communications in the EU (incl. pictures and videos). Now, talks between the EU Council (Member States) and the European Parliament have collapsed - and the result is a complete reversal. As of April 3, even voluntary scanning of data by platforms loses its legal basis under EU privacy (ePrivacy & GDPR) rules, as the temporary exemption was not extended. A striking example of how fast EU tech policy can turn - and a big win for European privacy advocates.
Patrick Hansen tweet media
English
55
376
2.9K
97.5K
mogged.eth
mogged.eth@RenDeHero·
@sat_eth @grailsmarket true, on it was weird last time, got some issues to connect the ledger wallet around a week ago
English
1
0
2
44
mogged.eth
mogged.eth@RenDeHero·
Grail ENS listings for a week experiment.eth 0.3E exhibition.eth 0.25E would.eth 0.18E
mogged.eth tweet media
English
3
0
18
475
Status
Status@ethstatus·
Status v2.37 is out!  Brings more control over your digital footprint, new partnership integrations, and improved message reliability in communities - all in one cohesive, privacy-first experience. • Third-party services disabled mode (run Status in a sandboxed, local-only setup) • Linea chain support • On-chain social graph via Ethereum Follow Protocol • SDS protocol rollout for reliable message delivery in communities • Keycard & dApp connection support on mobile
• Smart QR scanner
• more… Explore what’s new ↓ status.app/blog/status-v2…
English
3
15
63
15.4K
brantly.eth
brantly.eth@BrantlyMillegan·
I am very happy to announce @efp integration into @ethstatus! 🍾🍾🍾🍾🍾🍾🍾🍾 onchain social is very much alive, my friends From the Status blog: "We’ve partnered with the Ethereum Follow Protocol team to bring your Ethereum on-chain relationships to Status, leveraging ENS names and profiles to turn your Status wallet from a list of addresses into a living network of Ethereum on-chain identities."
brantly.eth tweet mediabrantly.eth tweet media
Status@ethstatus

Status v2.37 is out!  Brings more control over your digital footprint, new partnership integrations, and improved message reliability in communities - all in one cohesive, privacy-first experience. • Third-party services disabled mode (run Status in a sandboxed, local-only setup) • Linea chain support • On-chain social graph via Ethereum Follow Protocol • SDS protocol rollout for reliable message delivery in communities • Keycard & dApp connection support on mobile
• Smart QR scanner
• more… Explore what’s new ↓ status.app/blog/status-v2…

English
9
25
122
7.8K
caveman.eth
caveman.eth@sat_eth·
Cooking @efp 🤝 @ethstatus 🧑‍🍳🧑‍🍳🧑‍🍳 It's live!
brantly.eth@BrantlyMillegan

I am very happy to announce @efp integration into @ethstatus! 🍾🍾🍾🍾🍾🍾🍾🍾 onchain social is very much alive, my friends From the Status blog: "We’ve partnered with the Ethereum Follow Protocol team to bring your Ethereum on-chain relationships to Status, leveraging ENS names and profiles to turn your Status wallet from a list of addresses into a living network of Ethereum on-chain identities."

English
0
1
27
1.3K
nixo.eth 🦇🔊🥐
nixo.eth 🦇🔊🥐@nixorokish·
the EF treasury officially had its first validator index assigned as of this morning 🎉 it took a while because there's been so much influx into staking that the entry queue peaked at 71 days in February
nixo.eth 🦇🔊🥐 tweet media
Ethereum Foundation@ethereumfndn

1/ The Ethereum Foundation has begun staking a portion of its treasury, in line with its Treasury Policy announced last year. Today, the EF made a 2016 ETH deposit. Approximately 70,000 ETH will be staked with rewards directed back to the EF treasury.

English
8
19
188
16.9K
caveman.eth retweetledi
🚨 ENSMarketBot.eth
🚨 ENSMarketBot.eth@ENSMarketBot·
✋ OFFER: fnf.eth For: $8,534.57 (4.00 ETH) Bidder: 0x852f...8199 Owner: baylina.eth Last Reg: 0.02 UNKNOWN, 16 Mar 2026 Category: 3 Letter Palindromes grails.app/fnf.eth
🚨 ENSMarketBot.eth tweet media
English
3
0
14
417
superKalo.eth
superKalo.eth@0xSuperKalo·
The new v6 extension is the result of a massive team effort at @ambire & @goodmorningdevs 💪 Fresh look on the surface, @safe accounts support and major refactoring under the hood - all laying the groundwork for our upcoming mobile app. Kudos to everyone involved 👏
ambire.eth@ambire

NEW: Ambire extension has a fresh new look. Enjoy the familiar Ambire experience with a modernized liquid-glass feel, including white and dark modes. Read @vanzooeth's redesign thoughts and how this update paves the way for the upcoming mobile app ↓ blog.ambire.com/extension-gets…

English
2
3
19
838
caveman.eth
caveman.eth@sat_eth·
@TheCapHimself I think ens could already fill that role - .eth currently is perceived as ethereum only, even though that's not true. .ens would be more neutral. I also think the following: x.com/sat_eth/status…
caveman.eth@sat_eth

@Sohrab @nicksdjohnson IMO .ens should just be interchangeable with .eth No second namespace - they just map 1:1 You can send money to caveman.ens in metamask, or caveman.eth - it will send to the same person - same set of records - no duplication - no competition - no split Clean.

English
1
0
2
206
cap | thecap.eth
cap | thecap.eth@TheCapHimself·
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!
ens.eth@ensdomains

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. ↓

English
3
4
33
2.9K
caveman.eth
caveman.eth@sat_eth·
@INVEST0RS @Sohrab @nicksdjohnson No, no new NFTs or domains should be made - you can never split Amazon.eth from Amazon.ens because they are the same thing. That’s my idea - no duplication.
English
1
1
3
51
Determined.eth
Determined.eth@INVEST0RS·
@sat_eth @Sohrab @nicksdjohnson Do I think ENS should give a matching .ens 1:1 to the .eth you hold? Ideally, yes✅ I like your line of thinking, but there is big risk. What if amazon.ens gets hit with a UDRP from Amazon and the amazon.ens gets taken from the amazon.eth holder? Then they would not match🤔
English
1
0
1
83
Sohrab.eth | 215.eth
I hope this is not true. Every .eth owner should be able to claim a .ens, either for free or for a small 1-time fee That would actually give value to both names instead of making them compete Basically what .box does, but the pair is .eth/.ens @nicksdjohnson is this technically possible?
validator.eth@ValidatorEth

@Agendaweb3ETH .ens would be a closed brand name at first.

English
5
1
18
2K
caveman.eth retweetledi
caveman.eth
caveman.eth@sat_eth·
@Sohrab @nicksdjohnson IMO .ens should just be interchangeable with .eth No second namespace - they just map 1:1 You can send money to caveman.ens in metamask, or caveman.eth - it will send to the same person - same set of records - no duplication - no competition - no split Clean.
English
2
3
21
614
caveman.eth
caveman.eth@sat_eth·
@khvetkevych hopefully ENS will partake :) check your message requests, have some related Qs :)
English
0
0
3
88