The Binance Hack, and Why Creations Never Holds Your BSV

Six billion dollars left one company's wallets in twenty minutes. Here is the design that leaves us nothing to steal.

What happened at Binance

On the evening of 29 October 2026, somebody with the ability to make Binance's hot wallets sign transactions used it. Across ten blockchains, about six billion dollars' worth of coins left the exchange's wallets, most of it in roughly twenty minutes. It is the largest theft in the history of the industry, several times the previous record.

How the attacker got that ability is still being investigated. Binance first pointed to a compromised engineer's laptop, then said there were further points of breach and that the attackers had erased their tracks. Analytics firms attributed it to a North Korean state group within a day, and by the weekend the FBI had said the same. For the purpose of this article, it does not matter who did it. What matters is what was possible.

Two further facts. Roughly half of the stolen value was frozen within hours, almost all of it stablecoins, because the companies that issue those tokens can freeze any address they choose. And Binance has set aside its own money to make every customer whole, and says it has already replaced most of what was lost. As far as anyone can tell, no Binance user has lost a coin, though withdrawals were still paused as this was written.

Hold on to those two facts. They are doing more work than they appear to.

The chains did what they were told

Not one of the ten blockchains failed. Each received validly signed transactions and executed them, which is exactly what a blockchain is for. What failed was a company: one signing system, run by one organisation, able to move six billion dollars across ten networks with nothing in any protocol to stop it. Call it a "crypto hack" if you like. It was a company hack. A blockchain is only as trustworthy as whoever holds the keys, and the keys were held by Binance. The attacker did not even need to steal them. It was enough to make the system that held them sign.

Exchanges are honeypots

A honeypot, in the old sense, is a jar of something sweet left where the bears can smell it. In security the word means the same thing: a single place where so much value is concentrated that attackers are drawn to it no matter how well it is guarded, because the prize justifies any effort. A custodial exchange is the purest example there is. The coins of tens of millions of people, pooled behind one company's signing system, under one security team. There is no richer target on earth. Of course it was attacked. Of course it will be attacked again. The surprise is not that it happened but that anyone is surprised.

The counter-argument writes itself: my own wallet is not more secure than Binance's. Correct, and beside the point. Security is not an absolute; it is a return on the thief's investment. This attacker spent days preparing and, if the analysts are right, the resources of a state, to take six billion dollars in twenty minutes. Nobody mounts that operation against you and your few coins. You do not need to out-secure Binance. You need to be not worth the trouble, and in a wallet you control, you already are.

We rebuilt the bank

Bitcoin's whitepaper opens by naming the problem it solves: commerce on the internet relies on financial institutions as trusted third parties. The design removes them. You hold the key; the network checks the signature; nobody stands in between who can lose, lend or freeze your money.

Then we handed the keys back. A custodial exchange is a bank in everything but the name. You deposit; the exchange owns the coins; what you own is a line in its database saying it owes them to you. It pools everyone's deposits, moves them for its own convenience, and gives you back what you ask for as long as it can. That is a bank's balance sheet, and it carries a bank's failure mode: the moment the firm's assets fall short of what it owes, every customer is, in practice, an unsecured creditor queuing at a locked door. Mt. Gox's creditors queued for a decade.

Societies learned this about banks the hard way and built around it: deposit guarantee schemes, a central bank that lends to a solvent bank facing a run, capital rules, orderly wind-downs. None of that exists for an exchange. Binance keeps an emergency fund, but it is Binance's fund, Binance's size, spent at Binance's discretion. There is no lender of last resort and no guarantee scheme. If the company cannot pay, nobody pays.

This week the company could pay, and did. That is what a well-capitalised bank does after a robbery, and credit to it. But notice what it means: the only thing standing between users and loss was one company's balance sheet and one company's willingness to use it. On Thursday evening, Binance's customers did not hold coins. They held a promise, and the promise happened to be good.

And notice the other fact: what got frozen was the part of the pile that an issuer can freeze. The Bitcoin, the Ether and the other native coins, the assets there that behave like money you actually own, cannot be frozen by anyone; getting them back means catching someone. The industry celebrated the IOU with a kill-switch and shrugged at the bearer money. Whatever you think of freezing, know which of the two you hold.

Why we built Creations not to hold any of your BSV

The honeypot exists because the exchange is how coins get in and out. People buy there, park there, sell there. Take away the need for the ramp and you take away the pool. And the way to not need the ramp is for the coin to circulate as money: earned for work, spent on goods, never deposited anywhere.

That is the choice we made when we built Creations on BSVSearch, and this hack is the clearest illustration of why.

Creations is a place where writers sell their writing for BSV. BSVSearch never holds anybody's money. There is no wallet on the site and no balance on any account. When a reader buys an article, the reader's own wallet pays the writer's own address, directly, and the platform's fee goes to BSVSearch in a separate payment. The site watches the blockchain, sees the payment, and opens access. It never touches a key and it is not a payment processor. There is nothing pooled, so there is nothing to drain. What we can be attacked for is the address shown on the page, not the money behind it, and that is a risk we carry, not you. A thief who wanted to rob Creations' writers would have to rob them one at a time, which brings us back to return on investment: not worth it.

This design has costs. We thought them through before building, and you should know them before buying.

The first is the hassle. A reader pays two parties instead of one. A single transaction paying both at once would do the same job, and may come as wallets allow it. What we would not do is take one payment and forward your share — in that moment we would have been holding your money, and we would have had a hot wallet, and we would have been a very small Binance. Two payments is the price of there being nothing to steal.

The second is harder. Because we never hold the coins, we cannot move them back. A reader who sends the wrong amount to the writer's address has paid the writer, and the only remedy is the writer choosing to return it. A reader who sends to a wrong address altogether has paid a stranger, and the only remedy is to pay again, correctly. There is no refund button and no support desk that can reverse anything, because there is nobody in the middle with the power to do so. The convenience that custodians sell is exactly the power that made Binance robbable. You cannot have one without the other, and we chose the other.

The third is on the writer. Getting paid to your own address means your own key is your responsibility, and an address you publish for years accumulates a visible balance. Move your earnings off the published address from time to time. It is a small target, but it should not be a growing one.

What the reader gets in return is a transaction they can check on any block explorer, a price in satoshis that is paid once and never renews by itself, and the knowledge that no one between them and the writer can be hacked for their money. What the writer gets is payment at the moment of sale, with no payout schedule, no threshold and no withdrawal, because nothing was ever held.

The point

Bitcoin was designed so that value sits in millions of small places, each not worth attacking, moving directly from one person to another. We rebuilt the bank, called it an exchange, and got the bank's failure mode back with none of a bank's state-backed insurance. Binance's customers were lucky in their creditor.

The alternative is not a safer bank. It is no bank. It is slightly less convenient, it puts the key in your hands, and it means a mistake is a mistake. It is also the only design in which there is no pile to steal. That is what peer-to-peer electronic cash meant in the first place. Binance just spent six billion dollars reminding us.

Marquez

Creations · How it works · Selling Terms

Sources for the Binance account

• TRM Labs, "North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in History," 30 Oct 2026. trmlabs.com
• Chainalysis, "The $6.4 Billion Binance Hack: Tracing the North Korea Link," 30 Oct 2026. chainalysis.com
• Binance, "Security Incident Update #2," X, 30 Oct 2026. x.com
• Binance, "Security Incident | Update #3: 90% of Stolen Assets Replenished," X, 31 Oct 2026. x.com
• Richard Teng, video statement transcript, X, 30 Oct 2026. x.com
• Changpeng Zhao, X, 29 Oct 2026. x.com
• Paolo Ardoino (Tether), X, 29 Oct 2026. x.com
• Bloomberg, "FBI Blames North Korea for $6 Billion Binance Crypto Hack," 31 Oct 2026. bloomberg.com
• PBS NewsHour / AP, "What to Know about the $6.3B Hack on Binance," 31 Oct 2026. pbs.org