PROOF REQUEST

Ask for exactly one fact.

Choose the threshold, name yourself as the audience, set an expiry. Send the link. It opens the holder’s review screen, which shows precisely what you will learn before they approve.

Build a requestNo account

CLAIM

Holds at leastThreshold. The balance is never revealed.Received a paymentRoadmapOne payment, by transaction id.Received at least, sinceRoadmapIncome over a period, as a threshold.Holds exactlyBy designAn exact amount. Deliberately not offered: thresholds reveal less.

WHAT YOU ASK FOR

Proof of fundsOne proof: they hold at least this much.Exit certificateFor coins about to be sent to you.ReservesA batch summing every note, none twice.

THRESHOLD

= 50,000,000,000 zatoshi · proven in 0.125 ZEC steps

AUDIENCE

blake2b →

Your verifier identifier. The proof carries only its hash, never this name.

UNMOVED SINCE · OPTIONAL

Require the coins to have been in the chain at this block and untouched after it, e.g. a block before a known incident. It proves when the coins last moved, not where they came from.

Detect the same coins used twice with you this monthThe request names this month (202610). Within it the same notes give the same tags, so you see a second use; nobody else can link them. Always on for exit certificates.

EXPIRY

ordays

The proof stops verifying this many days after the holder generates it.

RESPOND BY

Bind to the holder’s Solana accountFor on-chain verifiers. Only that account can use the proof, so a copied proof is worthless.

Send this linkReady

Fix the highlighted fields and the link appears here.

STATELESSNothing is stored. The whole request is encoded in the link itself. No server keeps it, there is no account, and closing this tab forgets it.