Trust & security

Every Flip swap is verifiable on-chain. Your funds never leave your custody until you sign a transaction with your own wallet. This page explains exactly what Flip can and can't do, what the protocol enforces cryptographically, and how to verify any swap yourself.

What you control

Your wallet, your keys, your signature. Flip never has access to your private keys — your wallet (MetaMask, Phantom, Sparrow, Ledger, etc.) holds them and signs transactions locally. Flip cannot move your funds without you explicitly signing each transaction, and every signature prompt shows you what you're approving before you confirm.

What's enforced on-chain

When you start a swap, the protocol generates a temporary deposit address with a deadline. If solvers don't fill your order before that deadline, your funds are automatically refunded to the refund address you specified. This is enforced by smart contracts — not by Flip's good intentions.

Solvers (the parties that fill cross-chain orders) post collateral in advance. If a solver fails to deliver your destination tokens, the protocol penalizes their collateral and refunds you. There is no scenario where a swap completes from your side and you don't receive your tokens.

How to verify any swap

Every swap creates two on-chain transactions: a deposit on the source chain and a settlement on the destination chain. Both are public and visible on any block explorer.

Find your deposit:When you start a swap, Flip shows you a deposit address. Look it up on the source chain's explorer (Etherscan for Ethereum, Blockstream for Bitcoin, Solscan for Solana, etc.) — your tokens arriving there is the deposit confirmation.

Find your settlement:When the swap completes, your destination tokens land at the recipient address you specified. Look that address up on the destination chain's explorer — you'll see the incoming transaction with the exact amount.

Both transactions are also linked from flipdex.co/status for any swap you've started on this device. You can also paste any deposit address there to look up its status — Flip doesn't require an account, so anyone with a deposit address can audit the swap.

What can go wrong (and what protects you)

Quote expires before you sign: Quotes are valid for about 5 minutes. Flip auto-refreshes them before they expire. If no deposit lands, no swap happens — your funds stay where they are.

You send the wrong amount: If your deposit is less than the quoted amount (most common with manual BTC/SOL transfers), the protocol marks the swap incomplete and waits for the missing amount, or refunds you after the deadline.

Settlement fails:If solvers can't deliver your destination tokens, you're automatically refunded to the refund address you set. This is on-chain code, not human judgement.

You send to a wrong address you typed in: This is the one case nothing protects you from — crypto transactions are irreversible. Flip validates the address format before quoting (e.g. checks that BTC destinations are valid Bitcoin addresses), but the actual send happens from your own wallet, which Flip cannot intercept.

What you're actually trusting

Flip is a non-custodial interface to a third-party settlement network. You're trusting three things, in roughly this order of risk:

The Flip interface (this site)to construct your swap request correctly. The worst Flip could do is generate a deposit address you didn't intend to send to — but you see the address before sending and can verify it against the protocol's public records. Flip cannot move funds without your signature.

The underlying settlement protocol to enforce solver behavior, deadlines, and refunds. The protocol is on-chain code, not a company; its rules are publicly auditable. See the Terms page for the specific network Flip routes through and links to its own security disclosures.

The destination network to confirm and finalize the delivery transaction. This is base-layer cryptocurrency security (Ethereum, Bitcoin, Solana, NEAR, etc.) — not Flip-specific, not something we control or modify.

Reporting issues

Security concerns or suspected bugs go via the contact form — pick "Security disclosure" or "Bug report" as appropriate. See the Security page for scope and the disclosure process. For issues with the underlying settlement protocol itself, contact details are documented in the Privacy page's third-party section.