Skip to main content

Networks & Contracts

Sweepr uses one product surface, but routing and execution are chain-specific. Solana routes through Jupiter. EVM networks use sweep contracts, router allowlists, and aggregator-built calldata.

Supported Networks

NetworkDiscoveryRoutingExecution
SolanaHeliusJupiterSequential wallet transactions
BaseAlchemyMulti-DEX aggregator, Odos, EVM routersEIP-5792 batch calls or sequential fallback
MonadBackend discoveryOdos / KyberSwap-backed routesBatch or sequential fallback
EthereumBackend discoveryBackend aggregator routesBatch or sequential fallback
BNB ChainBackend discoveryBackend aggregator routesBatch or sequential fallback
AvalancheBackend discoveryBackend aggregator routesBatch or sequential fallback
PolygonBackend discoveryBackend aggregator routesBatch or sequential fallback
OptimismBackend discoveryBackend aggregator routesBatch or sequential fallback
ArbitrumBackend discoveryBackend aggregator routesBatch or sequential fallback

Active Contract Addresses

These V4 / Permit2 addresses come from the public client configuration used by the current web app. Click an address to open it in the network explorer.

V3 Status

V3 contracts are not active in the current public sweep flow. They are intentionally not listed as active spender contracts here.

Contract Behavior

The EVM sweep contract receives approved input tokens, executes allowlisted router calls, checks minimum output, applies the configured service charge, and returns the output token to the user. V4 / Permit2 flows are used where enabled to reduce approval friction while keeping the final sweep wallet-owned and user-signed.

Wallet Verification

When signing on EVM networks, compare the spender shown in the wallet prompt with the Sweepr contract address for the active network. If the spender does not match the expected contract or the route looks unfamiliar, cancel and re-scan.
Last modified on June 14, 2026