// pay

Choose who and how much. We handle the pool, the proof and the relayer.

RecipientAddress, ENS, or @username
Amount
Token
Privacy modeLonger delays make timing analysis harder
Invoice details (optional, for a payment receipt)+
Invoice ID
Merchant

Adds a receipt commitment so you can later prove “I paid this invoice” without revealing your wallet.

Advanced: relayer & how this works+
RelayerFeeUptimeReputationLatency

Any relayer can submit your proof, and you can always self-relay. No single relayer can block or redirect a payment: recipient and fee are bound inside the proof.

1. Deposit. Your wallet deposits standard-size notes into the privacy pool.

2. Prove. Your browser creates a zero-knowledge proof that you own one of the pool's deposits, without saying which one.

3. Relay. A relayer submits the proof after a random delay, so your sending wallet never appears in the withdrawal transaction.

Association set. Withdrawals prove membership in a published set of accepted deposits, which lets honest users separate themselves from illicit funds.

Privacy score90/100 · Strong
Network fee
…
Relayer fee
0 USDC
Protocol fee · 0.25%
0 USDC
Estimated arrival
~1 h – 6 h
Recipient receives
—

Your sending wallet will not be directly linked to the receiving wallet on-chain. Privacy is probabilistic, not absolute.

Why this score?+
  • Anonymity set35/35

    1,840 similar deposits

  • Timing16/25

    Time between deposit and withdrawal

  • Amount pattern15/15

    1 standard note(s)

  • Address reuse15/15

    Fresh recipient

  • Pool activity9/10

    64 deposits in 24h

The score estimates linkability from public data. It is not a guarantee — privacy also depends on how you and others use the pool.