Skip to content
~/sultan
Chapter 2 crest
Chapter 2 · § 2.2 · Recipe

Privacy as a Property of the Stack

Default-private at the protocol layer. Selective disclosure under holder control.

By · Originally published April 2026 · Next review October 2026 · ~5 min

Problem

What does it mean for a digital monetary system to be private? Privacy is one of the most overloaded words in the digital-money debate; what does it have to mean for the design to be coherent?

Solution

Default-private at protocol layer, scoped disclosure under holder control.

Privacy means default-private at the protocol layer, with selective disclosure under holder control or lawful warrant, and with the disclosure surface sized to the verification need rather than to the cryptographic limit of a prior era.

In StableZK, transactions are shielded by default using a zero-knowledge proof system. Account holders can issue scoped view keys to third parties. Compliance attestations prove specific properties without disclosing the underlying state. There is no master key.

Discussion

Privacy is not the absence of records. Privacy is the holder's control of disclosure. Cash exemplifies the property: holders cannot generate counterparty records on demand, but the records that exist are accessible under warrant. Banking exemplifies the corollary: holders generate counterparty records for their bank but the bank operates a controlled-disclosure regime against the rest of the world.

The pre-cryptographic constraint — that verifying a property required disclosing the underlying state — collapsed with production-ready zero-knowledge proofs. Most of the existing privacy/compliance debate is unaware of the collapse.

△ Warning Anyone who tells you privacy and compliance are at war is selling you something. Usually a surveillance product. Sometimes a privacy product. Always something.

See Also

❦ ❦ ❦