§7. Privacy as Private Money

Jason St George. "§7. Privacy as Private Money" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v1.9. /v/1.9/read/part-ii/7-privacy-as-private-money/

Privacy as Private Money

Cash used to be default private money: anonymous, bearer, final on receipt. In a world of KYC’d banks, programmable payments, and networked surveillance, that role has decayed. At the same time, the repression playbook (negative real rates + capital controls) makes bearer-like savings economically necessary, not ideologically optional.

“Privacy” in this thesis is not romantic opacity; it is the ability to hold and move value without chokepoints, plus the option to disclose on your own terms.

Concretely:

Bearer-like holding:
Keys, not accounts, define control. Custodians may exist, but custody is an optional service, not a mandatory chokepoint.

Non-custodial settlement:
Cross-asset flows (e.g., BTC$\leftrightarrow$ZEC/XMR) execute as atomic swaps or corridor protocols; neither side needs to trust a centralized intermediary.

Auditable by consent:
Viewing keys and structured receipts allow specific flows to be disclosed to auditors without exposing the entire graph.

When these properties hold, private settlement capacity itself starts to behave like a monetary asset:

• A treasurer facing capital controls is not just asking “what’s the yield?” but rather, “can I still get value to my people next year if on-/off-ramps are throttled?”

• A dissident journalist or NGO cares less about upside and more about “will this still be here and spendable if my local banks freeze?”

Blockchain may be waiting for its SSL moment. The analogy is suggestive: in 1994, putting credit card information on the Web seemed reckless until SSL made encrypted commerce viable. E-commerce grew into a multi-trillion-dollar industry once confidentiality became default. Today, most public blockchains are “public by default” the way HTTP was—every transaction visible, every address linkable. Privacy is plausibly the bottleneck for mass institutional adoption.

The institutional version is straightforward: no enterprise wants payroll, vendor rates, or treasury operations visible by default. The unlock is one-click, non-custodial BTC$\leftrightarrow$XMR/ZEC with refund-safe UX and clear settlement analytics—privacy as a product, not a promise.

In that environment:

• The rails (privacy corridors, shielded pools) earn fees for providing unseizable, auditable settlement capacity.

• The claims on those rails (e.g., corridor LP positions and Work Credits) are service, operating, or derivative claims. They may be held, but are not presumed stores of value.

You can think of Private Money as:

“Rights to future, censorship-resistant, auditable settlement capacity.”

The SoV properties from §3: First Principles: What a SoV Must Survive map naturally:

• Credible scarcity. Capacity is constrained by bandwidth, cryptographic verification costs, and capital at risk.

• Cheap public verification. Anyone can verify that a transaction was correctly formed, swapped, or refunded.

• Censorship-resistance & portability. Flows ride over non-custodial corridors; exit options span multiple assets and jurisdictions.

• Neutrality & permissionlessness. Adversarially diverse relays, routers, and LPs; public metrics on concentration.

• Native demand. Demand is created by repression itself.

• Lawful privacy. Viewing keys + PIDL receipts mean regulated entities can prove compliance without deanonymizing entire networks.

• Duration-neutrality. Claims participate in fee flows and scarcity premiums, not fixed coupons.

On a balance sheet, Private Money can coexist with BTC and fiat, but it plays a different role:

• BTC: thermodynamic base, global risk asset, macro hedge.

• Fiat: near-term unit of account, legal tender, credit medium.

• Private Money: repression-hedged rail, a way to ensure you can still pay and be paid without being fully seen.

Tip: hover a heading to reveal its permalink symbol for copying.