Verification without full disclosure
Monero is a Layer 1 network whose native asset is XMR. It uses proof of work and is designed to keep payment information private by default. That makes it useful for understanding a distinction often missed in blockchain discussions: a network can verify transactions without publicly exposing every payment detail.
Different protections, different purposes
A recipient can publish an address while payments create one-time destinations on the ledger. Confidential-amount mechanisms let the network check monetary consistency without publishing a readable amount for everyone. These are different protections: hiding an amount is not the same problem as reducing links between payments.
Who has access to the information?
A public explorer and the recipient’s wallet therefore do not have the same view. View keys can reveal incoming transactions without granting spending authority. This selective visibility is still sensitive information, and a view-only record should not automatically be treated as a complete accounting statement of incoming and outgoing funds.
Where privacy stops
Privacy is not an absolute guarantee of anonymity. An invoice, information shared with a counterparty, a compromised device or metadata outside the ledger may identify a person. Keep the question precise: who can see which information, through which channel? Studying those boundaries is more useful than labelling every blockchain either fully public or fully anonymous.
- 01Public observer
- 02Recipient’s view
- 03Invoice or account
- 04Different information
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
Draw three observers: a stranger using an explorer, the payment recipient and a shop holding an invoice. Their evidence differs. One-time destinations and confidential amounts limit what the public ledger reveals. A recipient can recognise incoming funds, while the invoice can link a customer to a purchase without relying on public transaction details. Privacy is a relationship between information and an observer.
Put the mechanism into context
A fictional shop receives a private payment and keeps a named invoice. A public observer cannot read the amount directly from the transaction. A colleague concludes that the shop cannot know the customer either.
Apply it in the workshop →What this mechanism does not guarantee
A view key is not a spending key, but revealing it still exposes information. Never enter a real key in an exercise. This conceptual comparison does not promise anonymity or describe all network-level metadata.