Bitcoin Weekly
No. 035
7 min readBy Karl
The Biggest Exchange Hack Ever, Core 32.1 Arrives, and Bitcoin Slips Below $80K
Binance lost an estimated $6.3 billion in the largest crypto theft on record, Bitcoin Core 32.1 shipped with security fixes, and Bitcoin fell to its lowest level since September.
The Biggest Exchange Hack Ever
On Thursday evening, October 29, attackers drained a Binance hot wallet, an exchange wallet kept online so customer withdrawals can be paid quickly. Binance puts the total loss at about $6.3 billion. CoinDesk calls it the largest crypto theft on record, more than four times the $1.4 billion taken from Bybit in 2025. At one point the attackers' wallets held nearly $1.5 billion in bitcoin, according to Arkham data cited by CoinDesk.
How it happened. Binance says its first findings point to "a compromised laptop belonging to a DevOps engineer," which gave the attackers a way to submit withdrawals the company never approved. Binance says it found no evidence that any wallet private key leaked. Its CEO, Richard Teng, has described further breach points and approval controls that were bypassed. TRM Labs links the attack with high confidence to TraderTraitor, a North Korean hacking group. Binance has not said who was behind it.
What it means for customers. Binance stopped withdrawals across its platform, bitcoin included, while deposits stayed open. It says it plans to restart withdrawals in phases this weekend, once security checks are complete, and to publish an updated proof of reserves early next week. "Binance will absorb the financial impact of these stolen funds, not our users," the company said, and it says it has set aside more than $6.3 billion to cover the loss. About $3 billion of the stolen funds has been frozen, most of it in dollar tokens whose issuers can block them. Bitcoin cannot be frozen that way.
The lesson is old, and it still holds. Binance may well make every customer whole. Even so, for as long as withdrawals are off, people with bitcoin on the exchange cannot move it, sell it elsewhere or take it home. That is what holding coins on an exchange means: you own a promise, and the exchange decides when it is honored. Coins in a wallet where you hold the private keys answer only to you.
If you buy on an exchange, withdraw on a schedule. Pick a threshold or a calendar day and move your bitcoin to self-custody when you reach it. Send a small test amount first. And expect a wave of fake "Binance support" messages this week: no real exchange will ever ask for your recovery phrase or ask you to move funds to a "safe" address.
Upgrade Week
Bitcoin Core 32.1 is out. On October 27, Bitcoin Core published version 32.1. The release notes explain that "due to last-minute issues, 32.0, although tagged, was never fully announced or released," so 32.1 is the first public release of the series we have been following since issue #031. It brings a new fee estimator that also looks at what is waiting in the mempool, faster block validation, watch-only wallet exports and three security fixes. One of the fixes stops a remote peer from crashing nodes on Windows, macOS and BSD by exhausting their memory. The same fixes shipped in versions 31.2, 30.4 and 29.5 for node runners on older series. With this release, versions 29.x and older are at end of life.
A new rule for bugs AI can find. On October 22, Bitcoin Core developer Antoine Poinsot announced a change to how the project handles vulnerabilities. Bugs that are easy to discover, "such as through a simple LLM prompt," will now be fixed in every maintained version as soon as possible, with an advisory published at the same time, instead of waiting quietly for the next major release. "The embargo period achieves little but it delays the availability of a fixed release," he wrote. The three fixes above were the first handled this way. It is the defense side of the trend we wrote about in issue #032: AI is not breaking Bitcoin's math, but it is making ordinary software bugs easier to find.
Electrum: a flaw used to steal bitcoin. On October 24, the Electrum wallet released version 4.8.3 to fix a high-severity flaw that, in the developers' words, "some servers are performing this attack in the wild." Electrum is a light wallet: it relies on public servers to tell it what is happening on the network. A malicious server could quietly drop a payment you sent and show a fake pending transaction in its place, paying the attacker instead, with an address made to end in the same four characters as your real recipient. The fake paid no fee, so it looked stuck. If you then raised the fee to speed it up, a feature called replace-by-fee, you signed the attacker's transaction yourself. Two users reported it, and one lost money. If you use Electrum, update to 4.8.3, downloaded only from electrum.org. Whatever wallet you use, check the address and amount on your hardware wallet's own screen before approving any payment or fee bump. Wallets connected to a server you run yourself were not affected.
Also this week. Eclair 0.14.6 fixed more splicing and fee issues, LND shipped the final versions of 0.21.5 and 0.20.6, and BTCPay Server merged a second set of fixes for API keys that could carry more permissions than the merchant chose. BTCPay notes that keys issued earlier may need to be revoked.
The Fed Holds, and Bitcoin Slips
The Federal Reserve held its benchmark rate at 3.75% to 4% on Wednesday, October 28. The vote was 10 to 2: Governor Lisa Cook and Cleveland Fed President Beth Hammack both wanted another quarter-point increase. The Fed said "an accumulation of more information" will guide its next move, and markets now price a December hike as likely, at about 83% on CME FedWatch after the meeting.
Bitcoin had spent much of October holding near $80,000. It slipped below that level early in the week, then fell harder after the Binance news, touching $76,301 late Thursday, its lowest price since September 18. About $1.5 billion of leveraged bets were wiped out in a day, mostly bets on higher prices, according to CoinGlass. On Friday morning Bitcoin traded near $77,300, down about 5% from a week earlier. Spot Bitcoin ETFs still took in about $303 million from October 23 to 29, all of it reported before the hack.
Miners kept adding machines through it all. Mining difficulty rose about 5.5% on October 29, to roughly 148.4 trillion, after a 5.9% increase two weeks earlier. That is two large increases in a row while the price fell, which squeezes what miners earn for each unit of computing power.
The Numbers
See them live in Bitcoin Pulse
| BTC Price | ~$77,300 (Fri Oct 30, morning) |
| On the Week | down ~5% |
| From All-Time High | ~39% (peak $126,198) |
| Binance Hack | ~$6.3B (Oct 29; Binance estimate) |
| Week's Low | $76,301 (Thu Oct 29, lowest since Sept 18) |
| Liquidations | ~$1.5B in 24 hours (CoinGlass) |
| Fed Funds Rate | 3.75% to 4% (held Oct 28; 10 to 2 vote) |
| December Hike Odds | ~83% (CME FedWatch, Oct 28) |
| Spot ETF Flows | ~+$303M (Oct 23 to 29) |
| Mining Difficulty | +5.5% to ~148.4T (Oct 29) |
| Bitcoin Core | 32.1 released Oct 27 (32.0 never released) |
| Electrum | 4.8.3 (Oct 24), fixes an exploited flaw |
What to watch next week
- Binance withdrawals. A phased restart is planned for this weekend. Watch whether bitcoin withdrawals come back first, and for the proof of reserves Binance promised early next week.
- Fake support messages. Hacks bring phishing waves. Nobody legitimate will ask for your recovery phrase.
- Bitcoin Core advisories. Under the new policy, more fixes may arrive as point releases with advisories. If you run a node, keep it current.
- Next difficulty adjustment. Early estimates point to a small decrease after two large increases in a row.
- The next Fed decision. Markets now expect a hike in December.
From 21VOX
Live dashboardBitcoin PulseTrack price, sentiment, ETF flows, and network health in one place. No account required.This week's tool
Bitcoin Transaction TrackerThis week's Electrum attack worked because the wallet trusted one server about what had happened to a payment. If a transaction ever looks stuck, check it against an independent source before you touch the fee. Paste the transaction ID into the Bitcoin Transaction Tracker to see whether the network actually has it and where it sits in line. The lookup goes from your browser straight to mempool.space, and the transaction ID is never sent to us.
Bitcoin LegacyIn development
Bitcoin Legacy
This week a single exchange stopped withdrawals for every one of its customers within hours. If part of your bitcoin sits with a company, your family's plan has to say which company, what the account is, and what to do when that company is slow, frozen or gone.
Legacy is the tool we are building for that. Answer a few multiple-choice questions about the wallets, companies and exchanges you use, and it builds a printable kit of five documents, with steps for each company's inheritance process and for what to do if the company is gone. For the Executor lists what you held and which companies are involved, with no secrets. The kit also includes step-by-step instructions for each wallet, a First 48 Hours guide for someone who has never touched Bitcoin, a security checklist, and a page to give your family now. It never asks where anything is kept, or who you are. Names, places and secrets go on by pen after you print.
It runs entirely in your browser. Nothing is stored or sent, and there is no account. Legacy is still in development, and everyone on the waitlist gets founding-member pricing. Prefer paper? A free sample of the paper workbook is on the Legacy page, no email needed.
Join the waitlistBitcoin Weekly is published every week by 21VOX. Written by Karl. No financial advice. Just signal.