Live on testnet. Mainnet coming soon.
Where it fits
- A wallet adding “private receive” as a primary action
- A treasury moving funds between chains without leaking the counterparty
- A user paying someone without exposing the relationship on-chain
What’s confidential
| On-chain (source) | Solver batch broadcast (pre-bid) | Post-bid (to winning solver) | |
|---|---|---|---|
| Sender address | ✓ (calls createIntent) | ||
| Token pair, amount, reward | ✓ | ✓ (batched with others) | ✓ |
| Destination chain | ✓ | ✓ | ✓ |
| Recipient address | Encrypted blob only (relayer key) | ✓ (re-encrypted to solver) | |
| Per-intent amount | ✓ | Aggregated across batch | ✓ |
| Sender ↔ recipient linkage | Solver sees both, but only for intents they won | ||
| Settlement on destination | Fresh stealth address |
Integration shape (two-step flow)
Today, submission is two steps:createIntent on source chain, plus POST /store-recipients on the relayer. See the bridge guide for the full code path.
Planned SDK call:
Settlement timing
Solvers fill on the destination chain immediately after bid win. Typical settlement is well under a minute end-to-end on directly supported chains. If your user’s source chain isn’t directly supported, an additional public hop (via Near Intents or Relay) precedes the confidential leg, the hop is public, but the final delivery is always private.Use the hosted UI
If you don’t want to integrate yet, the hosted Tachyon app supports the bridge end-to-end:Open the hosted bridge
Connect a wallet and send a confidential transfer without writing code.
Try it
Bridge integration guide
Step-by-step integration on testnet, using the real
createIntent + /store-recipients flow.