Your browser runs verification locally before any funds leave your wallet. If any check fails, nothing is sent.
Your browser confirms the deposit address matches an active Asgard vault and the swap memo is registered on-chain before you send.
Your browser verifies the deposit channel exists and its parameters match your swap via Chainflip’s public broker API.
Your browser confirms the intent is registered and swap parameters match via the 1Click API. Intent contracts are publicly auditable on-chain.
Your browser verifies the cryptographic proof locally — no external API required. The only protocol where you don’t trust any third party to tell you the truth.
Four ways a swap can lie to you. Four checks your browser runs locally before approving the transaction.
An attacker swaps the protocol’s vault address for one they control. Funds appear to leave correctly — they don’t come back.
The quote you see and the quote that gets executed don’t match. A hidden spread, a wrong route, or a downgraded asset.
The protocol never received your swap intent. Funds land in the right address and sit there indefinitely with no path home.
The amount you approve at the wallet differs from the amount actually transmitted. A skim, a rounding “error,” a fee not disclosed.
Not on trust. Not on a third party’s word. On math performed locally, in your own session, before a single byte of transaction data is broadcast.
Every swap parameter and network address is independently verified by your browser’s local environment — ensuring zero-trust security long before any funds leave your wallet.