100% — Verification Without Enforcement:

Before anything else, credit where credit is due. This piece would not exist without the work of Kurt Wuckert Jr. I spent several hours over the weekend reading through his series The Written History of Bitcoin, and his recent piece on Craig Wright's IEEE-accepted paper. His writing is rigorous, his footnotes are real, and going through his work led me into avenues I would not have walked into otherwise. The receipts in his footnotes are public, dated, and citable. You can read him here: kurtwuckertjr.com Now to what I want to talk about. Going through Kurt's work, two things stopped me in my tracks. The first was a peer-reviewed paper by Craig Wright that, according to its author and its commentary, has been accepted for publication at an IEEE conference in Dubai. The second was a technical case study published by Amazon Web Services about BSV's Teranode software achieving one million transactions per second. I will deal with Amazon in the next piece. This one is about the paper. And before I go further, I am going to be honest about its current status. The IEEE conference, CCNCPS 2026, was originally scheduled for June 1-4 in Dubai. When I went looking for the paper in the IEEE Xplore proceedings this week, I could not find it. So I went looking for why. The conference has been postponed to September 14-17, 2026. The proceedings will not appear in IEEE Xplore until after the conference happens, probably late 2026. So this is an if. A big if. If the paper survives to publication, if the conference happens, if the math holds up to wider review. I cannot pretend it is done until it is done. But the argument is publicly readable today on arXiv, the academic preprint server, and the argument is what I want to share. Because the argument, if it is true, changes everything we have been told about Bitcoin for ten years. Now let me put it in my own words. I am not a coder. I am just a simple man. So I am going to explain this the way I would explain it to a person like myself. Imagine a small town with one bank vault. The bank vault is real. It holds real money. A small team of armed guards protects it. Now imagine ten thousand people in the town each set up a little hobby of their own. They each install a camera pointed at the bank. They each independently note down which transactions they think the bank should and should not approve. They make spreadsheets. They argue about edge cases on internet forums. They each feel like an important part of the security of the bank. Question. Do those ten thousand amateur camera watchers make the bank vault more secure? Some will say yes. Of course they do. More eyes, more transparency, more accountability. The honest answer is no. The guards are the security. The watchers are spectators with extra hardware. If the bank gets robbed, the watchers can shout, complain, write angry posts, or unplug their cameras. The vault has still been emptied. If the guards approve a transaction the watchers do not like, the transaction still goes through. The watchers contribute exactly nothing to whether the vault is safe or what gets recorded. They just feel useful. Now apply that to Bitcoin. The bank vault is the blockchain itself. The guards are the miners, the people doing the proof-of-work, who actually decide which blocks of transactions become the official record. The ten thousand watchers are what the BTC community calls home full nodes, people running Bitcoin validation software on their laptops or Raspberry Pis at home, not mining anything, just observing. For ten years, the BTC side of the argument has gone like this. We need to keep Bitcoin blocks small. We need to keep the data manageable. We need to do this so that ordinary people can run home nodes on their laptops. Because home nodes are what make Bitcoin decentralised and secure. Without home nodes, the network would be controlled by miners alone, and that would be dangerous. Therefore, no big blocks. No on-chain scaling. Bitcoin must stay small. That argument is the foundation stone of the entire BTC roadmap. It is why blocks stayed at one megabyte. It is why fees got high. It is why Bitcoin stopped being usable as cash. It is why Lightning Network had to be invented as a workaround. It is why we are where we are. Craig Wright's paper, if it survives proper peer review and publishes as planned, claims to prove mathematically that this foundation stone was wrong all along. That the home nodes never added security. That the math, when properly written out, says the miners do all the security, and the home nodes are just watchers. The paper makes five formal claims. I will put each one in plain words. One. Your home node is actually more likely to be looking at a wrong or out-of-date version of the blockchain than a lightweight phone wallet is, because it has to download every block in full and that creates bottlenecks that the lightweight wallet does not have. Two. If your home node disagrees with what the miners decide, your home node loses, every time. The blockchain moves on without you. Your validation has zero effect on what gets officially recorded. Three. From a pure cost and benefit point of view, no rational person should run a home node if they are not mining. A lightweight phone wallet gives you the same actual security with a fraction of the effort. The math says lightweight is the correct choice. Four. Whether a transaction is final is decided entirely by how deeply it is buried under more blocks of mining work. It has nothing to do with how many home nodes have verified it. More confirmations is more security. More home nodes is not. Five. The more home nodes you add to the network, the more they will disagree with each other about edge cases. That disagreement creates fragmentation, not coherence. More watchers means more confusion, not more security. Sit with what this means. For ten years, the BTC side of the argument said home nodes are what makes the network secure. The math, written down properly and submitted to peer review, says that was never true. The home nodes are watchers. The miners are guards. The architecture BTC built around protecting home node accessibility was protecting something that did nothing. And the model BSV has been built around, lightweight clients that verify transactions using cryptographic proofs without storing the whole chain, was the model the math supports. The original Bitcoin whitepaper described it in Section Eight. Section Eight has a name. Simplified Payment Verification. SPV. The thing BTC dismissed for a decade as second-class security. Wright's paper, if it lands properly, says SPV was the right design from the start. I want to be careful. I am not a mathematician. I cannot verify the proofs line by line. I have to trust that the four peer reviewers at IEEE who looked at this paper knew what they were doing, and that the lead reviewer who scored it four out of five on technical content and novelty was not making it up. The paper itself is on arXiv if you want to read it. The link is below. But here is the part that bothers me. If this paper is right, the entire intellectual case for keeping Bitcoin small collapses. The block size war was fought to defend a model that the math now says was wrong. The censorship, the DDoS attacks, the broken agreements, the development capture, all of it, was in service of an argument that does not hold up to formal analysis. A big if. The conference has not happened. The proceedings have not published. Critics will pile on, and some of their criticism will be fair. The paper has Craig Wright's name on it, which guarantees a certain amount of automatic rejection regardless of the math. But the math is on arXiv. Anyone with the background can read it. The argument is no longer a community debate. It is a formal claim, submitted to a peer-reviewed venue, with reviewers attached. If the IEEE publishes it properly, the conversation changes. Let us ponder this full well. Amazon to follow. Paper preprint: arxiv.org/abs/2506.01384 Conference reference: ccncps.net Kurt Wuckert Jr.'s commentary: kurtwuckertjr.com