Sweep Lifecycle
Sweepr follows a deliberate lifecycle: connect, scan, review, preview, execute, complete. The UI stays simple, while chain-specific hooks and services handle the differences between Solana, Base, Monad, and other EVM networks.
1. Connect
The user connects a wallet for the selected network. Sweepr keeps Solana and EVM wallet paths separate so the active chain, active wallet, and signing surface remain clear.
The app uses Solana Wallet Adapter for Solana flows and Wagmi/Viem with Reown AppKit for EVM flows. Embedded and mini app contexts are handled separately where available.
2. Scan
Sweepr reads balances for the active wallet and active chain. Token data is normalized into a shared model containing:
- token mint or contract address
- symbol and display name
- decimals and raw balance
- estimated USD value
- token logo where available
- chain id and output eligibility
On Solana, token discovery and enrichment are powered by Helius. On Base, Sweepr uses Alchemy for balance discovery. Other EVM networks use backend discovery paths configured per chain.
3. Review
The review step is where the user chooses what to include. Sweepr separates detected value from selected value so the user can decide whether the sweep is worth executing.
The UI intentionally keeps these numbers visible:
- detected dust count
- selected token count
- potential recoverable value
- selected recoverable value
4. Preview
Preview is the safety gate. Sweepr checks selected tokens for route availability, estimated output, price impact, slippage, native gas balance, and blocked states.
The preview also displays the service charge and expected receive amount. If a token cannot be routed cleanly, it should be skipped or blocked instead of being silently included.
5. Execute
Execution depends on the chain:
| Network Type | Execution Path |
|---|---|
| Solana | Jupiter routes and sequential wallet transactions |
| Base | EIP-5792 batch calls where supported, sequential fallback otherwise |
| Monad and other EVM networks | Configured backend aggregator routes with batch or sequential fallback |
| Base mini app | Can use paymaster support when configured |
6. Complete
After execution, Sweepr shows the completion state and stores local sweep history with transaction references where available. History is browser-local, so clearing site data can remove it.