CryptoNote v 2.0

The problem the paper names

Bitcoin's ledger is a public list of amounts between reusable addresses. Anyone who learns one address can walk the graph. CryptoNote treats that traceability as the defect to design against, not as a feature to be patched with mixers after the fact.

What the design proposes

• One-time destination keys so a payment address is not reused on the ledger.
• Ring signatures so a spend is signed by a set, and the real signer is not revealed.
• Untraceable transactions as a protocol property, rather than an optional mixer.

How the mechanism is specified

• A sender takes their own output and mixes it, inside the signature, with other outputs of the same denomination drawn from the chain.
• The recipient detects the payment with a private view key without the sender learning when it is spent.
• Double-spends are still rejected because each output can be consumed only once, even though the spender is hidden inside the ring.

What this page does not treat as proven

• The paper does not establish the privacy of any later coin. Ring size, decoy selection and implementation bugs decide that.
• It does not hide amounts. Monero's later RingCT work is a different paper.
• The historic file whitepaper_review.pdf is a commentary, not this text.

Why a venture studio still reads it

Useful when a venture claims 'private payments' but still plans to publish amounts and reusable addresses. CryptoNote's bar is specific: unlinkability has to be in the transaction format.