I'm going to use Joel's post here as an opportunity to explain why we're doing what we're doing at BSVA and the BRC process (which was started in large part thanks to @ProjectBabbage) Backwards compatibility is a virtue, until what you’re staying compatible with is the bottleneck. Joel’s point is fair in general. New software usually should respect what came before. But the way Bitcoin wallets have always worked is not how Bitcoin was designed to work. It’s a workaround that stopped working the moment BSV got busy. We’ve already tested it at scale. BSV has mined blocks of nearly 4GB. When application traffic peaked, the network kept producing blocks. What fell over was everything around it: indexers, exchanges, explorers, ElectrumX servers, and services that tried to keep up by scanning the whole chain for every address they cared about. Mining scaled. The application layer didn’t. That’s the core problem with the ElectrumX model. A wallet asks a server, “What happened to my addresses?” To answer, that server has to index everyone’s history. Its cost grows with the whole network, not with its users. At 4GB blocks, that design isn’t old-fashioned. It’s broken. Satoshi’s design was different. Payments go directly between the people involved. The original client even let you pay straight to an IP address. The whitepaper describes Simplified Payment Verification (SPV): you keep block headers and check a Merkle proof for the transactions that matter to you. Nobody has to watch the entire chain on your behalf. That’s what the BRC-100 stack is built on. Transactions travel peer-to-peer with their own proofs attached (BEEF), and wallets verify them against headers. Your wallet’s workload grows with your own activity, not the world’s. Does that make us right about everything? No. People raised real criticisms of MessageBox, and that’s directly why work is now underway (Thank you @deggen !) on WebRTC-based peer-to-peer connections. Keep the criticism coming. Better still, contribute. We want this to be the most scalable, usable stack ever built, and that takes people breaking it. But “it’s not compatible with how we’ve always done things” isn’t a reason to stop. How we’ve always done things is what failed under real load. The miners are ready for terabyte blocks. Wallets and apps have to be designed to keep up now, not after the next wave of traffic takes them down again. I think Joel, Cryptorebel, and others are raising good points that require us all to communicate in good faith. I hope to be a part of facilitating that conversation moving forward!