Where to start

Choose the path that matches your technology stack:

• I'm building a backend service (use Core)
  • Start with the Core docs: Simple Bridge Introduction to understand the protocol and HTTP API flows.
  • Review Silent Swap Complete Example or Simple Bridge Complete Example for server-side integration patterns.
• I'm building a DEX with React
  • Start with React Overview to see how the SDK fits your component tree.
  • Review React Silent Swap Complete Example or React Simple Bridge Complete Example for complete integration examples.
  • Check out React Silent Swap Introduction and React Simple Bridge Introduction to understand the underlying flows.
• I'm building a DEX with Vue
  • Start with Vue Overview to see how the SDK fits your component tree.
  • Review Vue Complete Example for a complete integration example.
  • Check out Simple Bridge Introduction to understand the underlying bridge flows.
• I'm building a wallet (use Core)
  • Start with the Core docs: Simple Bridge Introduction to understand the protocol and HTTP API flows.
  • Focus on account management, signing flows, and how to surface SilentSwap as an option in your send/swap UI.
  • Review Silent Swap Complete Example or Simple Bridge Complete Example for integration patterns.

What you need

SilentSwap works with any EOA wallet (like MetaMask, Phantom, or any wallet that supports EIP-1193), Solana wallets (like Phantom, Solflare), and Bitcoin wallets (like Unisat, Xverse, OKX). It integrates similar to any RFQ (Request for Quote) API. You don't need specific RPC endpoints or wallets.

• Basic integration requirements
  • Ability to sign EVM transactions and messages via any EOA wallet
  • For Solana swaps: Solana wallet connection (Phantom, Solflare, etc.)
  • For Bitcoin swaps: Bitcoin wallet connection (Unisat, Xverse, OKX, etc.)
  • Your existing wallet connections work as-is
  • SilentSwap works like any RFQ API – request quotes, execute transactions
• Backend capabilities (recommended)
  • A small backend (or serverless) environment to store configuration, API keys, and handle callbacks
  • Monitoring/alerting for swap and bridge status in production
• Product & UX readiness
  • Clear entry points in your product for "Private swap" or "Private transfer"
  • A plan for educating users about privacy guarantees and limitations

What you don't need

• You don't need to custody user funds at any point
• You don't need to expose or manage user seed phrases
• You don't need specific RPC endpoints or wallet providers – any EOA wallet works
• You don't need to build your own TEE, SCA, or facilitator infrastructure – the SDK and protocol cover this
• You don't need to redesign your entire app – you can start by adding a single "Private" path to an existing flow