> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sweepr.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Networks & Contracts

> Supported network routing, public contract addresses, and EVM sweep notes.

# 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                |

## 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.

| Network   | V4 / Permit2 Contract                                                                                                              | Explorer             |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| Base      | [`0xCc59af29190ef3198a45dc517e889A9EA5fE9328`](https://basescan.org/address/0xCc59af29190ef3198a45dc517e889A9EA5fE9328)            | Basescan             |
| Monad     | [`0x7891cdEECe6f9c6eA1a19C6E53ACc27366173c28`](https://monadscan.com/address/0x7891cdEECe6f9c6eA1a19C6E53ACc27366173c28)           | Monadscan            |
| Ethereum  | [`0x2B43fc4516fFdBE4716c8D674e1032c640f33508`](https://etherscan.io/address/0x2B43fc4516fFdBE4716c8D674e1032c640f33508)            | Etherscan            |
| BNB Chain | [`0x1B703BEbA919d5117c2432015311A679828f24bf`](https://bscscan.com/address/0x1B703BEbA919d5117c2432015311A679828f24bf)             | BscScan              |
| Avalanche | [`0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58`](https://snowscan.xyz/address/0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58)            | Snowscan             |
| Polygon   | [`0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58`](https://polygonscan.com/address/0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58)         | PolygonScan          |
| Optimism  | [`0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58`](https://optimistic.etherscan.io/address/0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58) | Optimistic Etherscan |
| Arbitrum  | [`0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58`](https://arbiscan.io/address/0x64fF60c4F3E022A7F9D64eDE19DFFA79b4555c58)             | Arbiscan             |

## 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:

```txt theme={"dark"}
GET https://dev-api.sweepr.co/sweepr/v2/status
```

Current V5 Partner V2 contracts:

| Network   | V5 Contract                                                                                                                        | Explorer             |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| Base      | [`0xeb6329d5c53feebd3c4a61d4a831c82de173bc85`](https://basescan.org/address/0xeb6329d5c53feebd3c4a61d4a831c82de173bc85)            | Basescan             |
| Monad     | [`0xecd8d57a1fbc6138f45761c59a182e3e4b04a051`](https://monadscan.com/address/0xecd8d57a1fbc6138f45761c59a182e3e4b04a051)           | Monadscan            |
| Ethereum  | [`0x9728af50eee177869b044a8011203b771d67cfeb`](https://etherscan.io/address/0x9728af50eee177869b044a8011203b771d67cfeb)            | Etherscan            |
| BNB Chain | [`0x9014fa92fde5f435abe0c66db04982a9eff50d82`](https://bscscan.com/address/0x9014fa92fde5f435abe0c66db04982a9eff50d82)             | BscScan              |
| Avalanche | [`0x5d13c4b18b9553e0e670bcffac96888ec7f999ee`](https://snowscan.xyz/address/0x5d13c4b18b9553e0e670bcffac96888ec7f999ee)            | Snowscan             |
| Polygon   | [`0xa1bce5b22596bec5982625d0f32bd1119c3cf2f7`](https://polygonscan.com/address/0xa1bce5b22596bec5982625d0f32bd1119c3cf2f7)         | PolygonScan          |
| Optimism  | [`0x9be2819db660fc84f4841c026c81adf041314295`](https://optimistic.etherscan.io/address/0x9be2819db660fc84f4841c026c81adf041314295) | Optimistic Etherscan |
| Arbitrum  | [`0x33fbb55cb5ffe2c9293aac472abc2798313071c1`](https://arbiscan.io/address/0x33fbb55cb5ffe2c9293aac472abc2798313071c1)             | Arbiscan             |

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.