FOLLOW THE MECHANISM
- 1Ledger data
Public transaction details can expose relationships.
- 2Service data
Custodians and infrastructure providers may know identities or queries.
- 3Correlation
Observers combine timing, amounts and known addresses.
- 4Selective disclosure
Privacy mechanisms limit particular data under stated assumptions.
A conceptual sequence. Real implementations can add steps, intermediaries, and conditions.
Public identifiers can become personal
On transparent blockchains, transaction amounts, addresses and relationships are generally visible. An address may not contain a person’s name, but an exchange, merchant, public post or repeated usage pattern can connect it to an identity. Once that association is known, older public activity can become easier to interpret. Privacy is therefore about what an observer can infer from combined information, not simply whether the ledger has a name field.
A wallet talks to other systems
A wallet may ask an infrastructure provider for balances and submit transactions through that provider. The provider can learn requested addresses and connection metadata. Websites can also observe account connections and other browser information. Running independent infrastructure changes some dependencies, but does not automatically hide onchain flows. Network privacy and transaction privacy are different layers, and neither should be assumed from the presence of a secret signing key.
Cryptography can limit disclosure
Some systems use commitments and zero-knowledge proofs to verify authorized transfers without revealing every detail publicly. Shielded and transparent transaction forms can coexist, as illustrated by Zcash’s protocol specification. The privacy achieved depends on which form is used and what remains public. A proof system can hide a witness while timing, public inputs, entry and exit behavior or voluntarily shared information still reveal relationships.
Privacy has a specific observer model
A useful analysis asks: private from whom, for which data, and for how long? A counterparty may know a payment amount even when the public cannot. A view key can intentionally disclose records to a selected reviewer. A local website can avoid sending simulation inputs anywhere while an external link still takes the visitor to another service. Specific data flows are more informative than a blanket “anonymous” label.
MAKE IT CONCRETE
One public address changes the picture
Imagine someone publishes an address to receive payments for a public project. That association can help an observer interpret transactions involving the address, even if unrelated addresses remain uncertain. A later transfer may create additional clues. The mathematical security of the signing key has not changed; the amount of identifying context available to observers has.
FAILURE PATHS & COMMON MISREADINGS
Where the model can break
- Encryption of a wallet backup does not make public transactions private.
- Zero-knowledge technology does not automatically hide every public input or network trace.
KEEP EXPLORING