compact-core:compact-privacy-disclosure

A witness-value disclosure error occurs when private witness data reaches a public boundary without explicit permission. You must wrap witness-derived values in a disclose() annotation at the first public boundary to safely reveal them.

To apply disclose() correctly in Compact contracts, wrap witness-derived values at the exact public boundary where data exits private scope, such as ledger writes, exported circuit returns, or conditional branches, to prevent unintended leakage.

The Witness Protection Program tracking model monitors how private witness data flows through Compact contracts. It enforces domain separation, commitments, nullifiers, and selective disclosure to ensure only explicitly disclosed data becomes public.

You need to use disclose() for ledger writes and exported circuit returns whenever witness-tainted data crosses into a public scope. Applying it at these boundaries ensures the compiler recognizes intentional selective disclosure and passes privacy checks.

Yes, you can implement commitments, nullifiers, and MerkleTree proofs without triggering witness taint errors by ensuring all derived values crossing public boundaries are wrapped in disclose() to declare the exact scope of selective disclosure.

The limitation of disclose() is that it must be placed precisely at the first public boundary; incorrect placement can still leak witness data across conditionals or fail to resolve compiler errors regarding undisclosed witness values in privacy patterns.