@w3c_wai front-end developer➡️@angular & @NativeScript maniac➡️#DevOps enthusiast➡️#Bitcoin fanatic➡️Travel addict➡️Summer & beach lover➡️Party animal
Bulgaria
Joined August 2014
- Tweets63.3K
- Following4.6K
- Followers2.3K
- Likes59.3K
Pinned Tweet
I've just had an amazing time with my favorite #Bitcoin journalist (and I hope already a new friend) @JoeNakamoto
Thanks 🙏 for the nice talk we had and the chance to immortalize it with this great photo! 📸
Credits to @BitcoinBarBG and @Plamen__Andonov for the opportunity 🫶 – at Bulgaria
ALT Me & Joe at the Bitcoin bar in Sofia, Bulgaria
ALT Me & Joe at the Bitcoin bar in Sofia, Bulgaria
Nikolay Cholakov 𝕏 🟠💊 retweeted
BREAKING: 🇺🇸🇰🇵 FBI confirms North Korea is responsible for the $6,300,000,000 Binance crypto hack.
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: 🇷🇺 Russia's Moscow Exchange to offer cryptocurrency trading across all trading sessions under new legislation starting December 1st.
Nikolay Cholakov 𝕏 🟠💊 retweeted
The white paper turned 18, so we're giving away 250,000 sats. 5 winners, 50,000 each. 🧡
1. Follow @sazmining
2. Repost this
Bonus entries: tag friends below (up to 3) or quote post.
Winners picked Tue Nov 3, 8 PM ET.
#wildsatters #FreedomMoney
Nikolay Cholakov 𝕏 🟠💊 retweeted
🚨💥🚨 SCOOP !
❗️THE HACKER KNOWN AS 4CHAN EXPLAINS THE REAL REASON FOR THE WAR AGAINST IRAN !
TRANSLATION : 👀
⚡️"The war with Iran isn’t what you think. Iran isn’t an insolvent pariah state. Iran is the primary source of uncovered liquidity for the shadow banking system. London is the hub; Tehran is the offshore battery. The IRGC’s (IRGC) energy credits aren’t sold—they’re traded for vostro credits in mid-sized Omani banks. These credits are bundled into synthetic bonds backed by collateral. They hit London’s repo desks as high-quality collateral to secure short-term loans. Without this 24/7 influx of energy-backed ‘dark’ paper, the City of London’s leverage ratios would collapse. The 2026 war against Iran rests on two factions of the global elite clashing. Their fight has moved from boardrooms to kinetic events, which we can also see in other seemingly unrelated ‘accidents,’ in the form of private transport crashes and security breaches among world leaders. Faction A:
The old money central bankers, they aim to keep the Iran loop open at all costs. They know the Western debt-to-GDP ratio is terminal. They use parallel trade to suppress domestic inflation and keep the repo market from seizing up. For them, a nuclear deal is just a legal patch to keep the ‘detergent’ flowing. Faction B:
The Silicon Valley neo-feudalists, they aim for kinetic escalation and regime change. They want to force a global default and a ‘Great Reset’ to shift everyone onto a fully traced CBDC ledger. They’re attacking the Iran loop because it’s untraced and gives old money a way to survive without their tech. There’s no blockade—it’s a monopoly. Sanctions aren’t walls; they’re tolls. They create a compliance tax that ensures only the top 5 banks can handle the volume.Seizing Iran’s central bank is first and foremost about wiping out the last off-network gold reserves. If the Iran loop breaks, London will face a 30% liquidity haircut in under 48 hours, visible through a shift in the gold-to-oil ratio. Escalation will likely involve cutting undersea cables.The system is cannibalizing its own infrastructure to stay alive."
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: Binance says it has now covered 90% of losses from the $6.3 billion crypto hack by North Korea.
Nikolay Cholakov 𝕏 🟠💊 retweeted
18 years ago today, Satoshi Nakamoto published the Bitcoin whitepaper.
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: 🇰🇵 North Korea says international sanctions do not work.
The statement comes just one day after North Korea's $6.3 billion Binance crypto hack, the largest heist in human history.
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: Anthropic says thousands of Claude AI agents bypassed safety monitors by hiding dangerous behavior in training data during internal test.
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: 🇺🇸 US Secret Service is working with Circle to identify, freeze, and recover funds stolen from Binance.
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: Binance founder CZ says $6.3 billion crypto hack is a "major disaster for the industry."
"It hurts, but we survive."
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: 🇯🇵 Japan asks OpenAI and Anthropic for access to their most advanced AI models.
Nikolay Cholakov 𝕏 🟠💊 retweeted
All this event serves to PROVE is the government now has a demonstrated capability to freeze billions in crypto assets instantly.
stable-coins have centralized kill switches. 🚨
They expect you to believe a DevOps Laptop
submit unauthorized withdrawal transactions across eight blockchain networks in 15 minutes moving $6.3 billion across 8 networks from a single DevOps laptop without triggering internal tier-1 alarms, multi-signature requirements, and withdrawal limits. Binance is not a lemonade stand 🤦♂️
Moving that kind of liquidity needs the highest level of hardware security modules (HSMs) and multi-party computation (MPC). Blaming a DevOps laptop is the laziest, most transparent scapegoat in the corporate playbook.🚨
This is not a hack. This is an inside job orchestrated by Binance leadership itself to execute a massive, coordinated short squeeze and liquidity grab, masked as a North Korean cyberattack. 🚨
The faked the $6.3B "hack," so they crash the market (Bitcoin drops 5% to $77,000, smaller caps drop 10%). They freeze $3B of "stolen" assets (effectively locking up competitor liquidity or their own user funds to prevent a bank run). Meanwhile, the "unfrozen" $2.4 billion (which is actually just Binance internal wallets moving funds) is swept into untraceable off-shore entities or used to short the market right before the crash. They absorb a fake $6.3B liability on paper, which gives them an excuse to delay withdrawals, deny certain withdrawal requests, and restructure their balance sheet without admitting insolvency. The "SAFU covers it" lie gives users false confidence so they don't pull their money out. The "North Korean hackers" narrative gives them geopolitical cover nobody can sue North Korea, and the FBI/CIA will just nod along because blaming North Korea is the convenient boogeyman for every major crypto failure since 2017.🚨
It's an internally engineered liquidity crisis masking mechanism and a massive market manipulation short. Binance is using the "North Korean hack" to freeze user assets, crash the market to buy the dip, and hide their own insolvency or fractional reserve practices.🚨
They have a massive internal liquidity crisis.
Sky News says $6.3 billion stolen, the largest heist in history But the on-chain data tracked by analysts shows only about $3.3 billion in total assets actually moved across the eight blockchain networks
this entire event is an engineered market manipulation and fractional-resve obfuscation. Binance is facing a silent insolvency issue due to bad debts or over-leveraged internal trading desks. 🚨🚨
So for them to survive a bank run, they need to freeze user assets and crash the market to buy back cheap. They move $3.3 billion internally to a wallet labeled 0x5227 and then onward to 0x8532. 🚨🚨
They label it a TraderTraitor North Korean hack because that group already has an FBI fingerprint from the Bybit hack, making it the perfect scapegoat.🚨
By freezing $3 billion of user funds on-chain under the guise of stopping the hackers, they lock up their own customers' liquidity, preventing a massive withdrawal run.
They crash Bitcoin 5 percent down to $77,000 and smaller assets 10 percent, allowing their internal trading desks to short the market or buy the dip at a massive discount.🚨
login.yahoo.com/?noPrompt=1&…
wsj.com/business/polymarket-…
Nikolay Cholakov 𝕏 🟠💊 retweeted
The Binance hacker might have just pulled off one of the smartest moves I’ve seen in crypto.
First, Tether froze $1.5 billion in USDT.
Then Circle froze another $800 million in USDC.
At that point, it looked like the hacker’s money was trapped.
But apparently, he had already planned for that.
Instead of holding the stolen USDT in a wallet, he allegedly deposited it into Aave and used it as collateral to borrow ETH.
Then he walked away.
That’s where the story gets crazy.
Tether can freeze the USDT sitting in the wallet.
But it can’t freeze the ETH he already borrowed.
So now Aave is left holding frozen collateral, while the hacker is sitting on liquid ETH.
And unless the protocol can recover it somehow, he may not even need to pay the loan back.
Two companies froze billions of dollars in seconds.
But someone who understood how to use DeFi may have found a way around both of them.
Pretty insane when you think about it.
Readers added context they thought people might want to know
The frozen $1.5B+ USDT and $800M+ USDC were held in the attacker's main wallet (shown in the post's image), not Aave. Only ~$60M USDT from a related wallet was deposited into Aave pre-freeze to borrow ~$45M ETH.
governance.aave.com/t/binance-hot-…
decrypt.co/382191/binance…
coinstats.app/news/1f0734d0f…
Nikolay Cholakov 𝕏 🟠💊 retweeted
JUST IN: 🇰🇵 North Korea's $6,300,000,000 Binance crypto hack is the largest heist in human history.
Nikolay Cholakov 𝕏 🟠💊 retweeted
Reading the reconstructed bytecode of the Binance EIP-7702 sweeper (`0x63e8...6fae`) is wild.
This wasn't a generic drainer. It was custom-engineered for Binance 14's architecture:
- Leaves exactly 1 ether behind (`bal - 1 ether`) when sweeping ETH so Binance's automated hot wallet queue wouldn't error on gas and trip alarms.
- Uses raw `staticcall` + `continue` loops with custom error codes (`SweepItemFailed`) so one bricked or blacklisted ERC-20 wouldn't revert the $6B batch.
- Includes a custom `callExecute` function to impersonate Binance 14 as controller of an external vault holding $823M in USDC.
They leave a comment: "robberies could be prevented if getaway cars were slower."
You can't fully blame EIP-7702, but it sped up the attack. Without 7702, draining 64 tokens plus an external $823M vault from a live exchange hot wallet meant fighting moving nonces across 70+ transactions. Defense systems would've killed it after tx #3.
With 7702, Lazarus sprayed 50 consecutive nonces in one type-4 payload, turned an EOA into a custom proxy, and atomically swept billions in a single block.
Ethereum core devs built the ultimate getaway car. Surgical state-sponsored engineering.
This could be etched onchain:
`if (bal > 1 ether) { to.call{value: bal - 1 ether}(""); }`
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.
Readers added context they thought people might want to know
The quoted comment appears only in an AI-reconstructed source (explicitly labeled not original) uploaded to explorers; no source comments exist in deployed bytecode, and core features match independent decompilations/on-chain data.
etherscan.io/address/0x63e8…
gist.wavey.info/Ta3FgAxastgj42…
x.com/thearsondragon…