8 chains supportedZero manual bridgingDestination address locked at quote time

BC

Security

Last updated August 27, 2026

The short version

We never hold your private keys or seed phrase — every swap and purchase is signed in your own wallet. Once you get a quote, the destination address is locked in on our side and can't be changed by anyone, including us, before execution. The one place this app does involve a third party holding funds briefly is disclosed below, not hidden.

Destination-address binding

When you request a quote, the destination address and amount are locked into that quote at the moment it's created. Every later step reads the destination back from that locked record — it is never re-accepted from your browser again. This is the specific protection against a "man-in-the-middle swaps your destination address mid-transaction" attack, which was the core threat this app was designed around from day one.

Two different trust models, by rail

  • Solana ↔ EVM swaps (Jupiter/Relay). Fully non-custodial — your wallet calls the bridge's smart contract directly. We never take custody of your funds at any point.
  • BTC/ETH/SOL → Sui purchases (ChangeNOW). Relay has no Sui support, so this path uses ChangeNOW, a custodial exchange: you send funds to a deposit address it controls, and it sends Sui back to you afterward — the same kind of counterparty trust as using a centralized exchange to convert currency, not a trustless bridge. We disclose this plainly rather than implying every path in the app works the same way. Your own Sui wallet still signs the final purchase, so funds can never be silently redirected mid-flow on our end.

Verified on real transactions, not just in theory

This runs on Solana mainnet with real funds, not a testnet. Swaps have been run and independently verified directly on-chain — checking actual transaction receipts and wallet balances via public RPC endpoints, not just trusting what our own database says happened.

The code is public

This app's source is open on GitHub — you don't have to take our word for any of the above. Read the code yourself.

Related

See Privacy for what data we collect, and Terms for the full terms of use.