Skip to main content

Security Model

Sweepr is non-custodial. It can read public wallet balances, request quotes, prepare transactions, and ask the wallet to sign. It cannot move funds without the user's wallet approval.

What Sweepr Checks​

Before execution, Sweepr evaluates selected tokens for practical route risk:

  • route availability
  • estimated output
  • minimum receive amount
  • price impact
  • slippage tolerance
  • native gas balance
  • provider or aggregator errors
  • wallet warnings for large approval batches

If a token cannot be evaluated safely, Sweepr should warn, skip, or block it.

Approval Safety​

EVM sweeps can require token approvals. Batch-capable wallets may show multiple approvals and the sweep call in a single request. Users should verify:

  • the selected network matches the wallet prompt
  • the spender is the correct Sweepr contract for that network
  • the token amounts match the selected balances
  • the output asset matches the preview
  • the expected receive amount and service charge are acceptable

Slippage And Price Impact​

Dust balances can still route through thin liquidity. Sweepr surfaces slippage and price impact before signing so users can skip poor routes instead of accepting unexpectedly bad execution.

Slippage protects the minimum acceptable output. Price impact reflects how much the trade itself moves the market. Both are separate from the Sweepr service charge.

Native Balance Buffer​

Users should keep a small native-token balance for network fees. Sweepr maintains per-chain minimum native balance checks to reduce the chance that a wallet signs a sweep and then cannot pay for follow-up transactions.

Signing Rule​

If the wallet prompt does not match the Sweepr preview, cancel. Re-scan before retrying, because quotes and liquidity can change quickly.