In-App Execution
How a selected quote becomes a signed transaction: the Suuuper row settles through the Suuuper contract, provider rows through that provider's own router.
In-App Execution
Every quote on the panel is executable inside the app. What differs is where the transaction goes.
- The Suuuper row settles through the Suuuper settlement contract on that network. It is deployed on all four supported networks, so an engine-routed swap always executes atomically with wallet-delta verification and dust refunds. See Settlement Contract.
- Provider comparison rows are that provider's own quote, so the transaction is built against that provider's own router and signed in your wallet.
| Provider | Router used |
|---|---|
| Uniswap | Universal Router |
| SushiSwap | RouteProcessor |
| KyberSwap | Kyber Aggregation Router |
| PancakeSwap | Smart Router |
The execution sequence
- Select a row. BEST is selected automatically; you can pick any other row.
- Chain check. If your wallet is on a different network, Suuuper prompts the switch before building anything.
- Approval, if needed. ERC-20 inputs are approved for the exact amount of the current swap, to that route's own spender. Permit2 where it is used, the router directly where it is not. No infinite allowances.
- Pre-flight simulation. The transaction is simulated before your wallet opens. If it would revert, the reason is decoded and shown in plain language instead of a raw hex error.
- Sign. The built transaction carries your minimum-out floor and a deadline, both enforced on-chain.
Same protections everywhere
- Minimum out derived from your slippage setting, encoded into the call and enforced on-chain. The transaction reverts rather than deliver less.
- Deadlines on every built transaction, so a stale signature cannot be replayed later.
- Least-privilege approvals, scoped to the exact amount of the swap you asked for.
- Decoded revert reasons in plain language.
See Fees for how the 0.15% fee applies.