Send shielded Zcash to someone who has no wallet yet. CashDrop seals it in a one-time envelope, on your device, and hands you a link. The wallet can come after the money.
Amount, note, optional password. A fresh shielded address is derived on your device.
Send the amount plus a 0.0001 reserve from any shielded wallet. Save the recovery file.
Paste the link into an encrypted chat. The password, if any, travels another way.
Open it, make a wallet if needed, and the browser proves and sweeps the funds locally.
Checkout turns any phone into a shielded point of sale. Plans sell subscriptions where the customer approves every renewal. To confirm a payment, your browser rebuilds the merchant wallet from its recovery file and scans testnet itself. No account, no dashboard, no customer record.
On a transparent chain, a payment link would publish who paid whom, how much, and everything they do next. Zcash’s shielded pool hides all of it, and CashDrop keeps both the funding and the claim shielded.
Shielding hides the payment from the chain. It can’t hide a link pasted into the wrong chat, so here is exactly where the edges are.
Read the full threat model →A static PWA. No CashDrop API, user database, custodial wallet or analytics pipeline. There is nowhere for your keys to go.
Yes. The beta runs on the public Zcash testnet with real shielded addresses and transactions. Testnet coins have no monetary value.
It carries encrypted recovery material for a fresh shielded wallet. Treat it like cash: whoever unlocks the complete link can claim first.
No. It’s non-custodial. Save the recovery file when you create a drop, fund, checkout or plan.
Never. CashDrop holds no wallet authority. Every renewal is a payment the customer chooses to send.
Not yet. This release is testnet-only and needs an independent security review before it handles real value.