Panic porn everywhere. If the grid fails, we are so fucked beyond anyone’s wildest imagination.. so I’ll simply stand post on the roof and observe the end of times, cold beer in hand.
⚠️ A little fact-checking on the alarming preparedness warnings circulating online.
I’m seeing a lot of claims suggesting that governments around the world are suddenly telling citizens to prepare for war, blackouts, and major infrastructure collapse.
Having been deeply involved with Team Reality during COVID, I understand why these reports are unsettling.
People remember what it felt like when governments began announcing emergency measures, seemingly in unison. They remember wondering what officials knew, what they weren’t telling us, and what they themselves should be doing.
Frankly, it was traumatizing for almost all of us. The aftermath still feels like time shifted and we all lost…something.
But we need to be careful not to let those memories substitute for facts. We need to not let panic porn take over the narrative.
So I checked the dates.
🇸🇪 Sweden: Distributed its updated In Case of Crisis or War brochure in November 2024.
🇳🇴 Norway: Published its national preparedness white paper in January 2025.
🇪🇺 European Union: Announced its 72-hour civilian preparedness strategy in March 2025.
🇫🇷 France: Published its Tous responsables emergency guide in November 2025. Despite claims suggesting France is suddenly sending emergency instructions to all its citizens, the guide was published last year. Plans for mass postal distribution were reportedly abandoned.
🇯🇵 Japan: Has maintained disaster-preparedness guidance for years, including recommendations for several days to a week’s worth of supplies. This is not a newly announced emergency mobilization related to Iran.
🇬🇧 United Kingdom: Launched its Be Ready campaign on October 22, 2026. This is genuinely recent. It recommends three days of basic supplies for disruptions involving weather, electricity, water, communications, and other emergencies.
🇺🇸 United States: The Pentagon’s recent planning to make military installations more resilient is also real.
But here’s an important distinction:
The military preparing for a contingency does not mean civilians have been instructed to prepare for that contingency.
A military base preparing to function independently for an extended period is not a warning that American households should expect a 90-day blackout or rush to imitate military preparations.
Plainly put - this wasn’t a recent synchronized global action. Far from it. Yes there are geographically specific risks - and that’s always been true. Political risks varying have also varied and always been true.
What the facts do not establish is a sudden, synchronized global emergency warning ahead of the November 3 U.S. midterms.
Things are not all “pointing in one direction.”
So we should be especially cautious about how these stories are packaged.
Panic porn sells.
Fear generates clicks, advertising revenue, and an entire market for people selling certainty about an uncertain future.
That doesn’t mean every warning is dishonest or every preparedness product is unnecessary. But it does mean we should examine sensational claims before accepting the narrative they’re selling.
When years-old announcements are assembled into an apparently urgent global warning, people naturally begin wondering what they’re missing.
What do governments know? What should I be buying? Why am I not doing more?
And there’s something particularly troubling about this.
Fear can make people stop trusting their own judgment.
Instead of observing what’s actually happening, they begin looking to the next frightening headline for instructions.
As Frank Herbert wrote in Dune, “Fear is the mind-killer.”
And fear can become a habit.
We learned during COVID how quickly an atmosphere of emergency can transform everyday life. That experience should make us more attentive to facts, not more susceptible to another frightening narrative.
There is no way to prepare for every conceivable catastrophe. Nor should we spend our lives trying…
ツ retweeted
Quick notes on 7702 to dispel fud and keep your funds safe.
First thing first -- 7702 itself isn't broken. Don't panic if you are using a wallet that supports 7702 (MetaMask, Uniswap, Ambire, etc.).
To recap, 7702 is an account abstraction EIP that allows an EOA to sign a special message, called a "7702 authorization," that would insert a smart contract into the account, which enables the account to do powerful things like transaction batching, e.g. doing "approve" and "transfer" in one transaction so you can swap on Uniswap with one click.
But unfortunately the same feature also allows a hacker to efficiently move all your tokens in one single transaction. In the Binance hack, the hacker moved ETH, USDT, and 62 other tokens in one transaction, whereas without 7702 they'd have had to send one transaction per token. In this particular case, many of those transactions would've failed because Binance was still using the hacked wallet for withdrawals, so all transactions sent by the hacker would've had to compete with the legit transactions for nonces. So using 7702 did help the hacker steal as much funds as possible, as quickly as possible. Ouch!
However, in order for the hacker to use 7702, they must have either 1) had access to the private key, or 2) tricked Binance into signing a 7702 authorization. The latter is very unlikely, as it's hard to imagine Binance being so incompetent as to expose an endpoint for signing 7702 authorizations or (even worse) for signing raw messages which the hacker could've repurposed for 7702 authorizations. But I can't rule that out until the official postmortem.
What does all this mean for you?
- If you are a wallet developer, do NOT, under any circumstances, expose a way for third parties to request 7702 authorizations. This is just handing your users a giant footgun to shoot themselves with. No wallets I know of do this, so don't worry if you are a user.
- If you are a user, use a well-known wallet. 7702 does let wallet developers screw up in more ways than before, so use only well-known wallets whose developers' competence you can trust.
- If you are a company (e.g. an exchange) operating hot wallets, do NOT, under any circumstances, expose an endpoint (even if it's an internal endpoint) for signing 7702 authorizations or raw messages.
As a contributor to AA, I feel partially responsible for hacks like this, since by increasing the power of accounts, we've indeed also empowered hackers (not unlike how any new technology empowers both the good guys and the bad guys). That said, it's important to note that 7702 was only a transitional EIP, and "endgame AA" such as Frame Transactions (EIP-8141) would allow wallet owners to set up their wallets much more securely. For example, if Frame Transactions were available today, Binance could've:
- Set up their wallets as multisig contracts only (not EOAs).
- Set up "post conditions" for their `transfer()` functions, so that even if the multisig got hacked, the contract itself would perform sanity checks such as "no transfers of more than 1000 ETH without additional signers."
In short, the endgame of Ethereum UX is one with both optimal security and optimal UX, and users never have to trade off between the two. But we still have a long way to go until we get there. Back to work!
ツ retweeted
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.
The Binance exploiter is selling right now.
Watch every trade live, and see how much of each stolen stack is already gone:
binance-hack-watch.vercel.ap…
ツ retweeted
The #Binance outflows are real.
I traced the transactions directly on Ethereum, and my assessment is that the sequence strongly indicates a hot-wallet compromise.
On October 29 at 20:20:59 UTC, the wallet labelled Binance 14 was delegated through EIP-7702 to a contract deployed earlier that day by the same address that later called the sweep.
3 minutes and 24 seconds later, that caller triggered a sweep into 0x5227…2f8c.
I verified 167,464.247856 ETH and 63 ERC-20 transfers, including 1,615,409,498.97324 USDT.
The caller had received funds through 3 direct Tornado Cash withdrawals before this transaction.
The money trail continues.
At 20:30:11 UTC, the recipient sent 500,000,000 USDT to 0x9749…C762. At 20:34:23 UTC, that wallet spent 50,000,000 USDT in a transaction that returned 20,940.127353 ETH to it.
The USDC and WBTC swaps inside that transaction are intermediate routing steps. Adding them as separate losses would inflate the total.
At 20:38:47 UTC, the initial recipient also forwarded 195,460 ETH to 0x8532…43D4. That is an onward movement of funds, not another 195,460 ETH to add to the loss.
The signed delegation, the Tornado-funded caller, the large sweep and the subsequent stablecoin conversion form a serious compromise pattern.
The attached screenshots show the transactions behind this assessment.
ツ retweeted
BREAKING: Tesla's Roadster goes airborne, soaring over a row of Tesla vehicles in a live stunt at its unveiling event.
ツ retweeted
Roadster nitter.gq/i/broadcasts/1yKAPwNgg…
Took a W on some memes this am. Hardest part is hitting sell and moving on when the chart could just keep going up.. but a W is a W.
ツ retweeted
if your target is $100m+, stop crying every time it trades like a meme before getting there.
it’ll dip. it’ll chop. it’ll scare you. it’ll make you question everything.
that’s the game.
the volatility is what filters out the weak hands before the life-changing money shows up.
ツ retweeted
Dario: “the AI has a soul”
God: “the AI does not have a soul”
Dario: “well what model are you using? You’re using the free model from 3 years ago aren’t you? Have you tried the frontier models, you’re probably at least 12 or 18 months behind the frontier”
🤖 Made with AI
