Privacy lab
Every trade on PipTradeDex ships with a Privacy Receipt that names each leg as public, confidential, linkable or unknown. This page shows the checks behind it, live.
Model attestation, checked now
NEAR AI Cloud gateway, Intel TDXThe assistant that reads a typed trade runs inside a TEE. Press the button and this page asks the gateway for a fresh attestation report with a nonce it just generated, then checks that the quote binds the signing key and that nonce.
Leak study
Public chain data onlyAn observer who reads chains sees a deposit and, later, a payout. Can they tie the two together? We run four heuristics (amount, timing, address reuse, pair rarity) over our own completed trades and report how many could be singled out. Aggregates only, no addresses or hashes.
How a receipt is classified
| Leg | Visibility | Who can see it |
|---|---|---|
| Prompt to model | Confidential when encryption and the reply signature both verified, otherwise unknown | Gateway metadata only |
| Deposit | Public | Anyone on the origin chain |
| Swap | Confidential on the private route, public otherwise | Confidential Intents validator set, bridge, relay and solvers, none named in the docs |
| Payout | Public | Anyone on the destination chain |
| Deposit to payout linkage | Unknown until measured | An observer with public data |
A receipt never contains the typed text, only its hash. There is no privacy score. A shield or unshield into a Confidential Intents balance publicly links a wallet and is marked linkable. Nothing here says 100% private, because the deposit and payout are public transactions.
Your own receipts
Open the terminal, finish a swap, and press Privacy receipt on the card. Each receipt is hashed and downloadable.