> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tachyon.pe/llms.txt
> Use this file to discover all available pages before exploring further.

# Tachyon: privacy-native cross-chain payments

> Tachyon is a privacy-native cross-chain payment protocol. Submit signed intents; Tachyon delivers confidentially across chains.

Tachyon is a privacy-native cross-chain payment protocol. You submit a signed *intent* describing what you want, for example, *"move 1,000 USDC from Arbitrum to this address on Base"*, and Tachyon handles the rest. Intent contents are end-to-end confidential: on-chain observers cannot link sender, recipient, amount, or route.

Where existing rails fall short:

* **Stablecoin settlement networks** give you movement but no privacy.
* **Single-chain confidential execution** gives you privacy but locks you to one VM.
* **Tachyon gives you both**, private settlement, chain-agnostic.

The protocol is VM-agnostic by design. EVM (secp256k1), SVM (Ed25519), Move (Aptos, Sui), and Canton are all handled by the same confidential machinery, and on-chain dependencies are minimal so new chains roll out in days. See [supported chains](/concepts/supported-chains) for the full list.

<Note>
  Tachyon is currently live on testnet. Mainnet is coming soon. Try all features at [testnet.app.tachyon.pe](https://testnet.app.tachyon.pe).
</Note>

## Who integrates Tachyon

<CardGroup cols={2}>
  <Card title="Wallets" icon="wallet">
    Add private send and receive as a first-class feature without rebuilding settlement.
  </Card>

  <Card title="Payroll & payouts" icon="money-bill-transfer">
    Disburse to contributors across chains while keeping amounts and recipients confidential.
  </Card>

  <Card title="Agents & APIs" icon="robot">
    Pay HTTP 402 invoices from autonomous agents without exposing spending patterns.
  </Card>

  <Card title="Trading tools" icon="chart-line">
    Execute size over time without leaking strategy to on-chain observers.
  </Card>
</CardGroup>

## Core products

Tachyon ships four products on top of the same confidential settlement layer.

<CardGroup cols={2}>
  <Card title="Confidential Bridge" icon="arrow-right-arrow-left" href="/products/confidential-bridge">
    Transfer tokens between chains without revealing source, destination, or amount.
  </Card>

  <Card title="Confidential Payroll" icon="users" href="/products/confidential-payroll">
    Run private salary streams and recurring payouts with auditor-controlled visibility.
  </Card>

  <Card title="Private TWAP" icon="chart-line" href="/products/private-twap">
    Execute time-weighted average price orders without exposing strategy or schedule.
  </Card>

  <Card title="x402 Micropayments" icon="credit-card" href="/products/x402-payments">
    Confidential HTTP 402 payments for agents and APIs.
  </Card>
</CardGroup>

## How integrators use Tachyon

Today's flow is two steps: call `BridgeIntentV2.createIntent` on source chain (public solver-facing offer), then `POST /store-recipients` to the relayer (encrypted recipient bundle). Track the intent by polling `GET /intent-details/:intentId` until it reaches `completed`.

The SDK (WIP) wraps both into a single call. Under the hood the protocol batches your intent with others for solver broadcasting, and only re-encrypts recipient info to the solver that wins the bid.

```ts theme={null}
// Planned SDK surface
const { intentId } = await tachyon.intent.submit({
  sourceChain: "base_mainnet",
  destChain:   "horizen_mainnet",
  tokenIn:  USDC_BASE, tokenOut: USDC_HORIZEN,
  amountIn: 1_000_000_000n, minAmountOut: 999_000_000n, reward: 50_000_000n,
  deadline: Math.floor(Date.now() / 1000) + 600,
  recipients: [{ address: "0xRecipient...", amount: 999_000_000n }],
}, wallet);

tachyon.intent.subscribe(intentId, (intent) => {
  if (intent.status === "completed") console.log(intent.settleTxHash);
});
```

<Card title="Get started in 5 minutes" icon="play" href="/quickstart">
  Install the SDK and submit your first testnet intent.
</Card>

## What's guaranteed, what's public

Tachyon gives you **recipient-side confidentiality**. The sender's on-chain action is visible on the source chain; the recipient and the linkage between sender and recipient are not.

|                            | On-chain (source)            | Solvers (pre-bid, batched) | Post-bid (winning solver only)                  |
| -------------------------- | ---------------------------- | -------------------------- | ----------------------------------------------- |
| Sender                     | ✓                            |                            |                                                 |
| Token pair, amount, reward | ✓                            | Batched with others        | ✓                                               |
| Destination chain          | ✓                            | ✓                          | ✓                                               |
| Recipient                  | Encrypted blob (relayer key) |                            | ✓ (re-encrypted to solver)                      |
| Permit signatures          |                              |                            | ✓                                               |
| Sender ↔ recipient linkage |                              |                            | Solver sees both, but only for intents they won |

The encrypted blob in the on-chain event is the protocol's recovery anchor, it's only decryptable with the relayer key, which lets state be re-traced from on-chain history if the relayer is ever lost.

See [privacy guarantees](/concepts/privacy-guarantees) for the full breakdown and threat model.

## Where to go next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="play" href="/quickstart">
    Submit your first intent on testnet.
  </Card>

  <Card title="Concepts" icon="book" href="/concepts/overview">
    Mental model: intents, solvers, stealth addresses, settlement.
  </Card>

  <Card title="SDK" icon="code" href="/sdk/installation">
    Install, authenticate, submit, track, retrieve.
  </Card>

  <Card title="Reference" icon="file-code" href="/reference/intent-schema">
    Schemas, errors, rate limits.
  </Card>
</CardGroup>
