𝓻𝔃𝓴 retweeted
Had this discussion a million times: all PoW currencies fail because they're not a trapdoor functions, energy is spent better elsewhere rather than burned for concensus, "privacy" isn't formally or even rigorously verified so at best it's a false sense of security.
Don't bother responding.
𝓻𝔃𝓴 retweeted
Updated nano assets brand kit is live!
Everything you need to show nano in your app, shop or article: Ӿ kit, logos, payment badges, colours and typefaces all in one handy toolkit. nano:native
assets.nano.org/
𝓻𝔃𝓴 retweeted
Glad to see Monthly candle turning Green from the 1st week of the month. After a Year 🤝🗣️ beautiful.
#Nanovember Is here 👀 Let’s Go sir 🗣️
nano:native
𝓻𝔃𝓴 retweeted
One thing I really love about $XNO is that is just works as it is. It doesn't need any second layers or complicated smart contracts to be usable. This is especially important at a time where complicated setups in other projects are creating attack surfaces for hacks.
𝓻𝔃𝓴 retweeted
Well $XNO has no smart contracts. Not even a memo field 🥲
nitter.cf/connyb/status/21140095…
The Binance $5.6B drain is a masterclass in modern EVM exploitation.
It wasn't a complex logic bug. It was an EIP-7702 delegation hijack:
1. Setup: Attacker funds 0x7c86 via Tornado Cash, deploys a sweep contract (0x63e8), and runs three live dry-runs on external wallets.
2. Execution: Attacker submits an EIP-7702 batch with 50 pre-signed authorizations (nonce n to n+49) to hit Binance 14's moving nonce window.
3. One authorization hits. Instantly, Binance 14 (an EOA) is reprogrammed to run the attacker's contract bytecode.
4. Execution looks totally organic: Binance 14 sweeps itself clean. Internal threshold alerts don't trigger because, from the nodes' perspective, the hot wallet is just executing its own transaction.
5. Binance 16 immediately auto-refills 28,000 ETH due to automated treasury rebalance scripts, feeding the exploit loop.
The cold truth: you cannot forge an EIP-7702 delegation list.
For this to execute, the attacker already held the raw private key or unconstrained signing access to Binance 14's HSM/KMS.
But hey, 5.64 billion drained across ETH, BTC, and Tron. 2.54 billion frozen by Tether, Circle, Ripple, and World Liberty within hours.
Code is law until the stablecoin admin keys log in.
Binance got bailed out by the very centralized choke points the cypherpunks warned you about.
Hardware wallets leak your home address.
Centralized exchanges leak the keys to the kingdom.
Self-custody on native, non-delegated chains remains the only honest baseline.
At least you know what to avoid.
𝓻𝔃𝓴 retweeted
My biggest concern is that if there is a clean sweep by Democrats of the House, Senate and Presidency in 2028, they will:
1. Make DC and Puerto Rico states to gain a strong majority in the Senate.
2. Open the borders and legalize everyone living in America illegally to cement a permanent majority.
3. Increase the size of the Supreme Court to gain an immediate majority.
This would result in America becoming a permanent one-party state and the end of democracy in any meaningful sense of the word.
All that is needed to ensure this doesn’t happen is 51 Republican senators in 2029. That is why you should vote for Republican senators this election. Other reasons are irrelevant compared to this one.
𝓻𝔃𝓴 retweeted
@krakenfx is the #1 exchange in the world. Always has been. nano:native
ok safe to say binance is pwned
The biggest assets were approximately:
• 1.615B USDT
• 62.6M RLUSD
• 29,934 wBETH
• 11,372 XAUt
• 6.19M UNI
• 198.4M ENA
• 7.175T PEPE
• 27.8M USD1
• 2.26M LINK
• 127,853 AAVE
about $2.5B at the explorer’s prices.
1. The attacker deployed a delegate contract, 0x63e842b0...73e9c6fAe, from the relayer at 15:59 UTC.
2. About four hours later, the relayer submitted an EIP-7702 authorization transaction
That installed the malicious 7702 delegate code on Binance 14.
3. The relayer then made a call to Binance 14, executing the delegate code, and transferring Binance 14’s ETH and token balances.
4. The calldata is labeled sweep(address, address[]). The second argument is a list of recognizable token-contract addresses plus the zero-address (eth).
5. The same relayer later used the same delegate to move 780M USDC from Binance Hot Wallet 34 into the same pool
• The relayer 0x7C... was funded by three Tornado Cash 0.1 ETH withdrawals over the prior two days.
• The same pool also received 28,005.6 ETH from Binance 16 24 seconds after the main sweep.
• The pool then forwarded 195,460 ETH to a fresh, unlabeled EOA
• That EOA has only one transaction and currently holds the 195,460 ETH.
What's a bit unclear is why the relayer was needed in the first place. If they had the private keys to the Binance wallets, they could have just sent the assets out in an atomic bundle without needing a relayer at all.
So it seems likely that they didn't have the private keys and instead just had the 7702 auth signatures, which must have been phished somehow.
I think we can go ahead and assume DPRK.
𝓻𝔃𝓴 retweeted
I always thought nano:native adoption would come when people recognized it as the closest thing to Satoshi’s vision of neutral, fair, decentralized money. But perhaps AI will recognize its true potential before humans do, and drive adoption simply by putting it to use.
𝓻𝔃𝓴 retweeted
In Europe the Chinese government is trying to silence a soccer player with financial threats. In Taiwan they are threatening the old fashioned way, by arranging automobile accidents
Both cases show the lengths the CCP will go to censor people outside of country and it will only get worse
𝓻𝔃𝓴 retweeted
This is what happens when you shill for China, you get praise, opportunity, money and the support of the Nationalists. However you cannot have an opinion or even jokingly call the worst mass murderer in history a dictator or you'll be erased, blacklisted, harassed and attacked. China is an insecure Child of a country
