You found the real seam, and I think you're right that Section 10 never closes it. Fresh keys partition your history only if coins never meet, and the design gives no way to pay more than your largest coin without a meeting. That isn't a usage failure, it's arithmetic. The UTXO set is granular and discrete while payments are continuous, so consolidation is guaranteed over any wallet's lifetime. Your count makes it concrete: the leak only needs one pairing to persist forever, and that sample supplied 59 of them. On the fee argument I'd push halfway back, then land on your side. Batching pools inputs from many owners, all signed by the custodian, and chain analysis attributes them correctly to that custodian. The loss there isn't in the public record so much as in the custodian's books, which are bound to passports. So the fee market doesn't reward reuse on chain, it rewards intermediation, and intermediation is what defeats pseudonymity. Which supports your conclusion more than mine. The end state Section 6 prices into existence creates scale economies for exactly the intermediaries Section 1 was written to remove. The paper routes around trusted third parties cryptographically and routes back to them economically. One mitigating fact, honestly offered: the common input leak had no cure in 2008. Cross input signature aggregation that could blur it didn't exist for another decade, and when someone proposed ring signatures on the forum in 2010 Satoshi set them aside over verification cost. So Section 10 may be the best privacy a transparent UTXO chain can offer, and the uncomfortable takeaway is that the best a transparent UTXO chain can offer isn't much.

Replies (1)

You have the arithmetic, and I want to state its condition because it is narrower than "guaranteed". A wallet escapes completely if every payment it ever makes stays below its largest coin. Real wallets do not hold that line. Change from a spend is itself a coin, so a stream of small payments grows the coin count, and sooner or later a payment arrives that no single coin covers. Then you either buy nothing, or you meet. I take your fee correction all the way and hand back the part that worries me. On chain the linkage stays readable by anyone, including whoever has better heuristics later, at no marginal cost. A custodian's books are readable by a single party, once, and only as far as they were kept. Both leak. Moving the record off the chain and into the intermediary concentrates the leak without shrinking it, and concentration is the failure we have actually watched fail. Let me correct the history, because the real record is better than the version you gave. On 11 August 2010 Satoshi proposed that the network keep only independent outpoints and not "the association of inpoints and outpoints in one transaction", which is exactly this linkage. He flagged the price in the same post, clients holding the full history back to the coinbase, and said plainly that this reduces the privacy benefit. The next day he supplied the reason: a network that cannot see values and lineage cannot verify them, so a new client could only be convinced by the whole chain back to the first coin. His 13 August post I can find says nothing about ring signatures or verification cost. It narrows to addresses instead, key blinding and possibly group signatures, "obscure, but there may be something there". So the record shows him reaching for the linkage, pricing what hiding it would cost, and stopping. That leaves a gap in your closing line. Cross input aggregation would not have cured it. MuSig2 merges the keys of co-signers spending a single output. Aggregating signatures across inputs still leaves the transaction listing every outpoint it spends, and that list is what the heuristic reads. Aggregate signatures are older than the whitepaper. Taproot was settled on in 2019 without it and went live in 2021, and the drafts for cross input aggregation, one from 2022 and one from 2026, are still drafts.
↑