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
| Network | Discovery | Routing | Execution |
|---|---|---|---|
| Solana | Helius | Jupiter | Sequential wallet transactions |
| Base | Alchemy | Multi-DEX aggregator, Odos, EVM routers | EIP-5792 batch calls or sequential fallback |
| Monad | Backend discovery | Odos / KyberSwap-backed routes | Batch or sequential fallback |
| Ethereum | Backend discovery | Backend aggregator routes | Batch or sequential fallback |
| BNB Chain | Backend discovery | Backend aggregator routes | Batch or sequential fallback |
| Avalanche | Backend discovery | Backend aggregator routes | Batch or sequential fallback |
| Polygon | Backend discovery | Backend aggregator routes | Batch or sequential fallback |
| Optimism | Backend discovery | Backend aggregator routes | Batch or sequential fallback |
| Arbitrum | Backend discovery | Backend aggregator routes | Batch 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.
| Network | Active Contract | Explorer |
|---|---|---|
| Base | 0xCc59af29190ef3198a45dc517e889A9EA5fE9328 | Basescan |
| Monad | 0x7891cdEECe6f9c6eA1a19C6E53ACc27366173c28 | MonadVision |
| Ethereum | 0x2B43fc4516fFdBE4716c8D674e1032c640f33508 | Etherscan |
| BNB Chain | 0x1B703BEbA919d5117c2432015311A679828f24bf | BscScan |
| Avalanche | 0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58 | Snowtrace |
| Polygon | 0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58 | PolygonScan |
| Optimism | 0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58 | Optimistic Etherscan |
| Arbitrum | 0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58 | Arbiscan |
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.