ai@xns (@BitmanNFTs) header
ai@xns (@BitmanNFTs) profile picture

₿itman ₿itcoin | Ethereum | NFTs

Joined January 2016
Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)Photo by ai@xns (@BitmanNFTs)
ai@xns retweeted
No registrar. No DNS. With a local resolver, a .d3 site loads straight from Ethereum. Nothing between you and the chain for an attacker to hijack.
1
2
2
4
1,227
Look at this list of ENSv2 "features" that the community is supposed to be a excited about. 😭 Dropped ETH, introduced oracle dependency, introduced terrible USDC UX, increased prices, introduced smart contract complexity hell.
1
3
14
685
Another great UX upgrade as part of ENSv2.
Can't believe ENSv2 requires USDC just to set a Primary Name. Is this supposed to make sense to anyone?
4
2
5
525
You have to feel the magic, to understand it. Head over to app.d3.limo, register a domain of your choice (e.g., amara.d3), publish a html file directly on the blockchain and immediately view it via amara.d3.limo. No configuration of DNS records needed.
No registrar. No DNS. With a local resolver, a .d3 site loads straight from Ethereum. Nothing between you and the chain for an attacker to hijack.
2
6
500
ai@xns retweeted
Meet Stan. Stan has a .eth name. Stan has to renew it every year. If Stan forgets, the next payment to Stan can land with whoever grabs the name. Don't be Stan. Get a name that never expires. 0.001 ETH, paid once.
2
2
8
634
ai@xns retweeted
Devcon week in Mumbai. You'll share your wallet address a dozen times this week. Over chat, on slides, on QR codes. Share a name instead. alice@eth Never expires and can never point to another address. 0.001 ETH, paid once. x2xpay.me
1
2
3
469
ai@xns retweeted
A .d3 domain is an ERC-721. While you hold it, you can update the site. Burn it, and the content is frozen for good: no owner, no edits. For generative art or defi frontends, that's a final state anyone can verify. app.d3.limo
3
3
663
ai@xns retweeted
D3 is a home for generative art. Create something beautiful. Put it onchain. Give it a permanent home. > Register a domain at app.d3.limo, e.g. p0ng.d3 > Publish your artwork onchain > Share it at p0ng.d3.limo Your art deserves a home that lasts.
1
3
1
3
1,621
Correction. It’s just bad UX. The ENS team are masters in creating the worst user experience possible. 🤦‍♂️
🤣🤣🤣 As if ripping off users with annual subscriptions to a broken naming system wasn’t enough, now ENS users are getting ripped off with additional frontend fees. The gift that keeps on grifting.
2
7
526
🤣🤣🤣 As if ripping off users with annual subscriptions to a broken naming system wasn’t enough, now ENS users are getting ripped off with additional frontend fees. The gift that keeps on grifting.
I just renewed a bunch of my @PokemonENS @ensdomains names. I cant even believe how bad the new ENS app is. You cant even use ETH for renewals?? And the "total" is not the real total. I used my own FE and saved over 10% that they are adding in unexplained fees. Come on guys
2
2
1
8
1,266
ai@xns retweeted
Some things in life should never have a subscription model. Imagine your car’s seatbelt suddenly stops working while you’re driving because you forgot to renew your subscription. Absurd, right? The same applies to payment identifiers. Nobody should be able to claim your payment identifier and receive funds intended for you simply because you forgot to renew it. Some things should be permanent by design.
2
2
416
ai@xns retweeted
That’s insane.
Replying to @ordnals @ENSfndn
Imagine defending a financial system where users can lose money simply because someone forgot to renew a name. And then blaming the victims for not reading the manual. 🤡 The $12 million loss due to ENS dropcatching (see linked post) comes from independent research, not me. I’ve personally witnessed such a loss. Address poisoning is a problem. ENS dropcatching is another. You solve one problem by introducing another one. Permanent payment identifiers eliminate this entire class of risk. That’s called fixing the problem at its root. Happy to give you a lesson in thinking from first principles.
2
2
701
ai@xns retweeted
In address poisoning, scammers send you a tiny transfer from a lookalike address and wait for you to copy it from history. There's nothing to copy when you send by name. alice@eth can never expire or point to another address. x2xpay.me
3
1
3
949
ai@xns retweeted
💡 How to send crypto by name
💡How to register an XNS name
2
4
585
ai@xns retweeted
💡How to register an XNS name
3
2
7
901
ai@xns retweeted
Store your frontend directly on the blockchain. app.d3.limo
⚠️How can you tell a DNS is Hijacked when you visit an official website?..⚠️ At least 12+ domains got hijacked last night, serving wallet drainer code on their official website.. All but 5 have now moved their DNS to Vercel/Cloudflare to mitigate and those 5 are still compromised, DO NOT VISIT! The URL can be 100% correct, but the website you're visiting can still be malicious. This compromise did not break anything from the teams flow, setup, compromise anything they did, it appears someone inside name(.)com (The registrar) change the nameservers to the domains. If you use them as a registrar I would consider moving away and at minimum setup cloudflare for hosting/filtering. If you are a user, there really isn't a way to detect this unless you are checking WhoIs, DNS updates, ASN numbers, and many more which most don't. The only way to tell is that when you go to the website it will ask for your seed phrase/private key, or prompt you to sign an odd transaction. The transaction part is tough to spot which is why I recommend always using @RevokeCash extension to help spot this for you with the transaction simulator... If you are a business and not using cloudflare, let's talk, this is basic proper security on domains outside of domain lock, etc. You have to be prepared ahead of time to prevent/mitigate this in an instance moment! Stay Safe & Stay Vigilant
2
3
605
Time to host your websites onchain. @d3domains
Several websites were compromised yesterday, and some of them remain compromised still. We recommend to not use too many crypto related websites for the time being. If you already interacted with one of the compromised websites, make sure to check for any unexpected approvals. And check out the Revoke Sidekick extension in partnership with Fairside that simulates transactions before signing them, which can really make a difference for these kind of hacks.
4
2
1
14
1,497
Has the expiry issue for subnames been fixed in ENSv2? Asking for a friend. @ENSfndn
Another failure mode in the ENS system related to subnames: ENS markets subnames as "free", but the operational and configuration complexity behind them is enormous. The linked example shows that extending the expiry of the parent name does NOT extend previously created subnames. Meaning: - parent may expire in 2079 - subname may still expire in 2051 because expiry is effectively snapshotted at registration time This creates massive confusion and hidden rerouting risks. Users may believe that their subname lasts as long as the parent, but in reality, it depends on how and when the subname was configured, wrapped and created. Expiring ENS names are already dangerous enough. Adding layered subname logic with different expiration dates, wrappers and delegated control makes the system even harder to reason about safely. Stay safe out there.
1
2
4
759
What happened to @Stelecoin? The guys that essentially copied xns.name website, slapped a token on Pump.Fun to it and called it Powered by Solana 😂 All while saying "Naming Layer on Ethereum" on their website and linking to the XNS GitHub and x2xPay.me app. They would be better off working together with me rather than trying to run their own show. 🤷‍♂️
4
2
6
434
Instant settlement is a bug, not a feature.
1
2
4
369