Soda Labs

Selective disclosure as a compliance primitive

Bilateral disclosure versus publishing to everyone

Where privacy tech meets the rulebookGlobal

What Selective disclosure as a compliance primitive actually says

Supervisory access, external audit and suspicious activity reporting are all bilateral disclosures to a named party under a legal duty. Public-ledger transparency is something else entirely: universal, unauthorised disclosure to everyone, permanently. No other part of the financial system is asked for the second in order to satisfy the first. Viewing keys are the oldest worked example, letting a holder share visibility of shielded activity without surrendering the ability to spend, and they are already used for exchange deposit detection and custodian-to-auditor disclosure. Threshold decryption generalises this to a quorum. Two honest caveats. We found no regulator that has endorsed the pattern in guidance, so this is an argument from structure rather than from authority. And viewing keys are blunt: per address, retrospective and prospective at once, with no revocation once shared.

The instruments that matter

Zcash viewing keys
derived from the spending key; an incoming viewing key detects deposits, a full viewing key exposes value, memo and target address without exposing the spend key
Threshold and auditor keys
generalise the same idea to a quorum, removing the single point of failure a lone disclosure key creates

What this means for confidential transactions

Bubble is built for exactly this shape of obligation: amounts and balances live on chain as ciphertexts, computation happens without decryption, and the only disclosure path is an on-chain access list through which an authorized party - an auditor, a supervisor, a counterparty - can request scoped decryption. That is confidentiality from the public, not from the regulator.

Compliant by default.

See how selective disclosure satisfies a supervisor without publishing your book to the world.