Selective disclosure

Open a disclosure

Paste the view-key the merchant sent you over a separate channel. Decryption happens in this browser; the envelope travels in the URL fragment, which is never sent to a server.

What a CipherBill view-key is

An AES-256-GCM key the merchant generated in their own browser for one disclosure bundle. It is not a STRK20 protocol viewing key and not part of the STRK20 auditor key escrow. A STRK20 viewing key is registered once per account, is immutable, and only the account owner can register it.

· This key cannot decrypt STRK20 pool notes, derive nullifiers, read shielded balances, or authorize spending. Its authority begins and ends at one bundle.

· A bundle is application metadata the merchant's browser recorded, plus transaction hashes. It is not a zero-knowledge proof and carries no merchant signature.

· Deposits and withdrawals at the STRK20 pool edges are already public on Starknet, addresses and amounts included. Encrypting a report about them does not make them private.

· Totals cover only the scope the merchant disclosed. A milestone-scoped or confirmed-only export reports figures for the records it includes, not for the whole invoice.