> For the complete documentation index, see [llms.txt](https://thanasdefitools.gitbook.io/thanasdefitools-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thanasdefitools.gitbook.io/thanasdefitools-docs/sweeper/what-is-the-sweeper.md).

# What Is the Sweeper?

The **Sweeper** is a one-transaction tool for cleaning up wallet dust on Flare. You select a list of tokens you no longer want; one signature later, they're either consolidated into a single output token (WFLR or USDT0) or burned to `0x…dEaD`. No per-token approvals beyond a one-time Permit2 setup, no separate transactions per token, no manual swap-and-bridge dance.

It lives at [thanasdefitools.xyz/sweeper](https://thanasdefitools.xyz/sweeper) and runs on Flare mainnet. Songbird and Coston2 don't have the canonical Uniswap Permit2 contract deployed, so the Sweeper is unavailable there.

## When to use it

The Sweeper is for the long tail of tokens that build up in any active wallet:

* **Airdrops you didn't ask for.** Spam tokens that arrived because someone wanted to associate your address with their project. They're worth slightly more than zero, individually too small to bother swapping one at a time.
* **Leftover dust from past trades.** When you swapped 99% of a position out, that 1% remainder you never quite got around to clearing.
* **Old governance / yield-farm tokens** for projects you've stopped following but still hold a few units of.
* **Anything you'd rather see consolidated** into WFLR or USDT0 instead of cluttering your token list.

If a single token is large enough to swap by itself, you're probably better off using a regular DEX or aggregator — the Sweeper's value comes from batching N tokens into one Permit2 signature + one onchain transaction.

## How it differs from a regular swap

A regular swap-aggregator transaction:

1. Approve the router to spend token X
2. Sign a swap of token X → output (separate signature)
3. Pay gas for one swap
4. Repeat for token Y, token Z, …

A Sweeper transaction:

1. Approve **Permit2** (canonical Uniswap address) once per token. This is a one-time setup — future sweeps of the same token need no further approvals.
2. Sign **one** Permit2 batch signature listing all the tokens and amounts you want to sweep.
3. Pay gas for **one** transaction that pulls all N tokens, runs each through the right router, and forwards the aggregate output to your wallet.

The economy of scale starts paying off around 3+ tokens. Below that the savings are mostly UX (one signature, one tx confirmation).

## What gets routed where

The frontend tries each leg on **Enosys Route** first (this site's own swap router, which searches every major Flare DEX and the liquid staking protocols for the best path), while the Sweeper contract's owner keeps it allowlisted (it is). If Enosys Route can't route a token, the FE uses OpenOcean, and then BlazeSwap or Enosys V2 with a direct or 1-hop path (OpenOcean refuses dust below its minimum-USD-value threshold, which the V2 fallback covers). Each leg has its own minimum (its quote less your slippage tolerance), and the Sweeper contract also checks the total once all legs have run (`outputToken.balanceOf(this) ≥ minTotalOut`), so the total can't fall below your signed minimum.

Enosys Route also test-trades tokens that aren't on its curated list. A token that can't be sold (a honeypot) or whose transfer tax would take half the trade or more isn't swapped anywhere; it's offered for burning instead.

For those tokens, and for tokens where no swap route exists at any venue (very illiquid), the FE pops a small modal letting you either drop them from the sweep entirely or queue them for a chained burn transaction that fires automatically after the sweep mines.

## What the contract actually holds

**Nothing, between transactions.** The MultiSweeper contract is fully stateless: every sweep pulls in the user's tokens via Permit2, swaps them, and forwards every wei of output before the transaction returns. There is no admin function that can withdraw fees, no upgrade path, no take-rate skimmed off the top. Read [Risks and FAQs](/thanasdefitools-docs/sweeper/risks-and-faqs.md) for the full trust model.