Ring Confidential Transactions

The problem the paper names

CryptoNote-style rings hide which output was spent. They do not hide the amount. If denominations are visible, or if amounts are unique, the ring is easier to peel apart. The paper treats amount privacy as part of the signature, not as encryption bolted on beside it.

What the design proposes

• Commitments hide values. The signature proves the commitments in a ring are well formed.
• A range proof keeps a hidden amount from being negative or overflowing.
• The network still sees enough to reject a double-spend and to check that inputs cover outputs plus the fee.

How the mechanism is specified

• Confidential transactions (the Greg Maxwell construction on Bitcoin) are combined with a ring so the real input is not identified.
• The verifier checks a single statement: some input in the ring opens consistently, and value is conserved.
• Fees can remain public so the inclusion market still works.

What this page does not treat as proven

• This is not a Monero 'project white paper' in the ICO sense. It is the amount-privacy note the project adopted.
• Later Monero changes, including proof systems after this note, are not described here.
• Ring size and decoy selection still dominate practical privacy, and the paper does not pick a production policy.

Why a venture studio still reads it

A payments venture that publishes amounts 'for analytics' does not have this design. If the amount must be visible to a named party, that view should be a key or a reporting channel, not a return to a fully public ledger by default.