Skip to main content
Yes. Fees are charged per intent, based on whether the transfer is shielded:
  • Unshielded transfer: 2.5% (250 bps) of amountIn
  • Shielded transfer: 7% (700 bps) of amountIn
Fees are deducted from amountIn before settlement. They cover solver compensation and protocol overhead.
Typically well under a minute end-to-end on directly supported chains. If the source chain isn’t directly supported and routes through Near Intents or Relay, expect a small additional delay for the public hop.
No. The relayer is open-access. Endpoints are rate-limited at the platform level (see rate limits), and signature-protected endpoints validate per-request signatures.
The user is refunded via an on-chain escape mechanism on BridgeIntentV2. Funds are never at risk.
The HTTP API works from any environment that can make HTTPS requests, browsers, Node, React Native, Cloudflare Workers, Vercel Edge. The TypeScript SDK is WIP; until it ships, integrate directly against the Relayer HTTP API.
Show the settlement transaction hash from GET /intent-details/:intentId (settleTxHash on source chain, solveTxHash on destination chain). Verifiable selective-disclosure records (exportable receipts) are planned; see viewing permissions.
No. Funds settle to stealth addresses owned by Safes whose keys derive from the recipient’s own viewing/spending keys. Tachyon broadcasts transactions on the recipient’s behalf (gasless sweep via POST /recipient/relay-proxy) but doesn’t hold custody.
USDC, USDT, ETH, ZEN, and cBTC. Per-chain availability varies, query POST /get-routes (API ref) for live pairs on any source/destination.
No. Tachyon does not perform identity verification or sanctions screening. Integrators apply their own compliance layer before signing intents, and can use selective disclosure to satisfy audit requirements.
Solver onboarding is documented separately for solver operators. Reach out to the team via github.com/tachyonpe if you’re interested.
The on-chain escape mechanism on BridgeIntentV2 lets users withdraw funds independently of any Tachyon-operated infrastructure.
Yes. Use Near Intents or Relay to hop to a Tachyon-supported chain first, then create a Tachyon intent from there. The final leg (and the recipient’s visibility on the destination) stays private. See supported chains.
The protocol uses hybrid cryptography designed to resist both current and future (including quantum) attacks.
Submission-time viewers cannot be removed once the intent is signed. For reversible disclosure, share records out of band using the recipient’s viewing key, the user controls who they share with, and can stop sharing at any time.
Tachyon’s hosted testnet at testnet.app.tachyon.pe. The relayer base URL is https://relayer.tachyon.pe for both testnet and mainnet; select the network via the chain IDs in your requests. All chains listed on supported chains have matching testnets.
Open an issue at github.com/tachyonpe, or reach the team directly through your integrator channel.

Get started

Submit your first intent in five minutes.