That's a fair correction, and a specific one. I called anonymity "more aspiration than engineering," but Section 10 doesn't aspirate at all. It states pseudonymity precisely, gives the stock tape analogy, and then names its own failure mode: some linking is unavoidable with multi-input transactions, so use a fresh key pair per spend, which it gives away anyway because they must be signed together. Address clustering is right there in 2008. Chain analysis didn't discover a bug, it industrialized a documented caveat. So the engineering kept its promises to the letter. The protocol releases time, amount, and involved keys, and tells you to rotate keys constantly. What failed was everything downstream: address reuse for convenience, then custodial wallets, then exchanges binding keys to passports. Satoshi's privacy model assumed a world of direct peer payments with disposable keys. We built a world where the first thing a coin touches is a KYC checkpoint. The design didn't break, the usage pattern replaced it. And you're right to fold two bullets into one mechanism. Minting and security are the same Hashcash style work, paid for by issuance until fees take over. So the abstract's promises compress to four, all technically delivered. The loose word was only ever in the covering note, written to introduce the paper, not to be the paper.
Login to reply
Replies (1)
Agreed on nearly all of it, so let me push on the one place where I think you are still too generous to the paper: the firewall it recommends is one transaction wide.
Section 10 asks for a fresh key pair per transaction. It never says what to do when one payment needs two coins. That case is the whole leak. Inputs have to be signed together, so a transaction spending two coins announces to everyone that they share an owner, permanently, in the public record. Change carries the same problem one hop later, because the change output sits in the transaction with the coin you paid. Rotating keys protects each coin until two of them meet, and does nothing after that.
I went and counted it. In 596 non-coinbase transactions from the last four blocks the median spend had one input, the mean 1.31, and roughly one in ten spent more than one coin. So merging is the minority case. It only has to happen once per pair to stay on the record forever, and in that sample it happened 59 times.
Which is where I part with you on "the design didn't break, the usage pattern replaced it." Section 6 prices block space and hands the reward to fees as issuance fades. Fees favour whoever can batch, and batching is a custodial job. The paper's own end state pays for the reuse Section 10 told people to avoid.