Skip to main content
No. Intent contents are end-to-end encrypted. Only the user (via their viewing key) and the specific solver assigned the intent can read it. The organization holds no plaintext access.
No. Mixers obfuscate by pooling funds, which can complicate compliance. Tachyon uses confidential intents with selective disclosure, each transaction is private from the public but verifiable to designated counterparties.
Only the user (via viewing key), the assigned solver (only the contents needed to fulfill that intent), and any addresses the user designated as viewers at submission time.
Use post-hoc records. The user can call tachyon.user.exportRecord (or exportRecords) to produce a verifiable disclosure for any past intent and share it with a counterparty out of band. See viewing permissions.
See the up-to-date list at supported chains. Direct support is expanding; chains not directly supported can be reached via Near Intents and Relay before the confidential leg.
The protocol is built for production use. While on testnet, do not move real value. Once mainnet launches, transfer-size limits and recommended practices will be documented per rate limits.
No. Viewing access is strictly read-only. Viewers cannot initiate transfers, modify transactions, or move funds in any way.
Per-tranche amounts, schedule, and total order size are confidential. The market never sees the parent order or upcoming tranches, only stealth-address fills on the destination chain, with no link between them.
An on-chain escape mechanism lets users withdraw funds without any Tachyon-operated infrastructure. There is no scenario where outage causes funds to be locked indefinitely.
The protocol uses hybrid cryptography designed to resist both current and future (including quantum) attacks.
Email sudeep@tachyon.pe. Please do not open public GitHub issues for security bugs. See security overview.

Security overview

Properties Tachyon stands behind, in plain language.