01 PAYMENT PRIVACY / EVIDENCE
Follow the proof.
Find the leak.
Turn a shielded payment into evidence you can inspect. Verify what the recipient wallet saw, then catch sensitive values that escaped into logs.
- LOCAL Browser processing
- REDACTED Hashes, never raw markers
- OPEN JSON evidence
02 PROOF DESK
Interrogate the evidence.
Choose a recorded case or bring your own CLI report. Everything is processed in this tab.
RECORDED CLI EVIDENCE
Loading report…
Loading recorded CLI evidence…
BROWSER-LOCAL CANARY SCAN
Did a private value reach the log?
Plant a synthetic marker, paste the application output, and inspect every exact match. The export keeps only hashes and line numbers.
Evidence boundary: this scan covers only the supplied text and literal markers. It does not observe a wallet, transaction, browser telemetry, or network traffic.
03 COLLECT REAL EVIDENCE
The proof begins beside the wallet.
Run the CLI beside your recipient wallet. It observes the payment, scans your logs, and writes the redacted report this desk can inspect.
Open the setup guidepython ztestkit.py \
--uri-file /private/request.txt \
--rpc-url http://127.0.0.1:50233 \
--rpc-cookie /private/rpc-cookie \
--account-uuid YOUR_ACCOUNT \
--txid YOUR_TRANSACTION \
--network regtest \
--canary-file /private/canaries.txt \
--log /private/app.log \
--report /private/report.json