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

​
Public App Permit2 Contract Addresses

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

​
Partner V2 Contracts

Partner V2 uses SweeprBatchV5PartnerFees for EVM on-chain partner/protocol fee splitting. V5 addresses are configured by Sweepr backend per chain and exposed through:
Current V5 Partner V2 contracts: The current public app can continue using the existing V4 path while Partner V2 is tested with selected integrations. Partner integrations should use /v2/status as the source of truth for enabled chains, contract addresses, output tokens, and router allowlists.

​
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 July 5, 2026