Privacy and disclosure
A Chainjump swap publicly links an Ethereum account to a Monero recipient. Zero knowledge protects private witness material beyond the public statement.
Public on Ethereum
Section titled “Public on Ethereum”| Action | Published information |
|---|---|
| Creation | User, recipient address, ETH principal, minimum XMR, height, difficulty, and deadlines |
| Bidding | Solver identities and XMR amounts |
| Settlement | Swap ID, Monero transaction ID, and selected output key in calldata |
Terminal storage deletion does not erase transaction history. A fresh Monero subaddress reduces address reuse but remains visible in the intent.
Provers and infrastructure
Section titled “Provers and infrastructure”A remote prover receives the witness, including transaction components, outgoing-proof data, inclusion paths, and work blobs. The wallet’s transaction secret key is not a witness field, but the witness reveals payment relationships. Select prover identities accordingly.
RPC providers can observe requests and simulations. Private submission must protect transaction delivery from public-mempool or searcher sharing; HTTPS alone does not establish that policy.
Local records
Section titled “Local records”Solver state, artifacts, logs, and backups contain payment and transaction recovery data. Remote errors can echo sensitive material even when solver-authored log fields omit credentials. Restrict access to these records and wallet/requester secrets.
The website stores pending transaction information in the browser. A shared browser profile can expose it; clearing storage does not cancel a transaction.