# Sumo Docs (full text)

> Complete Sumo documentation in one file. The page index is at https://docs.sumo.trade/llms.txt.

# Welcome to Sumo

> The all-in-one platform for token market making on Solana and EVM chains.

- URL: https://docs.sumo.trade/
- Markdown: https://docs.sumo.trade/index.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo is the all-in-one market making platform for token founders and professional market makers. Manage wallets, execute automated trading strategies, and monitor performance — all from a single dashboard.

Whether you're launching a new token or managing liquidity for an established project, Sumo gives you the tools to maintain healthy markets across Solana and EVM chains.



## What Sumo Does

Sumo runs market operations for a token from one dashboard. A **profile** is one token on one chain, with its own wallets, strategies, and treasury. An **organization** is your Sumo account: it can hold many profiles across Solana, Ethereum, BNB Smart Chain, Base, Robinhood Chain, Stable Mainnet, and Tron.

* **Launch or import a token.** Launch on PumpFun, BONK.fun, America.Fun, Memoo, Meteora DAMM v2, Four.meme, Flap, PancakeSwap, Pons V2, Uniswap, SushiSwap, and Aerodrome with bundled wallet buys, or import a token that already trades.
* **Run automated strategies.** Counter Trade offsets external buys and sells to stabilize price. DCA, Limit Orders, Instant Trade, and Snipe Token Supply cover scheduled, market-cap-triggered, manual, and launch-time trading.
* **Manage wallets at scale.** Generate, import, group, and fund hundreds of wallets. Keys are protected with envelope encryption and never exist in plaintext.
* **Build wallet history.** Wallet Farm creates aged wallets with real on-chain activity and privacy-funded balances, ready to import into any profile.
* **Move funds.** Treasury tools cover withdrawals, privacy cashout, stable and custom swaps, cross-chain swaps, airdrops, burns, token cleanup, and wrap/unwrap.
* **Watch execution.** Live trading feed, trade logs, treasury logs, audit logs, surveillance, and Bubblemaps holder analysis, with Telegram alerts.

## Where to Start

* **New to Sumo:** [create an account](/getting-started/create-account), then [choose your path](/getting-started/choose-your-path) between launching and importing.
* **Already have a token:** [import an existing token](/getting-started/import-existing-token) and set up [Counter Trade](/strategies/counter-trade).
* **Launching:** pick your launchpad under [Launch Tokens](/launch-tokens/pumpfun-launch) and prepare wallets with [Wallet Farm](/wallet-farm/overview).

## Documentation Sections

| Section                                              | Covers                                                                                    |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| [Getting Started](/getting-started/choose-your-path) | Account creation, profiles, funding, dashboard, importing or launching a token            |
| [Launch Tokens](/launch-tokens/pumpfun-launch)       | Per-launchpad launch wizards for Solana, Ethereum, BSC, Base, Robinhood Chain, and Stable |
| [Strategies](/strategies/overview)                   | Counter Trade, DCA, Limit Orders, Instant Trade, Snipe Token Supply, Impact Calculator    |
| [Wallet Farm](/wallet-farm/overview)                 | Aged wallets, activity generation, privacy funding, import to profile                     |
| [Wallets](/wallets/how-wallets-work)                 | Generation, import, groups, marketplace, key export, encryption                           |
| [Treasury](/treasury/treasury-dashboard)             | Withdraw, swaps, cashout, airdrops, burn, token cleanup                                   |
| [Insights & Logs](/reporting)                        | Live trading, trade and treasury logs, audit logs, surveillance, notifications            |
| [Integrations](/integrations/supported-chains)       | Supported chains, DEXes, aggregators, Telegram bot                                        |
| [Account & Settings](/account/user-settings)         | User settings, user management, rewards, key export policy                                |
| [Platform Fees](/platform-fees) and [FAQ](/faq)      | Fee schedule and common questions                                                         |

Every page is also available as Markdown: append `.md` to any docs URL, or fetch [llms.txt](/llms.txt) for an index and [llms-full.txt](/llms-full.txt) for the complete documentation in one file.


---

# Video Tutorials

> Watch SUMO walkthroughs by workflow, then jump to the matching written guide.

- URL: https://docs.sumo.trade/video-tutorials
- Markdown: https://docs.sumo.trade/video-tutorials.md
- Docs index: https://docs.sumo.trade/llms.txt

Use this page when you want to browse SUMO by workflow instead of reading docs page by page. Each video also appears inline on its matching guide.


---

# Create Your Account

> Sign up for Sumo and set up your organization.

- URL: https://docs.sumo.trade/getting-started/create-account
- Markdown: https://docs.sumo.trade/getting-started/create-account.md
- Docs index: https://docs.sumo.trade/llms.txt

Get started with Sumo by creating your account. The process takes under a minute.

![Sumo signup page](/images/signup.png)

## Invite Code

Sumo signup is invite-only. If you do not already have an invite code, contact us on [Telegram](https://t.me/sumo_support) and we can provide one.

## Sign Up

1. Go to [app.sumo.trade](https://app.sumo.trade) and click **Sign Up**
2. Enter your **invite code** when prompted
3. Enter your **email address**, **organization name**, and choose a **password** (minimum 8 characters)
4. Verify your email with the code sent to your inbox
5. You're in

An organization is automatically created for you when you sign up. You can invite team members later from [Settings](https://app.sumo.trade/settings).

## Log In

1. Go to [app.sumo.trade](https://app.sumo.trade)
2. Enter your **email** and **password**
3. Complete the **2FA challenge** (email code or Telegram verification)
4. You're in

Sumo supports two-factor authentication via **email code** or **Telegram**. You can configure your preferred 2FA method in [Settings](https://app.sumo.trade/settings).

## What's Next

Now that your account is set up, start with the dashboard overview, then choose whether you want to import an existing token or launch a new one.

- [Dashboard Overview](/getting-started/dashboard-overview): Understand the main profile dashboard and quick actions.

- [Choose Your Path](/getting-started/choose-your-path): Decide whether to import an existing token or launch a new token through Sumo.


---

# Dashboard Overview

> Understand the main Sumo dashboard after you log in.

- URL: https://docs.sumo.trade/getting-started/dashboard-overview
- Markdown: https://docs.sumo.trade/getting-started/dashboard-overview.md
- Docs index: https://docs.sumo.trade/llms.txt

After you log in, the dashboard gives you a high-level view of every trading profile in your organization. Use it to check which profiles are live, compare balances, and jump into the right workspace.

> **Video: Navigating The Sumo Dashboard**
>
> A quick tour of the dashboard, project profiles, key metrics, and the main setup actions.
>
> https://www.youtube.com/watch?v=noonznG5tmY

![Sumo dashboard showing trading profiles, balances, and quick actions](/images/dashboard-overview.png)

## What You See

Each profile row shows the token, quote pair, pool address shortcut, supported integrations, and key treasury totals. Expanded rows show the wallets or wallet groups attached to that profile.

The dashboard highlights:

* **Market cap and liquidity** - Current project market cap and pool liquidity.
* **Supply and value** - How much token supply your wallets hold and its estimated value.
* **Native or quote balance** - SOL, ETH, BNB, USDC, or other quote assets available to the profile.
* **Wallet count** - Number of wallets attached to the profile.
* **Status toggle** - Enables or disables the profile from the dashboard.

## Quick Actions

Use the buttons in the top-right to start the main setup flows:

* **Import Token** - Add an existing token or pool to Sumo.
* **Launch New Token** - Create a new token through one of Sumo's launch methods.

Each profile row also has quick action icons for common profile tasks, such as opening the profile workspace, copying the pool address, or accessing more actions.

## Clone a Profile

Use the clone icon on a profile row to create a copy of that profile inside the same organization. Cloning is available to **Trader** roles and above, and the clone dialog asks for a name for the new profile.

The clone copies:

| Copied               | Notes                                                                                                |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| **Profile settings** | Chain, DEX, pool, token, and execution settings                                                      |
| **Wallets**          | Cloned with the same on-chain addresses as the source profile, keeping each wallet's original status |
| **Wallet groups**    | Group structure is rebuilt and re-pointed at the cloned wallets                                      |
| **Strategies**       | Copied and re-pointed at the cloned wallets and groups                                               |

Some settings are deliberately not carried over, because they are specific to the source profile: fee and cashback overrides, fee collector assignments, viewer access links, and launch workflow state such as funding wallets, allocations, and wallet-group assignments. If the source was a launch profile, the clone keeps the launch method but not its in-progress launch data.

> **Clones Start Archived**
>
> A cloned profile is created with **archived** status and opens in Live Trading once created. Review its wallets and strategies, then activate it from the dashboard status toggle when you are ready to trade.

> **Cloned Wallets Share Addresses**
>
> Cloned wallets are not new wallets. They share the same on-chain address and key material as the source profile's wallets, so both profiles see the same balances and history. Generate new wallets instead if you need the clone to trade from separate addresses.

## Copy or Transfer a Profile

Archived profiles can be copied to another organization with a **transfer code**. The destination organization generates a short-lived code and shares it with you; entering it in **Copy or Transfer Profile** sends the profile's operational state — settings, wallets, and groups — to the destination.

Historical records stay in the source organization: order history, fee accounting, referral attribution, and audit logs are never moved, and the source profile remains archived after a successful transfer. Codes are multi-use with a profile limit and expire after a few hours.

## What's Next

- [Choose Your Path](/getting-started/choose-your-path): Decide whether to import an existing token or launch a new token.

- [Import an Existing Token](/getting-started/import-existing-token): Add an existing token or pool to Sumo.

- [Launch a New Token](/getting-started/launch-new-token): Create a new token through Sumo's launch wizard.

- [Wallet Farm](/wallet-farm/overview): Prepare wallets before a profile exists.


---

# Choose Your Path

> Decide whether to import an existing token or launch a new token through Sumo.

- URL: https://docs.sumo.trade/getting-started/choose-your-path
- Markdown: https://docs.sumo.trade/getting-started/choose-your-path.md
- Docs index: https://docs.sumo.trade/llms.txt

After you create an account, the first decision is whether you already have a token to manage or whether you want Sumo to launch one for you.

| Goal                              | Use This             | Result                                                                                                                                            |
| --------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| You already have a token or pool  | **Import Token**     | Creates a trading profile for that existing token so you can trade, manage wallets, and monitor activity in Sumo                                  |
| You want Sumo to create the token | **Launch New Token** | Creates a pre-launch profile, prepares launch wallets and launch settings, submits the launch, then activates the profile after the token is live |

## Import an Existing Token

Use this path when the token already exists on-chain, or when the liquidity pool already exists on a supported DEX. You provide the token or pool details, attach wallets, optionally add starter strategies, and Sumo creates a profile for ongoing market operations.

- [Import an Existing Token](/getting-started/import-existing-token): Add an existing token or pool to Sumo.

## Launch a New Token

Use this path when you want Sumo to create the token and run the launch flow. The launch wizard starts as a pre-launch profile. After launch, the profile becomes the active trading workspace for the new token.

- [Launch a New Token](/getting-started/launch-new-token): Pick a launch method and understand the pre-launch flow.

## Further Reading

* [How to Launch a Memecoin in 2026](https://blog.sumo.trade/how-to-launch-a-memecoin/) — what to prepare before choosing the launch path
* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — how launchpad pricing works before a token graduates to a pool


---

# Import an Existing Token

> Add an existing on-chain token or pool to Sumo and create a trading profile for it.

- URL: https://docs.sumo.trade/getting-started/import-existing-token
- Markdown: https://docs.sumo.trade/getting-started/import-existing-token.md
- Docs index: https://docs.sumo.trade/llms.txt

Use **Import Token** when the token already exists on-chain, or when a liquidity pool already exists and you want Sumo to trade, monitor, and manage wallets for it.

This path creates a **trading profile** for an existing token. A trading profile defines which token you're trading, which chain and DEX to use, which wallets belong to the profile, and how Sumo should execute trades.

If you want Sumo to create and launch a brand-new token instead, start with [Launch a New Token](/getting-started/launch-new-token).

> **Video: How to Import a Live Token Profile**
>
> A walkthrough of importing an existing token, configuring routing, setting up wallet groups, and adding starter strategies.
>
> https://www.youtube.com/watch?v=7gEww8t6vVE

## Import an Existing Token

1. From the [dashboard](https://app.sumo.trade/dashboard), click **Import Token**
2. Complete **Token Info** with your profile name, token address, routing fields, and execution defaults
3. Click **Continue** to resolve the token details before moving to Wallet Setup
4. Complete **Wallet Setup** by creating wallets, importing keys, copying wallets from Wallet Farm, or copying wallets from another profile
5. Optionally add starter strategies in **Strategies**
6. Review the final preview and click **Import**

![Import Token modal for creating a trading profile](/images/import-token.png)

## Flow

The import flow creates the trading profile and its initial wallet setup together. If you include a pool address and DEX, the profile is created as an active trading profile. If you only enter the token information, Sumo saves a draft profile that you can finish later from Profile Settings.

### Token Info

Token Info defines what token Sumo will track, how it should price the token, and which execution route the profile should use. The base token address is required. The quote token defaults to the chain's wrapped native asset unless you choose another quote token.

### Wallet Setup

Wallet Setup decides which wallets are attached to the new profile:

* **Create New** — Generate one or more new wallets
* **From Farm** — Move Wallet Farm wallets into this profile
* **From Profile** — Copy wallets from another profile in the same organization
* **Import Keys** — Import existing private keys

If you create a wallet group in this step, the imported wallets are added to that group as part of the same import.

### Strategies

You can create Counter Trade, DCA, and Limit Order strategies before importing, by hand or from a strategy preset - Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Starter strategies are created inactive and target all wallets by default, so you can review wallet assignments and settings before activating them.

## Profile Fields

### Profile Name

Give your profile a descriptive name, e.g. "MYTOKEN Market Making" or "MYTOKEN DCA".

### Pool Address

Paste the on-chain pool address (or pool ID) for your token's liquidity pool. Sumo automatically resolves the pool and fills in the DEX, base token, and quote token for you.

> **Smart Pool Resolution**
>
> When you paste a pool address, Sumo detects the DEX, identifies both tokens in the pair, and fetches token metadata (symbol, decimals, image) — all automatically.

### Network

Select the blockchain network where your token lives. Sumo supports:

* **Solana Mainnet**
* **Ethereum**
* **BNB Smart Chain**
* **Stable Mainnet**
* **Base**
* **Robinhood Chain**
* **Tron Mainnet**
* **Ethereum Sepolia** (testnet)

### Pool DEX

Automatically set when you resolve a pool address. You can also select manually. See [Supported DEXes](/integrations/supported-dexes) for the full list.

### Base Token & Quote Token

These are resolved automatically from the pool address. The base token is your project's token and the quote token is the asset it's paired against (e.g. SOL, WETH, WBNB).

You can also enter token addresses manually if you're not using pool resolution.

### Execution Provider

Choose how trades are routed:

* **DEX** (default) — Trades execute directly on the selected pool
* **Aggregator** — Trades route through a DEX aggregator for best-price execution (e.g. Jupiter, 0x). Some aggregators charge a small additional fee on top of the trade.

If your token trades on a single pool, **DEX** is recommended — it's direct and fee-free. If your token has significant liquidity across multiple pools, an **Aggregator** can find better prices through cross-pool routing, even accounting for the small additional fee.

See [Supported Aggregators](/integrations/supported-aggregators) for available options per chain. Stable Mainnet and Tron have no aggregator integrations, so profiles on those chains always use direct DEX execution.

### Default Slippage

Maximum slippage tolerance for trades, in percent. Default is 1%. Individual strategies can override this.

### Trade with Native

When enabled, Sumo trades with the chain's native asset (SOL, ETH, BNB) instead of its wrapped version. Enabled by default.

## Preview & Import

As you complete Token Info and Wallet Setup, the preview pane shows the profile summary that will be created:

* Token symbol, profile name, token address, quote address, pool address, and network
* Native balance and quote balance across the wallets selected for import
* Token and quote decimals
* Total token supply
* Default slippage

The final preview summarizes the profile, wallets, balances, and starter strategies. Review the details and click **Import** to finalize. You'll be taken to the Live Trading page for the new profile.

## What's Next

- [Profile Settings](/getting-started/profile-settings): Fine-tune your profile with slippage, risk limits, and strategy defaults.

- [Launch a New Token](/getting-started/launch-new-token): Compare this import path with Sumo's guided token launch flows.


---

# Launch a New Token

> Start a Sumo launch draft, configure wallets and funding, then activate the trading profile after launch.

- URL: https://docs.sumo.trade/getting-started/launch-new-token
- Markdown: https://docs.sumo.trade/getting-started/launch-new-token.md
- Docs index: https://docs.sumo.trade/llms.txt

Use **Launch New Token** when you want Sumo to create the token and run the launch sequence for you. This is different from importing an existing token: a launch starts as a **pre-launch profile**, then becomes an active trading profile after the launch completes.

> **Video: How to Launch a Token On Sumo**
>
> A full launch walkthrough covering token setup, buy planning, wallet funding, and launch execution.
>
> https://www.youtube.com/watch?v=CbQ1TYr0XEY

![Token Launch wizard for creating a new token](/images/token-launch.png)

## How Launch Profiles Work

1. Start from the dashboard and click **Launch New Token**
2. Pick a launch method
3. Enter token metadata and launch settings
4. Create, import, or buy the wallets needed for the launch
5. Fund the launch wallets
6. Optionally add starter strategies, by hand or from a built-in or org-saved strategy preset
7. Review the preview and submit the launch
8. After launch, Sumo activates the profile for live trading, strategies, wallets, logs, and reporting

Launch profiles usually create role-based wallet groups such as dev wallets, bundle wallets, holder wallets, sniper wallets, tax wallets, or injection wallets depending on the launch method.

Each launch also needs a launch-fee payment method. You can use one **Launch Ticket** from your organization's ticket inventory, or pay the launch fee as a **0.25% token-supply dev allocation** for that launch. See [Platform Fees](/platform-fees) and [Rewards](/account/rewards) for the ticket purchase and fee details.

## Supported Launch Methods

| Launch method                                                    | Chain           | Use when                                                                                                                                          |
| ---------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| [PumpFun Solana](/launch-tokens/pumpfun-launch)                  | Solana          | You want a PumpFun SOL or PumpFun USDC launch with bundle and optional migration controls                                                         |
| [Meteora DAMM v2 Solana](/launch-tokens/meteora-dammv2-launch)   | Solana          | You want a Meteora DAMM v2 SOL or USDC pool launch                                                                                                |
| [BONK.fun Solana](/launch-tokens/bonkfun-launch)                 | Solana          | You want a BONK.fun / Raydium LaunchLab launch with bundled WSOL buys                                                                             |
| [America.Fun Solana](/launch-tokens/americafun-launch)           | Solana          | You want an America.Fun USD1 launch with Meteora DBC migration support                                                                            |
| [Memoo Solana](/launch-tokens/memoo-launch)                      | Solana          | You want a Memoo / Raydium LaunchLab launch                                                                                                       |
| [Uniswap V2 Ethereum](/launch-tokens/uniswap-eth-launch)         | Ethereum        | You want to deploy an ERC-20 and launch a WETH pool on Ethereum                                                                                   |
| [Uniswap Base](/launch-tokens/uniswap-base-launch)               | Base            | You want to deploy an ERC-20 and launch a Uniswap V2 or V3 WETH pool on Base                                                                      |
| [Aerodrome Base](/launch-tokens/aerodrome-base-launch)           | Base            | You want to deploy an ERC-20 and launch an Aerodrome Classic pool                                                                                 |
| [Uniswap Robinhood](/launch-tokens/robinhood-uniswap-launch)     | Robinhood Chain | You want to deploy an ERC-20 and launch a Uniswap V2 or V3 WETH pool on Robinhood Chain                                                           |
| [SushiSwap Robinhood](/launch-tokens/robinhood-sushi-launch)     | Robinhood Chain | You want a SushiSwap Launchpad token where the launchpad seeds liquidity and every buy lands in one creator transaction                           |
| [Pons V2 Robinhood](/launch-tokens/robinhood-pons-v2-launch)     | Robinhood Chain | You want a Pons V2 native bonding-curve launch that graduates to a Pons V4 pool                                                                   |
| [lunch.fun Robinhood](/launch-tokens/robinhood-lunch-fun-launch) | Robinhood Chain | You want a lunch.fun launch straight into a permanent Uniswap pool, quoted in ETH, HOOD, USDG, or a tokenized stock, with an optional creator tax |
| [Uniswap V3 Stable](/launch-tokens/stable-uniswap-launch)        | Stable          | You want to deploy an ERC-20 and launch a USDT0-quoted Uniswap V3 pool on Stable                                                                  |
| [PancakeSwap V2 BSC](/launch-tokens/pancakeswap-v2-bsc-launch)   | BNB Smart Chain | You want to deploy an ERC-20 and launch a WBNB pool on BSC                                                                                        |
| [Four.meme BSC](/launch-tokens/fourmeme-bsc-launch)              | BNB Smart Chain | You want to launch through Four.meme and submit BSC bundle buys                                                                                   |
| [Flap BSC](/launch-tokens/flap-bsc-launch)                       | BNB Smart Chain | You want a Flap bonding-curve launch with Tax V3 duration, anti-farmer, and dividend controls                                                     |

## Wallets

You can use ready wallets, create new wallets, or buy aged wallets during the launch wizard. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

## After Launch

After the launch lands, Sumo opens the live trading workspace for the new token. From there you can monitor the chart, inspect trade flow, manage wallets, activate strategies, use treasury actions, and review launch logs.

- [Import an Existing Token](/getting-started/import-existing-token): Use this path instead when the token or pool already exists.

- [Wallet Farm](/wallet-farm/overview): Prepare wallets before a launch or import flow.

## Further Reading

* [How to Launch a Memecoin in 2026](https://blog.sumo.trade/how-to-launch-a-memecoin/) — the full launch playbook, from wallet prep to post-launch market making
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — interactive simulator with real bonding-curve math for every supported launchpad
* [Do You Need a Dev to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-dev/) — why most launches need zero custom code


---

# Profile Settings

> Configure slippage, strategy defaults, and MEV protection for your trading profile.

- URL: https://docs.sumo.trade/getting-started/profile-settings
- Markdown: https://docs.sumo.trade/getting-started/profile-settings.md
- Docs index: https://docs.sumo.trade/llms.txt

After creating your trading profile, you can configure default settings that apply across your strategies. These defaults save time when creating new strategies — you can always override them per-strategy.

Access profile settings from your profile page by clicking **Settings** in the navigation.

> **Video: Trading Profile Settings Walkthrough**
>
> A walkthrough of profile routing, trading defaults, market alerts, AutoFix, strategy defaults, MEV settings, and client portal controls.
>
> https://www.youtube.com/watch?v=HuPnGiJi3RM

![Profile Settings page with settings tabs and Trading Configuration content](/images/profile-settings.png)

Settings are split into sections in the left pane. Each section can be edited independently and saved with **Save Settings**.

## Trading Configuration

Trading Configuration controls profile routing, token metadata, and default execution behavior.

Routing fields such as **Network**, **Pool DEX**, **Execution Provider**, and **Pool Address** are editable only while the profile is in `draft`, `pre-launch`, or `archived`. Once a profile is active, token and route identity stays locked so strategies, reporting, and live trading remain consistent.

Read-only fields show the resolved base token, quote token, decimals, total supply, and circulating supply. Use **Refresh Supply** if the token supply metadata needs to be re-fetched.

### Default Slippage (%)

Maximum slippage tolerance for trades, measured in **basis points (bps)** where **100 bps = 1%**.

Individual strategies can override this default with their own slippage settings.

> **Slippage Warning**
>
> **Too low** — Trades will fail frequently, especially in volatile markets or low-liquidity pools.
>
> **Too high** — You become an easy target for MEV bots (sandwich attacks), which profit by front-running your trades.
>
> A range of **50–200 bps (0.5%–2%)** works well for most tokens.

### Trade with Native

When enabled, Sumo trades with the chain's native asset (SOL, ETH, BNB) instead of its wrapped version. Enabled by default.

### Max Tx Retries

Number of times Sumo will retry a failed transaction before giving up. Default is 3.

### Private Relay

For EVM profiles, private relay routes eligible trades through private execution paths for MEV protection.

### Fee on Transfer

For EVM profiles, enable this when the traded token charges a transfer tax or similar fee.

## Market Alerts

Market Alerts notify traders when market or social signals cross thresholds for the profile.

| Setting                           | Description                                                                  |
| --------------------------------- | ---------------------------------------------------------------------------- |
| **Alert Mode**                    | Choose pump alerts, dump alerts, both directions, or off                     |
| **Window (Minutes)**              | Rolling time window used to evaluate the alert                               |
| **Price Move Threshold (%)**      | Price move required before an alert can trigger                              |
| **Cooldown (Minutes)**            | Minimum time before another similar alert is sent                            |
| **Min External Gross Volume ($)** | External volume required inside the window before alerts fire                |
| **Social Alerts**                 | Ingest qualified X posts for the token and notify traders when a cue matters |

The social link fields are read-only metadata resolved from token and pair sources. Use **Refresh Socials** to re-fetch them when the pool has updated metadata.

## AutoFix

AutoFix controls the wallet-maintenance suggestions shown on the Live Trading page. It is designed for active DCA, Counter Trade, and Limit Order strategies where a wallet can become unusable because it is low on gas, low on quote asset for buys, or low on project token for sells.

| Setting                    | Description                                                                                                       |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Low gas**                | Shows wallets below the configured native-asset threshold and can suggest a treasury-swap gas refill or archival. |
| **Low quote balance**      | Shows buy wallets that no longer have enough quote asset for the configured number of planned trades.             |
| **Low token balance**      | Shows sell wallets that no longer have enough project-token balance for the configured number of planned trades.  |
| **Low Gas Threshold**      | Native-asset balance where the wallet starts appearing as low gas.                                                |
| **Critical Gas Threshold** | Lower native-asset balance that marks the wallet as urgent.                                                       |
| **Gas Refill Amount ($)**  | Dollar amount of quote asset Sumo should swap per wallet when using AutoFix to refill gas.                        |
| **Warning Trade Buffer**   | Number of minimum-size planned trades a wallet should be able to cover before it is warned.                       |
| **Critical Trade Buffer**  | Lower buffer used to mark a wallet as critical.                                                                   |

AutoFix suggests one of three fixes for each issue. Low-gas wallets can **Refill** gas by swapping some of a stablecoin quote into the native asset. Buy wallets that hold the native asset but not enough quote can **Convert** spare native into the quote token, which is how wallets funded with SOL, ETH, or BNB get their first balance of a custom or stablecoin quote. Wallets that cannot be fixed by a swap are offered **Archive**. A conversion only spends native that sits above the Native Refill Threshold plus the swap's own fees, so the wallet stays above the threshold after it runs.

Use AutoFix to keep strategy wallets operational without manually scanning every balance. It does not move funds automatically just because a warning appears; traders still choose whether to run the suggested fix.

## Default Instant Buy / Sell Settings

Configure up to **6 presets** each for instant buy and instant sell. Each preset defines an asset plus min and max amounts for quick one-click execution from the live trading page.

Presets can be denominated in USD, quote/native asset, or the profile token. Use the six slots to create different trade-size bands for quick buys and quick sells.

When you trigger an instant trade, Sumo picks a random amount between the preset's min and max to make the trade less predictable on-chain.

## Default Counter Trade Settings

Defaults are configured separately for **Default Counter Buy Into Sell** and **Default Counter Sell Into Buy** strategies:

| Setting             | Description                                                                               |
| ------------------- | ----------------------------------------------------------------------------------------- |
| **Trigger Asset**   | Asset used to express the trigger size, such as native, quote, token, or USD              |
| **Trigger Min**     | Minimum external trade size that triggers a counter trade                                 |
| **Trigger Max**     | Maximum external trade size to counter (leave empty for no cap)                           |
| **Min Capture (%)** | Minimum percentage of the detected trade to counter                                       |
| **Max Capture (%)** | Maximum percentage of the detected trade to counter                                       |
| **MEV Exclusion**   | When enabled, automatically excludes known MEV bot wallets from triggering counter trades |

## Default DCA Settings

Defaults for both **DCA Buy** and **DCA Sell** strategies:

| Setting                | Description                                                                      |
| ---------------------- | -------------------------------------------------------------------------------- |
| **Trade Asset**        | Asset used to express the per-trade amount, such as native, quote, token, or USD |
| **Trade Amount**       | Amount per DCA trade                                                             |
| **Interval (Seconds)** | Time between each DCA trade                                                      |
| **Timing Jitter (%)**  | Randomizes the interval by this percentage to make trade timing less predictable |
| **Amount Jitter (%)**  | Randomizes the trade size by this percentage for the same reason                 |

## Custom Fees

Organizations with negotiated fee and cashback terms can raise a profile's Sumo trading fees above the organization minimum.

| Setting            | Description                                                               |
| ------------------ | ------------------------------------------------------------------------- |
| **Buy Fee (bps)**  | Sumo buy-side fee for this profile. Empty inherits the organization fee.  |
| **Sell Fee (bps)** | Sumo sell-side fee for this profile. Empty inherits the organization fee. |

The section shows the effective buy fee, effective sell fee, and cashback percentage. Profile fees can only be raised above the organization minimum, and the organization cashback percentage is unchanged by profile overrides.

Custom Fees is visible only to org admins, and only when the organization has custom fee and cashback terms configured.

## Custom Tokens

The **Custom Tokens** section manages the allowlist behind [Custom Swap](/treasury/custom-swap). Each entry is a token address the profile's wallets are allowed to trade against known assets. Admins add tokens here or inline from the Custom Swap tab; removal is settings-only, so a token cannot be dropped mid-trade. Removing a token hides it from the swap selector but does not touch existing balances.

## MEV Wallet Blacklist

Manage wallets that should be ignored by your counter-trade strategies. This prevents your bot from counter-trading against known MEV bots or other wallets you want to exclude.

* **Manual** — Add wallet addresses directly, one per line
* **Auto** — Wallets added automatically by your counter-trade strategies over time as they detect MEV activity

The blacklist shows counts for manual, auto, and total blocked wallets.

## Client Portal

Client Portal creates a shareable read-only link for selected profile views. It is useful when a founder or market-making lead wants to show stakeholders the current trading workspace without giving them login access or permission to trade.

When enabled, you can:

* Copy the Client Portal link
* Rotate the link to invalidate older links
* Choose which read-only views are available, such as Trading, Strategies, Insights, Wallets, Surveillance, Logs, and Team Notes

Anyone with the active link can view the selected tabs, but trading, withdrawals, wallet edits, strategy edits, and profile settings remain disabled.

## What's Next

- [Fund Your Profile](/getting-started/funding-your-profile): Generate wallets and deposit funds to start trading.


---

# Funding Your Profile

> Generate or import wallets and deposit funds to start trading with Sumo.

- URL: https://docs.sumo.trade/getting-started/funding-your-profile
- Markdown: https://docs.sumo.trade/getting-started/funding-your-profile.md
- Docs index: https://docs.sumo.trade/llms.txt

Before you can start trading, you need wallets with funds. Sumo doesn't hold your funds in a central pool — each wallet is a real on-chain address that you fund directly.

## Step 1: Generate or Import Wallets

You need at least one wallet to start trading. From your profile, open the **Wallets** tab and click **+ New Wallets**.

### Create New

Generate one or more wallets directly inside the profile.

1. Select **Create New**
2. Choose the number of wallets to create, or use the quick count buttons
3. Optionally assign the wallets to existing wallet groups or create a new group
4. Optionally enter a seed phrase if you want to derive from a specific mnemonic; otherwise Sumo auto-selects or creates an encrypted seed for the profile
5. Click **Confirm**

![Create Wallets modal with wallet count, wallet groups, and optional seed phrase](/images/profile-funding-create-new.png)

### From Farm

Move prepared Wallet Farm wallets into the profile.

1. Select **From Farm**
2. Choose one or more Wallet Farm folders
3. Optionally assign the imported wallets to profile wallet groups or create a new group
4. Click **Confirm**

Only active Wallet Farm wallets are available for import. This is useful when you prepared wallets before the trading profile existed.

![Import From Farm modal with Wallet Farm folder selector and wallet group assignment](/images/profile-funding-from-farm.png)

### From Profile

Copy wallets from another profile in the same organization.

1. Select **From Profile**
2. Choose a source profile on the same network
3. Select individual wallets, wallet groups, or all wallets from that profile
4. Optionally assign the copied wallets to groups in the current profile
5. Click **Confirm**

![Import From Profile modal with source profile and wallet group selectors](/images/profile-funding-from-profile.png)

### Import Keys

Import existing wallets from private keys.

1. Select **Import Keys**
2. Paste private keys separated by new lines or commas
3. Optionally assign the imported wallets to wallet groups or create a new group
4. Click **Confirm**

![Import Wallets modal with private key input and wallet group assignment](/images/profile-funding-import-keys.png)

> **Seed Security**
>
> All seed phrases and private keys are encrypted at rest using AES-256-GCM with keys stored in a hardware security module (HSM). They never exist in plaintext in Sumo's application database. See [Security & Encryption](/wallets/security-encryption) for details.

## Step 2: Fund Your Wallets

Send funds directly to your wallet addresses. Each wallet's public address is visible in the Wallets dashboard.

### What to Deposit

**For Solana profiles:**

* **SOL** — Required for transaction fees and trading
* **Your token** — If running sell-side strategies

**For EVM profiles:**

* **Native asset** (ETH, BNB, etc.) — Required for gas fees
* **Your token** — If running sell-side strategies

### How to Deposit

1. Copy a wallet's public address from the dashboard
2. Send funds from your external wallet, exchange, or another Sumo profile
3. Balances update automatically within seconds

> **Deposits Are Free**
>
> There are no Sumo platform fees on deposits or withdrawals. Sumo charges a 1% platform fee on Sumo-executed trading volume.

### Funding with Privacy

If you want to avoid linking your wallets on-chain (e.g. so they don't all trace back to the same funding source), use this approach:

1. Send all funds to **one wallet** in your profile
2. Use [Privacy Cashout](/treasury/privacy-cashout) to distribute those funds from that single wallet to multiple other wallets in the profile
3. Use the destination wallets for trading
4. Archive the original source wallet so it's not used for trading

This way, your trading wallets have no direct on-chain link to each other or to the original funding source.

## Step 3: Organize with Wallet Groups (Optional)

If you're running multiple strategies or want to segment your trading activity, organize wallets into groups:

1. Go to **Wallets** → **Groups**
2. Create a new group with a name and optional color
3. Assign wallets to the group

Wallet groups let you run different strategies on different subsets of wallets. See [Wallet Groups](/wallets/wallet-groups) for details.

## Checking Balances

View balances for all wallets from:

* **Dashboard** — Treasury card shows aggregate balances
* **Wallets page** — Per-wallet SOL, wrapped native, and token balances
* **Telegram** — Use the `/balance` command for a quick summary

## You're Ready to Trade

With your account set up, profile configured, and wallets funded, you have two paths forward:

* **Launch your token through Sumo** — Use your funded wallets to create a new token through one of Sumo's supported launch methods.
* **Start trading an existing token** — If your token is already live, jump straight into setting up strategies like Counter Trade or DCA.

- [Launch a New Token](/getting-started/launch-new-token): Pick a launch method and understand the pre-launch flow.

- [Import an Existing Token](/getting-started/import-existing-token): Add an existing token or pool to Sumo.

- [Strategies Overview](/strategies/overview): Learn about Counter Trade, DCA, Limit Orders, and more.


---

# PumpFun Solana Launch

> Launch your token on PumpFun SOL or PumpFun USDC from Sumo with automated mint prep, bundled buys, funding, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/pumpfun-launch
- Markdown: https://docs.sumo.trade/launch-tokens/pumpfun-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo lets you prepare and launch a [PumpFun](https://pump.fun) token from a guided launch draft. The flow creates a pre-launch profile, prepares the launch mint automatically, sets up role-based wallets, handles funding, and submits the final bundle when everything is ready.

The launch wizard supports both **Pumpfun SOL** and **Pumpfun USDC**. Both use the same six-step workflow; the main difference is which quote asset funds launch buys.

> **Video: Live PumpFun Bundle (Live Example)**
>
> A live example of configuring wallets, funding, bundle buys, and launch execution for a PumpFun token.
>
> https://www.youtube.com/watch?v=O-ySBmQrh-E

![PumpFun token launch buy setup](/images/pumpfun-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. A funding source for the selected quote asset: SOL for Pumpfun SOL, or USDC plus SOL for Pumpfun USDC
3. A planned launch shape: supply target, wallet counts, and whether you want a post-migration snipe
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new wallets / buy aged wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **USDC Launches Still Need SOL**
>
> Pumpfun USDC uses USDC for launch buys and optional USDC holder or injection funding. Launch wallets still need SOL for network fees, lookup-table preparation when required, token cleanup reserves, and Jito tips.

## Launch Flow

The PumpFun launch wizard has six steps.

### 1. Info

Enter the token and profile details, then choose the launch method.

| Field                    | Required | Description                                                                                                                              |
| ------------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Choose **Pumpfun SOL** or **Pumpfun USDC**. The launchpad is locked after the draft is saved; create a new draft to switch quote assets. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                                                                             |
| **Token Name**           | Yes      | Public token name                                                                                                                        |
| **Ticker**               | Yes      | Token symbol, auto-uppercased                                                                                                            |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                                                                             |
| **Description**          | No       | Public token description                                                                                                                 |
| **X, Telegram, Website** | No       | Public social links included with the PumpFun metadata                                                                                   |

### Pumpfun SOL vs Pumpfun USDC

| Launch method    | Quote asset | Use when                                              | Notes                                                                                                                   |
| ---------------- | ----------- | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Pumpfun SOL**  | SOL / WSOL  | You want the standard SOL-quoted PumpFun launch path. | Launch buys, holder funding, injection wallets, and fee reserves are SOL-based.                                         |
| **Pumpfun USDC** | USDC        | You want the launch market quoted in USDC.            | Launch buys are USDC-based. Sumo also tracks the SOL required for fees, Jito tips, lookup tables, and cleanup reserves. |

> **No Manual Vanity Mining**
>
> You do not need to mine or select a vanity address manually. When you save the launch draft, Sumo automatically reserves the launch mint and stores it on the draft. The final launch uses that saved mint.

### 2. Buy Mode

Choose how the launch should acquire supply.

| Mode               | Description                                                                                                                                                   |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Bundle**         | Creates the token and executes launch buys from the dev and bundle wallets. This is capped by the PumpFun bonding curve limit of about 79.31% supply control. |
| **Bundle + Snipe** | Uses bundle buys to reach migration, then adds post-migration PumpSwap sniper buys. Use this when you need supply control beyond the bonding curve cap.       |

Configure the buy plan:

| Setting                                | Description                                                                                                                                                                                                                                                                                                               |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**              | Total supply percentage controlled by launch wallets. Bundle mode is capped at 79.31%; Bundle + Snipe starts at that migration target and can go higher through sniper buys.                                                                                                                                              |
| **Dev Buy**                            | Supply percentage assigned to the dev wallet.                                                                                                                                                                                                                                                                             |
| **Bundle Buy**                         | Read-only allocation derived from target supply minus the dev buy.                                                                                                                                                                                                                                                        |
| **Sniper Buy**                         | Read-only post-migration allocation shown only for Bundle + Snipe.                                                                                                                                                                                                                                                        |
| **Bundle Wallets**                     | Number of bundle buyer wallets. Pumpfun SOL supports up to 15 in Bundle mode and 9 in Bundle + Snipe. Pumpfun USDC supports up to 12 in Bundle mode and 6 in Bundle + Snipe.                                                                                                                                              |
| **Sniper Wallets**                     | Number of post-migration sniper wallets, shown only for Bundle + Snipe.                                                                                                                                                                                                                                                   |
| **Holder Wallets**                     | Wallets funded for post-launch holder distribution.                                                                                                                                                                                                                                                                       |
| **Injection Wallets**                  | Optional wallets funded alongside launch wallets for later injection activity. Pumpfun SOL funds them with SOL; Pumpfun USDC can fund them with SOL and optional USDC.                                                                                                                                                    |
| **Trader Cashback**                    | Optional PumpFun feature that redirects eligible creator fees to traders based on swap volume. Available for Pumpfun SOL and Pumpfun USDC in both launch modes; traders claim accrued cashback separately. The choice locks after the initial draft save, and cashback Bundle + Snipe launches support one sniper wallet. |
| **Funds Per Holder Wallet**            | SOL sent to each holder wallet during cleanup/funding.                                                                                                                                                                                                                                                                    |
| **Token Cleanup Method**               | Token Transfer or Sell / Buy. New drafts default to Sell / Buy, redistributing through buys and sells in a Sender Max bundle (small tip reserve). Pick Token Transfer for plain token transfers.                                                                                                                          |
| **USDC Funds Per Holder Wallet**       | USDC sent to each holder wallet during cleanup/funding, shown only for Pumpfun USDC.                                                                                                                                                                                                                                      |
| **Funds Per Injection Wallet**         | SOL sent to each injection wallet when injection wallets are enabled.                                                                                                                                                                                                                                                     |
| **USDC Funds Per Injection Wallet**    | USDC sent to each injection wallet, shown only for Pumpfun USDC when injection wallets are enabled.                                                                                                                                                                                                                       |
| **CEX Funding**                        | Funds launch wallets through Husher. This adds the provider fee to the funding estimate.                                                                                                                                                                                                                                  |
| **CEX Funding Buffer Per Wallet**      | Extra SOL sent per wallet when CEX funding is enabled.                                                                                                                                                                                                                                                                    |
| **CEX USDC Funding Buffer Per Wallet** | Extra USDC added per wallet for Pumpfun USDC CEX funding. The current minimum is 2 USDC per wallet.                                                                                                                                                                                                                       |
| **Advanced Controls**                  | Slippage, bundle supply jitter, holder supply jitter, and Jito tip.                                                                                                                                                                                                                                                       |

> **Bundle Limit**
>
> Pumpfun USDC uses lower bundle-wallet limits than Pumpfun SOL because USDC v2 transactions carry different account and packet-size constraints. If a launch needs many buyer wallets, Sumo prepares a lookup table before submitting the final bundle.

For Pumpfun USDC, the Buy Mode estimate shows both:

* **Estimated SOL required** - Native SOL required for fees, Jito tip, lookup table budget, token cleanup reserves, and SOL funding rows.
* **Estimated USDC required** - USDC required for launch buys plus optional USDC holder or injection funding.

### 3. Wallets

Add, import, or generate wallets for each launch role.

| Role                  | Description                                                         |
| --------------------- | ------------------------------------------------------------------- |
| **Dev Wallet**        | Single deployer wallet used for the launch transaction and dev buy. |
| **Bundle Wallets**    | Wallets used for bundled launch buys before the token is live.      |
| **Sniper Wallets**    | Bundle + Snipe wallets used for PumpSwap buys after migration.      |
| **Holder Wallets**    | Wallets used for post-launch holder distribution.                   |
| **Injection Wallets** | Optional wallets funded for later injection activity.               |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace). After saving the draft, Sumo creates the launch wallet groups and persists the selected wallets to the pre-launch profile.

### 4. Funding

Save the launch draft before funding. Saving the draft creates the pre-launch profile, role wallet groups, funding wallet when CEX funding is enabled, and the automatic launch mint.

If CEX funding is enabled for Pumpfun SOL, deposit the estimated SOL into the funding wallet, check the balance, then use **Fund** to distribute SOL through Husher to the launch wallets.

If CEX funding is enabled for Pumpfun USDC, deposit both the estimated SOL and USDC into the funding wallet. Use **Fund** to distribute SOL requirements and **Fund USDC** to distribute USDC requirements. The funding table marks a wallet complete only after it has enough of every required asset.

If CEX funding is disabled, fund the launch wallets directly and use **Check Balances** before continuing.

The funding table lets you:

* Copy role wallet addresses
* Randomize token buy allocations
* Edit per-wallet token buy percentages
* Reorder wallets within the same role
* Check SOL balances for Pumpfun SOL, or SOL and USDC balances for Pumpfun USDC
* Fund launch, holder, and injection wallets through the funding wallet when CEX funding is enabled

Every launch wallet must have the required balances before the final launch can be submitted. Pumpfun USDC launch wallets need enough USDC for their assigned buy amount and enough SOL for execution costs.

### 5. Strategies

Optionally add starter strategies to the profile before launch. These strategies are saved with the draft so you can review and activate them after the token is live.

You can configure strategies by hand or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Each preset shows a projected hourly volume estimate before you apply it.

Common starter strategies include:

* [Counter Trade](/strategies/counter-trade) for reactive market support
* [Limit Order](/strategies/limit-orders) for fixed buy or sell levels
* [DCA](/strategies/dca) for scheduled accumulation or distribution

### 6. Launch Preview

Review the final composition before submitting:

* Token metadata and saved launch mint
* Dev, bundle, sniper, holder, and injection wallet counts
* Supply control split across dev, bundle, and sniper buys
* Funding rows and buy allocations
* Starter strategies

Click **Launch** when the preview is correct and all required wallets are funded. If the bundle needs a lookup table, Sumo prepares it automatically before submitting the launch transaction. Pumpfun USDC launches always use the v2 PumpFun instruction path.

## After Launch

Once your token is live on PumpFun or migrated to PumpSwap, the pre-launch profile transitions to an active trading profile. You can then:

* Monitor trades on the [Live Trading](/reporting/live-trading) feed
* Review and activate any starter strategies
* Use [Counter Trade](/strategies/counter-trade) to react to external trades and support price action
* Add more wallets from [Wallet Farm](/wallet-farm/overview)
* Use [DCA](/strategies/dca) or [Limit Order](/strategies/limit-orders) strategies to continue managing inventory
* Claim creator fees when they are available
* Change the creator-fee recipients when the current creator is managed by Sumo

## Creator Fee Claims

PumpFun profiles can expose a **Claim creator fees** action in the profile wallet toolbar when the profile has a creator wallet eligible for fee collection. Use it to submit a creator fee claim from Sumo without leaving the profile workspace.

Creator fee claim results appear in Treasury Logs as **Creator Fee Claim** entries, including the transaction details when the claim is submitted on-chain.

## Changing the Creator

Organization admins can use **Change creator** to permanently route future Pump creator fees to one wallet or split them between multiple wallets. This changes the creator attribution used for fees; it does not transfer the token mint authority or profile ownership.

The action supports existing and newly launched Pumpfun SOL and Pumpfun USDC coins while they are on the PumpFun bonding curve, and PumpSwap coins after graduation. For PumpSwap, Sumo updates both the historical PumpFun creator record and the PumpSwap pool creator in the same transaction.

To change the creator:

1. Open the profile's **Wallets** tab and open the wallet actions menu
2. Select **Change creator**
3. Add between 1 and 10 unique Solana recipient addresses
4. Assign a positive percentage to every recipient so the total is exactly 100%
5. Review the final split and confirm the transaction

A single replacement wallet should receive 100%. For a shared arrangement, every future creator-fee payment follows the finalized percentage split.

> **Creator Changes Are Permanent**
>
> Pump's fee-sharing program revokes its admin after the split is finalized. The recipients and percentages cannot be changed again, so verify every address and the complete 100% allocation before confirming.

The current on-chain creator wallet must be managed by the profile so Sumo can authorize the transaction. If it is not managed, import its private key before continuing. A graduated coin must also be routed to PumpSwap with its canonical pool address recorded on the profile; refresh the profile's migration routing before changing the creator if it still points to a completed PumpFun curve.

After submission, the transaction appears in [Treasury Logs](/reporting/treasury-logs) as **Change Creator**. Once it confirms, Sumo refreshes the affected PumpFun and PumpSwap pool caches used for trading.

## Trader Cashback Claims

When a launch enabled **Trader Cashback**, eligible creator fees accrue to trading wallets based on their swap volume. The profile wallet toolbar exposes a **Claim cashback** action that claims across wallets in one batch:

1. Open the profile's **Wallets** tab and click **Claim cashback** from the wallet actions menu
2. Select the wallets to include — individual wallets, wallet groups, or all wallets
3. Review the live preview of claimable SOL and USDC per wallet
4. Confirm to queue the batch — one notification arrives when the batch finishes

Wallets with nothing claimable are skipped automatically.

## Launch Logs

Launch profiles also add a **Launch Logs** tab to the Logs workspace. Use it to review launch-specific activity such as token creation, bundle launch submission, bundle confirmation, and related launch transactions.

Launch Logs are shown only when the profile has launch metadata. The tab sits alongside Trade Logs, Treasury Logs, and Audit Logs so launch activity can be reviewed without mixing it into normal trading history.

- [Counter Trade](/strategies/counter-trade): Automatically counter external trades to maintain price stability.

- [Strategies Overview](/strategies/overview): Learn about all available trading strategies.

## Further Reading

* [Which Memecoin Bundling Tool Is the Best on Solana](https://blog.sumo.trade/which-memecoin-bundling-tool-is-the-best-on-solana/) — what a bundle is, why teams bundle, and how Sumo compares to the alternatives
* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — PumpFun's virtual reserves and graduation math, side by side with other launchpads
* [How to Launch a Memecoin in 2026](https://blog.sumo.trade/how-to-launch-a-memecoin/) — the end-to-end launch playbook


---

# Meteora DAMM v2 Solana Launch

> Launch a Solana token on Meteora DAMM v2 with SOL or USDC liquidity, freeze bundle controls, injection wallets, liquidity locking, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/meteora-dammv2-launch
- Markdown: https://docs.sumo.trade/launch-tokens/meteora-dammv2-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Solana launches through **Meteora DAMM v2**. The wizard supports both **Meteora DAMM v2 SOL** and **Meteora DAMM v2 USDC**. Both paths create a new token mint, create the DAMM v2 pool, run bundle-wallet buys while freeze controls are active, optionally lock liquidity, and then transition the launch draft into an active trading profile.

> **Video: Meteora Freeze Bundle Launch (Live Example)**
>
> A live example of configuring and running a Meteora DAMM v2 freeze-bundle launch from Sumo.
>
> https://www.youtube.com/watch?v=li0qfiQiqVM

![Meteora DAMM v2 token launch buy setup](/images/meteora-dammv2-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. A SOL funding source for network fees, priority fees, and SOL-quoted launches
3. USDC when using **Meteora DAMM v2 USDC**
4. A launch plan: initial liquidity, initial token liquidity percentage, bundle wallet count, and optional injection wallets
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Solana wallets / buy aged Solana wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **SOL and USDC Variants**
>
> Meteora DAMM v2 SOL uses WSOL as the quote side. Meteora DAMM v2 USDC uses USDC for liquidity and launch buys, while still requiring SOL for transaction fees and priority fees.

## Launch Flow

### 1. Info

Enter the token and profile details, then choose the launch method.

| Field                    | Required | Description                                                                                                   |
| ------------------------ | -------- | ------------------------------------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Choose **Meteora DAMM v2 SOL** or **Meteora DAMM v2 USDC**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                                                  |
| **Token Name**           | Yes      | Public token name                                                                                             |
| **Ticker**               | Yes      | Token symbol, auto-uppercased                                                                                 |
| **Total Supply**         | Yes      | SPL token total supply before decimals. Maximum 1T; defaults to 1,000,000,000.                                |
| **Decimals**             | Yes      | Meteora launches support 0 to 9 decimals; defaults to 6.                                                      |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                                                  |
| **Description**          | No       | Public token description                                                                                      |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                                                   |

### 2. Buy Mode

Meteora DAMM v2 supports two launch modes:

| Mode              | Description                                                                                       |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| **Freeze Bundle** | Creates the pool and runs bundle-wallet buys while freeze controls protect the launch sequence.   |
| **Simple Pool**   | Dev-only launch: creates the pool with initial liquidity and no bundle buys or injection wallets. |

| Setting                             | Description                                                                                          |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Initial Liquidity SOL / USDC**    | Quote asset supplied by the dev wallet when the pool is created.                                     |
| **Pool Fees**                       | Meteora DAMM v2 fee configuration selected for the pool: 0.25% (default), 1%, 2%, 4%, or 6%.         |
| **Initial Token Liquidity**         | Percentage of token supply paired into the pool.                                                     |
| **Bundle Wallets**                  | Number of bundle wallets used for launch buys. Meteora supports up to 200 bundle wallets.            |
| **Funds Per Bundle Wallet**         | Native SOL reserved per bundle wallet. For USDC launches, this is separate from USDC buy allocation. |
| **USDC Funds Per Bundle Wallet**    | Extra USDC top-up per bundle wallet, shown for the USDC variant.                                     |
| **Injection Wallets**               | Optional wallets funded for later injection activity. They do not participate in the launch bundle.  |
| **Funds Per Injection Wallet**      | SOL top-up for each injection wallet.                                                                |
| **USDC Funds Per Injection Wallet** | Optional USDC top-up for each injection wallet, shown for the USDC variant.                          |
| **Lock Liquidity**                  | Locks the Meteora LP position after trading opens and launch transactions complete.                  |
| **Advanced Controls**               | Priority fee, bundle supply jitter, delay per bundle transaction, and the launch mint address type.  |

> **Vanity Mint Address**
>
> In Advanced Controls, the **Address Type** setting can mine a vanity launch mint: choose **Random** (default), **Vanity Address: Starts With**, or **Vanity Address: Ends With**, then enter up to 4 case-sensitive base58 characters.

> **Injection Wallets**
>
> Injection wallets are funding targets for later activity. They are not bundle buyers and do not receive launch-token allocation during the initial bundle.

### 3. Wallets

Add, import, or generate wallets for each required Solana role.

| Role                  | Description                                                                                                         |
| --------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Creates the mint, creates the pool, supplies initial liquidity, and pays launch setup costs.                        |
| **Freeze Wallet**     | Controls freeze/thaw operations during the freeze-bundle flow and signs final freeze-authority revoke transactions. |
| **Bundle Wallets**    | Execute launch buys while freeze controls protect the launch sequence.                                              |
| **Injection Wallets** | Optional wallets funded for later injection activity.                                                               |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

### 4. Funding

Save the launch draft before funding. Saving creates the pre-launch profile, role wallet groups, token mint details, and launch settings.

For SOL launches, the funding table tracks SOL requirements for setup, liquidity, bundle wallets, priority fees, and optional injection wallets.

For USDC launches, the funding table tracks both SOL and USDC requirements. USDC covers liquidity, buy allocations, and optional USDC top-ups. SOL covers transaction fees, priority fees, setup transactions, and optional native top-ups.

If CEX funding is enabled, deposit the estimated assets into the funding wallet and use the funding actions to distribute them. If CEX funding is disabled, fund the launch wallets directly and use **Check Balances** before launch.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

Review the final launch composition before submitting:

* Token metadata and mint
* Pool fee and initial liquidity
* Dev, freeze, bundle, and injection wallet counts
* Bundle allocation and funding rows
* Liquidity-lock setting
* Starter strategies

The preview sequence creates the pool, submits bundle buys, finalizes freeze state, optionally locks liquidity, and activates the trading profile.

## After Launch

After the Meteora pool is live, the profile opens in Live Trading. You can monitor trades, review launch logs, run starter strategies, manage wallets, and use the Meteora profile actions that are available for the launched pool.

## Launch Logs

Meteora launch profiles add a **Launch Logs** tab to the Logs workspace. Use it to review pool creation, bundle execution, freeze/finalize actions, liquidity-lock actions, and related launch transactions.


---

# BONK.fun Solana Launch

> Launch a Solana token through BONK.fun and Raydium LaunchLab with bundled WSOL buys, a configurable graduation target, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/bonkfun-launch
- Markdown: https://docs.sumo.trade/launch-tokens/bonkfun-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **BONK.fun** launches on Solana. The flow creates the BONK.fun token on Raydium LaunchLab with WSOL quote, submits the create-pool transaction with bundled exact-in WSOL buys, and transitions the draft into an active trading profile.

![BONK.fun token launch buy setup](/images/bonkfun-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. SOL for dev buy, bundle buys, transaction fees, Jito tip, and optional holder or injection top-ups
3. A launch plan: supply target, dev buy, graduation target, bundle wallet count, holder count, and optional injection wallets
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Solana wallets / buy aged Solana wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Fixed Token Parameters**
>
> BONK.fun launch tokens use a fixed supply of 1 billion tokens with 6 decimals and WSOL as the quote asset. Total supply and decimals are not edited in the standard Sumo flow.

## Launch Flow

### 1. Info

Choose **BONK.fun** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                            |
| ------------------------ | -------- | ---------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **BONK.fun**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                           |
| **Token Name**           | Yes      | Public token name                                                      |
| **Ticker**               | Yes      | Token symbol, auto-uppercased                                          |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                           |
| **Description**          | No       | Public token description                                               |
| **X, Telegram, Website** | No       | Public social links included with the BONK.fun metadata                |

### 2. Buy Mode

BONK.fun supports normal bundled launches with SOL buys.

| Setting                        | Description                                                                                                                                                                                      |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Supply Control Target**      | Total supply controlled by dev and bundle wallets. BONK.fun is capped at 79.31%.                                                                                                                 |
| **Dev Buy**                    | SOL buy assigned to the dev wallet.                                                                                                                                                              |
| **Bundle Buy**                 | Allocation assigned across bundle wallets.                                                                                                                                                       |
| **Graduation Target**          | SOL raise target at which the LaunchLab curve graduates. Range 1 to 1,000 SOL; default 85 SOL.                                                                                                   |
| **Bundle Wallets**             | Number of LaunchLab bundle buyers. BONK.fun supports up to 12 bundle wallets.                                                                                                                    |
| **Holder Wallets**             | Wallets funded through token cleanup after launch.                                                                                                                                               |
| **Token Cleanup Method**       | Token Transfer or Sell / Buy. New drafts default to Sell / Buy, redistributing through buys and sells in a Sender Max bundle (small tip reserve). Pick Token Transfer for plain token transfers. |
| **Injection Wallets**          | Optional wallets funded for later activity.                                                                                                                                                      |
| **Funds Per Holder Wallet**    | SOL top-up delivered through cleanup source wallets.                                                                                                                                             |
| **Funds Per Injection Wallet** | Optional SOL top-up for injection wallets.                                                                                                                                                       |
| **CEX Funding**                | Optional Husher funding path for distributing SOL.                                                                                                                                               |
| **Advanced Controls**          | Category, slippage, bundle supply jitter, holder supply jitter, and Jito tip.                                                                                                                    |

The **Category** control selects the BONK.fun platform configuration:

| Category    | Description                                           |
| ----------- | ----------------------------------------------------- |
| **Classic** | Default. No creator curve fee; 1.50% total curve fee. |
| **BONKers** | Includes a 0.05% creator fee; 1.30% total curve fee.  |

### 3. Wallets

Add, import, or generate wallets for each launch role.

| Role                  | Description                                                    |
| --------------------- | -------------------------------------------------------------- |
| **Dev Wallet**        | Creates the token, pays setup costs, and performs the dev buy. |
| **Bundle Wallets**    | Execute bundled Raydium LaunchLab buys.                        |
| **Holder Wallets**    | Receive post-launch holder distribution through cleanup.       |
| **Injection Wallets** | Optional wallets funded for later injection activity.          |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Sniper wallets are not used in the BONK.fun launch flow exposed by Sumo.

### 4. Funding

Save the draft before funding. The funding table tracks SOL requirements for dev and bundle buys, transaction fees, Jito tip, holder cleanup reserves, and optional injection wallets.

If CEX funding is enabled, deposit the estimated SOL into the funding wallet and use **Fund** to distribute it through Husher. If CEX funding is disabled, fund the launch wallets directly and use **Check Balances**.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

Review:

* BONK.fun metadata and saved launch identifiers
* Category and graduation target
* Dev, bundle, holder, and injection wallet counts
* SOL funding rows
* Supply split across dev and bundle buys

When launched, Sumo prepares the launch bundle, simulates it, then submits the Raydium LaunchLab create-pool transaction with the bundled buys.

## After Launch

The launched profile opens in Live Trading. You can monitor Raydium LaunchLab trades, activate starter strategies, run token cleanup, and use normal wallet and treasury tooling.

## Launch Logs

BONK.fun profiles add a **Launch Logs** tab for metadata preparation, bundle simulation, bundle launch, and related launch transactions.

## Further Reading

* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — this launchpad's curve overlaid on every other supported launchpad, with graduation math
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — simulate launch cost, starting market cap, and supply held for this launchpad


---

# America.Fun Solana Launch

> Launch a Solana Token-2022 project through America.Fun with USD1 buys, Meteora DBC migration support, holder cleanup, injection wallets, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/americafun-launch
- Markdown: https://docs.sumo.trade/launch-tokens/americafun-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **America.Fun** launches on Solana. The launch path uses USD1 as the quote asset, creates a Token-2022 launch mint, initializes a Meteora DBC market through America.Fun, and can optionally continue into a migration bundle with DAMM v2 sniper buys.

![America.Fun token launch buy setup](/images/americafun-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. USD1 for the dev initial buy, bundle buys, and optional holder or injection top-ups
3. SOL for transaction fees, Jito tips, ATA creation, and migration-related rent or fees
4. A launch plan: supply target, bundle wallet count, holder count, and optional migration sniper count
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Solana wallets / buy aged Solana wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **USD1 Quote**
>
> America.Fun launches use USD1 for launch buys. Launch wallets still need SOL for transaction costs and setup.

## Launch Flow

### 1. Info

Choose **America.Fun** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                               |
| ------------------------ | -------- | ------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **America.Fun**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                              |
| **Token Name**           | Yes      | Public token name                                                         |
| **Ticker**               | Yes      | Token symbol, auto-uppercased                                             |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                              |
| **Description**          | No       | Public token description                                                  |
| **X, Telegram, Website** | No       | Public social links included with the launch metadata                     |

### 2. Buy Mode

America.Fun supports the same high-level supply planning model as other Solana launch flows, but uses USD1 for launch buys.

| Setting                             | Description                                                                                                                                                                                      |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Mode**                            | Bundle launches on the DBC market. Bundle + Snipe adds a migration step and DAMM v2 sniper buys.                                                                                                 |
| **Supply Control Target**           | Total supply percentage controlled by dev, bundle, and optional sniper wallets. America.Fun is capped at 80%.                                                                                    |
| **Dev Buy**                         | Initial USD1 buy included in the America.Fun pool-initialize transaction.                                                                                                                        |
| **Bundle Buy**                      | Allocation assigned across DBC bundle wallets.                                                                                                                                                   |
| **Sniper Buy**                      | Post-migration DAMM v2 allocation, shown only for Bundle + Snipe.                                                                                                                                |
| **Bundle Wallets**                  | Normal bundle mode supports up to 16 bundle wallets. Migration mode supports up to 8 DBC bundle wallets.                                                                                         |
| **Sniper Wallets**                  | Bundle + Snipe supports up to 2 migration sniper wallets.                                                                                                                                        |
| **Holder Wallets**                  | Wallets funded through token cleanup after launch.                                                                                                                                               |
| **Token Cleanup Method**            | Token Transfer or Sell / Buy. New drafts default to Sell / Buy, redistributing through buys and sells in a Sender Max bundle (small tip reserve). Pick Token Transfer for plain token transfers. |
| **Injection Wallets**               | Optional wallets funded for later activity.                                                                                                                                                      |
| **Funds Per Holder Wallet**         | SOL top-up delivered through cleanup source wallets.                                                                                                                                             |
| **USD1 Funds Per Holder Wallet**    | USD1 top-up delivered through cleanup source wallets.                                                                                                                                            |
| **Funds Per Injection Wallet**      | SOL top-up for injection wallets.                                                                                                                                                                |
| **USD1 Funds Per Injection Wallet** | Optional USD1 top-up for injection wallets.                                                                                                                                                      |
| **CEX Funding**                     | Optional Husher funding path for distributing SOL and USD1.                                                                                                                                      |
| **Advanced Controls**               | Slippage, supply jitter, holder jitter, and Jito tip.                                                                                                                                            |

> **Migration Capacity**
>
> Bundle + Snipe uses tighter transaction packing than normal bundle mode. If you need migration and sniper buys, keep the wallet counts within the America.Fun migration limits shown in the wizard.

### 3. Wallets

Add, import, or generate wallets for each launch role.

| Role                  | Description                                                              |
| --------------------- | ------------------------------------------------------------------------ |
| **Dev Wallet**        | Creates the launch, pays setup costs, and performs the initial USD1 buy. |
| **Bundle Wallets**    | Buy on the Meteora DBC market during the launch bundle.                  |
| **Sniper Wallets**    | Bundle + Snipe wallets that buy after migration on DAMM v2.              |
| **Holder Wallets**    | Receive post-launch holder distribution through cleanup.                 |
| **Injection Wallets** | Optional wallets funded for later injection activity.                    |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

### 4. Funding

Save the draft before funding. The funding table tracks both SOL and USD1 requirements.

USD1 covers dev and bundle buys plus optional USD1 holder or injection top-ups. SOL covers transaction fees, Jito tips, ATA creation, migration costs, and optional SOL holder or injection top-ups.

If CEX funding is enabled, deposit the required SOL and USD1 into the funding wallet and use the funding actions to distribute them. If CEX funding is disabled, fund the launch wallets directly and use **Check Balances**.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview shows:

* Token metadata and America.Fun metadata status
* Dev, bundle, holder, injection, and sniper wallet counts
* USD1 and SOL funding rows
* Supply split across dev, bundle, and optional sniper buys
* Whether migration and DAMM v2 sniper buys are part of the launch

When launched, Sumo submits setup transactions as needed, then submits the Jito bundle that initializes the DBC market and executes launch buys.

## After Launch

The profile opens in Live Trading after the launch completes. America.Fun projects can also expose creator-fee claim actions when claimable amounts are available.

## Launch Logs

America.Fun profiles add a **Launch Logs** tab for launch setup, DBC bundle submission, migration activity, and related launch transactions.

## Further Reading

* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — this launchpad's curve overlaid on every other supported launchpad, with graduation math
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — simulate launch cost, starting market cap, and supply held for this launchpad


---

# Memoo Solana Launch

> Launch a Solana token through Memoo and Raydium LaunchLab with SOL buys, funding tiers, bundle wallets, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/memoo-launch
- Markdown: https://docs.sumo.trade/launch-tokens/memoo-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Memoo** launches on Solana. The flow creates and saves Memoo metadata, uses Raydium LaunchLab with WSOL quote, prepares any required lookup table, submits bundled launch buys, and transitions the draft into an active trading profile.

![Memoo token launch buy setup](/images/memoo-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. SOL for dev buy, bundle buys, transaction fees, Jito tip, and optional holder or injection top-ups
3. A funding tier selection for the Raydium LaunchLab configuration
4. A launch plan: supply target, dev buy, bundle wallet count, holder count, and optional injection wallets
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Solana wallets / buy aged Solana wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

## Launch Flow

### 1. Info

Choose **Memoo** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                         |
| ------------------------ | -------- | ------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Memoo**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                        |
| **Token Name**           | Yes      | Public token name                                                   |
| **Ticker**               | Yes      | Token symbol, auto-uppercased                                       |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                        |
| **Description**          | No       | Public token description                                            |
| **X, Telegram, Website** | No       | Public social links included with the Memoo metadata                |

Memoo uses fixed launch-token supply settings in the standard Sumo launch flow.

### 2. Buy Mode

Memoo supports normal bundled launches with SOL buys.

| Setting                        | Description                                                                                                                                                                                      |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Supply Control Target**      | Total supply controlled by dev and bundle wallets. Memoo is capped at 78%.                                                                                                                       |
| **Dev Buy**                    | SOL buy assigned to the dev wallet.                                                                                                                                                              |
| **Bundle Buy**                 | Allocation assigned across bundle wallets.                                                                                                                                                       |
| **Funding Tier**               | LaunchLab migration funding target. Low, medium, and high correspond to larger SOL migration targets.                                                                                            |
| **Bundle Wallets**             | Number of LaunchLab bundle buyers. Memoo supports up to 12 bundle wallets.                                                                                                                       |
| **Holder Wallets**             | Wallets funded through token cleanup after launch.                                                                                                                                               |
| **Injection Wallets**          | Optional wallets funded for later activity.                                                                                                                                                      |
| **Funds Per Holder Wallet**    | SOL top-up delivered through cleanup source wallets.                                                                                                                                             |
| **Funds Per Injection Wallet** | Optional SOL top-up for injection wallets.                                                                                                                                                       |
| **Token Cleanup Method**       | Token Transfer or Sell / Buy. New drafts default to Sell / Buy, redistributing through buys and sells in a Sender Max bundle (small tip reserve). Pick Token Transfer for plain token transfers. |
| **CEX Funding**                | Optional Husher funding path for distributing SOL.                                                                                                                                               |
| **Advanced Controls**          | Slippage, bundle supply jitter, holder supply jitter, and Jito tip.                                                                                                                              |

> **Lookup Table Preparation**
>
> Memoo can prepare a launch-specific lookup table when wallet counts require it. The wizard stores the prepared lookup table on the draft and reuses it for simulation and launch.

### 3. Wallets

Add, import, or generate wallets for each launch role.

| Role                  | Description                                                                                    |
| --------------------- | ---------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Authenticates with Memoo, creates launch metadata, pays setup costs, and performs the dev buy. |
| **Bundle Wallets**    | Execute bundled Raydium LaunchLab buys.                                                        |
| **Holder Wallets**    | Receive post-launch holder distribution through cleanup.                                       |
| **Injection Wallets** | Optional wallets funded for later injection activity.                                          |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Sniper wallets are not used in the Memoo launch flow exposed by Sumo.

### 4. Funding

Save the draft before funding. The funding table tracks SOL requirements for dev and bundle buys, transaction fees, Jito tip, optional lookup-table preparation, holder cleanup reserves, and optional injection wallets.

If CEX funding is enabled, deposit the estimated SOL into the funding wallet and use **Fund** to distribute it through Husher. If CEX funding is disabled, fund the launch wallets directly and use **Check Balances**.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

Review:

* Memoo metadata and saved launch identifiers
* Funding tier
* Dev, bundle, holder, and injection wallet counts
* SOL funding rows
* Supply split across dev and bundle buys
* Prepared lookup table status when required

When launched, Sumo uses Memoo's signing flow for token creation, builds the Raydium LaunchLab bundle, and submits the launch transaction sequence.

## After Launch

The launched profile opens in Live Trading. You can monitor Raydium LaunchLab trades, activate starter strategies, run token cleanup, and use normal wallet and treasury tooling.

## Launch Logs

Memoo profiles add a **Launch Logs** tab for metadata preparation, lookup-table preparation, bundle launch, and related launch transactions.


---

# Uniswap V2 Ethereum Launch

> Launch an ERC-20 token on Uniswap V2 Ethereum with WETH liquidity, private bundle buys, tax controls, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/uniswap-eth-launch
- Markdown: https://docs.sumo.trade/launch-tokens/uniswap-eth-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Ethereum launches through **Uniswap V2 Ethereum**. The flow creates an ERC-20 launch token, prepares a WETH pair, opens trading with initial liquidity, executes private bundle buys, and transitions the pre-launch draft into an active trading profile.

![Uniswap V2 Ethereum token launch buy setup](/images/uniswap-eth-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. ETH for contract deployment, pool creation, initial liquidity, bundle buys, and gas buffers
4. A launch plan: target supply control, pool-token percentage, bundle wallet count, and optional tax settings
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new EVM wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **WETH Quote Asset**
>
> Uniswap V2 Ethereum launches are WETH-quoted. In the form, operators enter ETH amounts; Sumo stores the profile quote asset as WETH after pool creation.

## Launch Flow

The Uniswap V2 Ethereum launch uses the same six-step launch wizard as other launch methods.

### 1. Info

Choose **Uniswap V2 Ethereum** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                       |
| ------------------------ | -------- | --------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Uniswap V2 Ethereum**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                      |
| **Token Name**           | Yes      | ERC-20 token name                                                                 |
| **Ticker**               | Yes      | ERC-20 token symbol, auto-uppercased                                              |
| **Total Supply**         | Yes      | ERC-20 total supply before decimals                                               |
| **Decimals**             | Yes      | ERC-20 display decimals, commonly 18                                              |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                      |
| **Description**          | No       | Public token description                                                          |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                       |

### 2. Buy Mode

Configure liquidity, supply control, wallet counts, and optional token controls.

| Setting                            | Description                                                                                                                                                                                   |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**          | Total supply controlled by dev-retained supply plus bundle wallet buys. Range: 1% to 99.99%.                                                                                                  |
| **Initial Liquidity ETH**          | ETH supplied by the dev wallet when opening trading.                                                                                                                                          |
| **Initial Liquidity Tokens**       | Percentage of total supply supplied to the pool. The remainder stays with the dev wallet.                                                                                                     |
| **Estimated ETH Required**         | Estimated initial liquidity, bundle buys, gas buffers, and CEX funding buffers when enabled.                                                                                                  |
| **Estimated Market Cap**           | Estimated from Uniswap V2 reserves after bundle buys, using the ETH/USD reference price.                                                                                                      |
| **Dev Supply**                     | Read-only value derived from total supply minus pool-token percentage.                                                                                                                        |
| **Bundle Buy**                     | Read-only value derived from supply-control target minus dev-retained supply.                                                                                                                 |
| **Bundle Wallets**                 | Number of EVM wallets buying in the private launch bundle. Uniswap V2 Ethereum supports up to 48.                                                                                             |
| **Funds Per Bundle Wallet**        | ETH reserved per bundle wallet for gas. Minimum 0.01 ETH.                                                                                                                                     |
| **Injection Wallets**              | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                          |
| **Funds Per Injection Wallet**     | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                     |
| **Token Cleanup Method**           | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to holder wallets and sweeps residual native balances after the launch buys confirm. New drafts default to Sell / Buy. |
| **Holder Wallets**                 | Shown when token cleanup is not Off. Use at least one holder per bundle wallet and no more than 100 holders per bundle wallet.                                                                |
| **Native Funds Per Holder Wallet** | Shown with Sell / Buy. ETH sent to each holder wallet during funding for its cleanup buy, seeded at 0.01 ETH. Each holder must hold at least 0.002 ETH before the launch is accepted.         |
| **CEX Funding**                    | Optional Husher funding path for distributing ETH to launch wallets.                                                                                                                          |
| **CEX Funding Buffer Per Wallet**  | Extra ETH added per wallet when CEX funding is enabled. Minimum 0.01 ETH.                                                                                                                     |
| **Advanced Controls**              | Slippage, bundle supply jitter, and bundle priority fee in gwei.                                                                                                                              |

### Tax Controls

Tax Controls are optional and disabled by default. When disabled, the token deploys from the no-tax contract template. When enabled, the launch token is deployed with tax, wallet-limit, and tax-clog settings.

| Setting                                | Description                                                                                             |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Initial Buy Tax / Initial Sell Tax** | Taxes applied during the initial tax period after the launch bundle finalizes launch taxes.             |
| **Final Buy Tax / Final Sell Tax**     | Taxes applied after the tax switchover block window.                                                    |
| **Tax Switchover Blocks**              | Number of blocks before final taxes replace initial taxes.                                              |
| **Max Supply Per Wallet Limit**        | Optional maximum token balance per non-excluded wallet, as a percentage of total supply.                |
| **Tax Clog**                           | When enabled, tax tokens accumulate on the token contract and can be swapped to ETH for the tax wallet. |
| **Max Tax Swap Amount**                | Maximum tax-token amount sold in one automatic tax-clog swap.                                           |
| **Min Blocks Between Tax Swaps**       | Cooldown between automatic contract tax-token swaps.                                                    |

### 3. Wallets

Add, import, or generate wallets for each required EVM role.

| Role                  | Description                                                                                                   |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Deploys the token, creates the pool, supplies initial liquidity, opens trading, and receives retained supply. |
| **Tax Wallet**        | Receives tax proceeds and submits later tax or limit updates.                                                 |
| **Bundle Wallets**    | Execute private bundle buys after trading opens.                                                              |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.       |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is not Off.                                     |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Sniper wallets are not used by Uniswap V2 Ethereum launches.

### 4. Funding

Save the draft before funding. Saving creates the pre-launch project, role wallet groups, optional funding wallet, and generated token metadata.

If CEX funding is enabled, deposit the estimated ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH through Husher. If CEX funding is disabled, fund the dev, tax, and bundle wallets directly and use **Check Balances**.

The funding table lets you copy addresses, randomize bundle allocations, edit earlier bundle wallet percentages, reorder wallets within the same role, and verify ETH balances. The dev allocation and final bundle allocation are auto-balanced from the target.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

Review metadata, supply composition, wallet counts, funding rows, and starter strategies.

For Uniswap V2 Ethereum, the preview action sequence is:

1. **Deploy Contract** - Deploys the generated ERC-20 launch token from the dev wallet.
2. **Create Pool** - Creates the token/WETH Uniswap V2 pair.
3. **Simulate Bundle** - Simulates the private launch bundle before submission.
4. **Launch Bundle** - Opens trading with initial liquidity, executes bundle buys, updates the project to active when landed, and submits ownership renounce.

## After Launch

Once the bundle lands, the profile becomes active and opens in Live Trading. You can monitor trades, review launch logs, activate starter strategies, and manage taxes or limits from the supported launch-token controls.


---

# Uniswap Base Launch

> Launch a Base ERC-20 token on Base Uniswap V2 or Uniswap V3 with WETH liquidity, staged launch buys, optional tax controls, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/uniswap-base-launch
- Markdown: https://docs.sumo.trade/launch-tokens/uniswap-base-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Base launches through **Base Uniswap V2** and **Base Uniswap V3**. Both flows deploy a Base ERC-20 launch token, create a WETH pool, add initial liquidity while public trading is still closed, run launch-wallet buys, then open public trading.

The main differences between the two launch methods:

|                  | Base Uniswap V2                             | Base Uniswap V3                                        |
| ---------------- | ------------------------------------------- | ------------------------------------------------------ |
| **Pool type**    | Uniswap V2 pair                             | Uniswap V3 pool with a selectable fee tier             |
| **Liquidity**    | V2 reserves held by the dev wallet          | Full-range V3 position NFT held by the launch contract |
| **Tax controls** | Optional taxes, wallet limits, and tax clog | Not available - V3 launch tokens are tax-free          |

![Base Uniswap V3 token launch buy setup](/images/base-uniswap-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. ETH on Base for deployment, pool setup, initial liquidity, launch buys, and gas buffers
4. A launch plan: target supply control, pool-token percentage, bundle wallet count, and optional tax settings (V2 only)
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Base wallets / buy aged Base wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Base WETH Quote**
>
> Base Uniswap launches use WETH as the quote token. Operators enter ETH amounts in the wizard; Sumo stores WETH quote metadata on the active profile.

## Launch Flow

### 1. Info

Choose **Base Uniswap V2** or **Base Uniswap V3** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                                          |
| ------------------------ | -------- | ---------------------------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Base Uniswap V2** or **Base Uniswap V3**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                                         |
| **Token Name**           | Yes      | ERC-20 token name                                                                                    |
| **Ticker**               | Yes      | ERC-20 token symbol, auto-uppercased                                                                 |
| **Total Supply**         | Yes      | ERC-20 total supply before decimals                                                                  |
| **Decimals**             | Yes      | ERC-20 display decimals, commonly 18                                                                 |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                                         |
| **Description**          | No       | Public token description                                                                             |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                                          |

### 2. Buy Mode

Both Base Uniswap launch methods use the EVM buy setup controls.

| Setting                           | Description                                                                                                                                                 |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**         | Total supply controlled by dev-retained supply plus launch-wallet buys. Range: 1% to 99.99%.                                                                |
| **Initial Liquidity ETH**         | ETH supplied by the dev wallet during pool setup.                                                                                                           |
| **Initial Liquidity Tokens**      | Percentage of total supply supplied to the pool. The remainder stays with the dev wallet.                                                                   |
| **Pool Fee Tier**                 | V3 only. Fee charged by the Uniswap V3 pool on every swap: 0.01%, 0.05%, 0.30% (default), or 1.00%. Initial liquidity always uses the canonical full range. |
| **Estimated ETH Required**        | Estimated initial liquidity, launch buys, gas buffers, and CEX funding buffers when enabled.                                                                |
| **Estimated Market Cap**          | Estimated from pool composition after launch buys, using the ETH/USD reference price.                                                                       |
| **Dev Supply**                    | Read-only value derived from total supply minus pool-token percentage.                                                                                      |
| **Bundle Buy**                    | Read-only value derived from supply-control target minus dev-retained supply.                                                                               |
| **Bundle Wallets**                | Number of Base wallets used for launch buys. Base launch methods support up to 200.                                                                         |
| **Funds Per Bundle Wallet**       | ETH reserved per bundle wallet for gas. Minimum 0.01 ETH.                                                                                                   |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                        |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                   |
| **CEX Funding**                   | Optional Husher funding path for distributing ETH to launch wallets.                                                                                        |
| **CEX Funding Buffer Per Wallet** | Extra ETH added per wallet when CEX funding is enabled. Minimum 0.01 ETH.                                                                                   |
| **Advanced Controls**             | Slippage (labelled Pool Setup Slippage for V3), bundle supply jitter, and - for V2 - bundle priority fee in gwei.                                           |

Token cleanup and holder wallets are not available for Base launches; they are specific to Robinhood and Stable launch methods.

### Tax Controls (V2 only)

Base Uniswap V2 launch tokens support the same tax controls as the other EVM V2 launch methods. Tax controls are optional and disabled by default; when disabled, the token deploys from the no-tax contract template. Base Uniswap V3 launch tokens are always tax-free.

| Setting                                | Description                                                                                                                 |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Initial Buy Tax / Initial Sell Tax** | Taxes used during the initial post-launch tax window.                                                                       |
| **Final Buy Tax / Final Sell Tax**     | Taxes used after the tax switchover block window.                                                                           |
| **Tax Switchover Blocks**              | Number of blocks before final taxes replace initial taxes. Base defaults to 3,000 blocks, longer than the Ethereum default. |
| **Max Supply Per Wallet Limit**        | Optional maximum token balance per non-excluded wallet.                                                                     |
| **Tax Clog**                           | Accumulates tax tokens on the contract and allows swaps to ETH for the tax wallet.                                          |
| **Max Tax Swap Amount**                | Maximum tax-token amount sold in one automatic swap.                                                                        |
| **Min Blocks Between Tax Swaps**       | Cooldown between automatic tax-token swaps.                                                                                 |

### 3. Wallets

Add, import, or generate wallets for each required Base role.

| Role                  | Description                                                                                             |
| --------------------- | ------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Deploys the token, creates the pool, adds liquidity, opens trading, and receives retained supply.       |
| **Tax Wallet**        | V2 launches with tax enabled only. Receives tax proceeds and submits later tax or limit updates.        |
| **Bundle Wallets**    | Execute launch buys before public trading is opened.                                                    |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup. |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Holder and sniper wallets are not used by Base Uniswap launches.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Base ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH through Husher. If CEX funding is disabled, fund the dev, tax, and bundle wallets directly and use **Check Balances**.

The funding table tracks ETH requirements for the dev and bundle wallets. It supports address copying, allocation randomization, per-wallet allocation edits, and balance checks. The dev allocation and final bundle allocation are auto-balanced from the target.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

For Base Uniswap V2, the preview action sequence is:

1. **Deploy Token** - Deploys the generated Base ERC-20 launch token from the dev wallet.
2. **Create Pool** - Creates the Base Uniswap V2 pool, sets launch-wallet fee exemptions, and adds initial liquidity while public trading remains closed.
3. **Launch** - Starts the durable launch runner. It submits bundle-wallet buys in batches, opens public trading after the launch buys are confirmed, activates the profile, and submits ownership renounce.

For Base Uniswap V3, the sequence has the same shape:

1. **Deploy Token** - Deploys the ERC-20 launch token from the dev wallet with the selected fee tier baked in.
2. **Create Pool** - Creates the token/WETH Uniswap V3 pool, sets launch-wallet exemptions, and mints the full-range liquidity position while public trading remains closed. The preview shows the **Position NFT ID** once minted.
3. **Launch** - Starts the durable launch runner for bundle-wallet buys with live buy progress, opens public trading, activates the profile, and submits ownership renounce.

> **Background Launch Runner**
>
> Base launches do not hold the browser request open for every wallet buy. After you click Launch, Sumo records progress on the project and continues the launch-wallet buy runner in the background.

## After Launch

When all launch buys confirm and public trading opens, the profile becomes active and opens in Live Trading. For V2 launches with tax enabled, you can manage taxes or limits and withdraw accumulated tax tokens from the supported launch-token controls.


---

# Aerodrome Base Launch

> Launch a Base ERC-20 token on Aerodrome Classic with WETH liquidity, staged launch buys, tax controls, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/aerodrome-base-launch
- Markdown: https://docs.sumo.trade/launch-tokens/aerodrome-base-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Base launches through **Base Aerodrome**. The flow deploys a Base ERC-20 launch token, creates an Aerodrome Classic volatile WETH pool, adds initial liquidity while public trading is still closed, runs launch-wallet buys, then opens public trading.

![Base Aerodrome token launch buy setup](/images/aerodrome-base-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. ETH on Base for deployment, pool setup, initial liquidity, launch buys, and gas buffers
4. A launch plan: target supply control, pool-token percentage, bundle wallet count, and optional tax settings
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Base wallets / buy aged Base wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

## Launch Flow

### 1. Info

Choose **Base Aerodrome** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                  |
| ------------------------ | -------- | ---------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Base Aerodrome**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                 |
| **Token Name**           | Yes      | ERC-20 token name                                                            |
| **Ticker**               | Yes      | ERC-20 token symbol, auto-uppercased                                         |
| **Total Supply**         | Yes      | ERC-20 total supply before decimals                                          |
| **Decimals**             | Yes      | ERC-20 display decimals, commonly 18                                         |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                 |
| **Description**          | No       | Public token description                                                     |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                  |

### 2. Buy Mode

Base Aerodrome uses the shared EVM buy setup controls.

| Setting                           | Description                                                                                                                          |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Supply Control Target**         | Total supply controlled by dev-retained supply plus launch-wallet buys. Range: 1% to 99.99%.                                         |
| **Initial Liquidity ETH**         | ETH supplied by the dev wallet during pool setup.                                                                                    |
| **Initial Liquidity Tokens**      | Percentage of total supply supplied to the pool. The remainder stays with the dev wallet.                                            |
| **Estimated ETH Required**        | Estimated initial liquidity, launch buys, gas buffers, and CEX funding buffers when enabled.                                         |
| **Estimated Market Cap**          | Estimated from Aerodrome pool reserves after launch buys, using the ETH/USD reference price.                                         |
| **Dev Supply**                    | Read-only value derived from total supply minus pool-token percentage.                                                               |
| **Bundle Buy**                    | Read-only value derived from supply-control target minus dev-retained supply.                                                        |
| **Bundle Wallets**                | Number of Base wallets used for launch buys. Base launch methods support up to 200.                                                  |
| **Funds Per Bundle Wallet**       | ETH reserved per bundle wallet for gas. Minimum 0.01 ETH.                                                                            |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup. |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                            |
| **CEX Funding**                   | Optional Husher funding path for distributing ETH to launch wallets.                                                                 |
| **CEX Funding Buffer Per Wallet** | Extra ETH added per wallet when CEX funding is enabled. Minimum 0.01 ETH.                                                            |
| **Advanced Controls**             | Slippage, bundle supply jitter, and bundle priority fee in gwei.                                                                     |

### Tax Controls

Base Aerodrome launch tokens support configurable taxes, wallet limits, and tax clog behavior. Tax controls are optional and disabled by default; when disabled, the token deploys from the no-tax contract template.

| Setting                                | Description                                                                                                 |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Initial Buy Tax / Initial Sell Tax** | Taxes used during the initial post-launch tax window.                                                       |
| **Final Buy Tax / Final Sell Tax**     | Taxes used after the tax switchover block window.                                                           |
| **Tax Switchover Blocks**              | Number of blocks before final taxes replace initial taxes. Base defaults are longer than Ethereum defaults. |
| **Max Supply Per Wallet Limit**        | Optional maximum token balance per non-excluded wallet.                                                     |
| **Tax Clog**                           | Accumulates tax tokens on the contract and allows swaps to ETH for the tax wallet through Aerodrome.        |
| **Max Tax Swap Amount**                | Maximum tax-token amount sold in one automatic swap.                                                        |
| **Min Blocks Between Tax Swaps**       | Cooldown between automatic tax-token swaps.                                                                 |

### 3. Wallets

Add, import, or generate wallets for each required Base role.

| Role                  | Description                                                                                                 |
| --------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Deploys the token, creates the Aerodrome pool, adds liquidity, opens trading, and receives retained supply. |
| **Tax Wallet**        | Receives tax proceeds and submits later tax or limit updates.                                               |
| **Bundle Wallets**    | Execute launch buys before public trading is opened.                                                        |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.     |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Holder and sniper wallets are not used by Base Aerodrome launches.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Base ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH through Husher. If CEX funding is disabled, fund the dev, tax, and bundle wallets directly and use **Check Balances**.

The funding table tracks ETH requirements for the dev and bundle wallets. It supports address copying, allocation randomization, per-wallet allocation edits, and balance checks. The dev allocation and final bundle allocation are auto-balanced from the target.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

For Base Aerodrome, the preview action sequence is:

1. **Deploy Token** - Deploys the generated Base Aerodrome launch token from the dev wallet.
2. **Create Pool** - Creates the Aerodrome Classic pool, sets launch-wallet fee exemptions, and adds initial liquidity while public trading remains closed.
3. **Launch** - Starts the durable launch runner. It submits bundle-wallet buys in batches, opens public trading after the launch buys are confirmed, activates the profile, and submits ownership renounce.

> **Background Launch Runner**
>
> Base launches continue in the background after the Launch action starts. The preview shows launch progress while the runner submits and confirms launch buys.

## After Launch

When all launch buys confirm and public trading opens, the profile becomes active and opens in Live Trading.


---

# Uniswap Robinhood Launch

> Launch a Robinhood Chain ERC-20 token on Uniswap V2 or Uniswap V3 with WETH liquidity, staged launch buys, optional tax controls, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/robinhood-uniswap-launch
- Markdown: https://docs.sumo.trade/launch-tokens/robinhood-uniswap-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Robinhood Chain launches through **Robinhood Uniswap V2** and **Robinhood Uniswap V3**. Both flows deploy an ERC-20 launch token on Robinhood Chain, create a token/WETH pool, add initial liquidity while public trading is still closed, run launch-wallet buys, then open public trading and activate the profile.

The main differences between the two launch methods:

|                  | Robinhood Uniswap V2                        | Robinhood Uniswap V3                                   |
| ---------------- | ------------------------------------------- | ------------------------------------------------------ |
| **Pool type**    | Uniswap V2 pair                             | Uniswap V3 pool with a selectable fee tier             |
| **Liquidity**    | V2 reserves held by the dev wallet          | Full-range V3 position NFT held by the launch contract |
| **Tax controls** | Optional taxes, wallet limits, and tax clog | Not available - V3 launch tokens are tax-free          |

![Robinhood Uniswap V3 token launch buy setup](/images/robinhood-uniswap-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. ETH on Robinhood Chain for deployment, pool setup, initial liquidity, launch buys, and gas buffers
4. A launch plan: target supply control, pool-token percentage, bundle wallet count, holder cleanup preference, and optional tax settings (V2 only)
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Robinhood Chain Network**
>
> Robinhood Chain uses chain ID eip155:4663 and ETH for gas. Robinhood Uniswap launches use WETH as the quote token, so operators enter ETH amounts in the wizard and Sumo stores the Robinhood Chain WETH quote asset on the active profile after pool creation.

## Launch Flow

### 1. Info

Choose **Robinhood Uniswap V2** or **Robinhood Uniswap V3** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                                                    |
| ------------------------ | -------- | -------------------------------------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Robinhood Uniswap V2** or **Robinhood Uniswap V3**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                                                   |
| **Token Name**           | Yes      | ERC-20 token name                                                                                              |
| **Ticker**               | Yes      | ERC-20 token symbol, auto-uppercased                                                                           |
| **Total Supply**         | Yes      | ERC-20 total supply before decimals                                                                            |
| **Decimals**             | Yes      | ERC-20 display decimals, commonly 18                                                                           |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                                                   |
| **Description**          | No       | Public token description                                                                                       |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                                                    |

### 2. Buy Mode

Both Robinhood launch methods use the EVM buy setup controls.

| Setting                           | Description                                                                                                                                                                                             |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**         | Total supply controlled by dev-retained supply plus launch-wallet buys. Range: 1% to 99.99%.                                                                                                            |
| **Initial Liquidity ETH**         | ETH supplied by the dev wallet during pool setup.                                                                                                                                                       |
| **Initial Liquidity Tokens**      | Percentage of total supply supplied to the pool. The remainder stays with the dev wallet.                                                                                                               |
| **Pool Fee Tier**                 | V3 only. Fee charged by the Uniswap V3 pool on every swap: 0.01%, 0.05%, 0.30% (default), or 1.00%. Initial liquidity always uses the canonical full range.                                             |
| **Estimated ETH Required**        | Estimated initial liquidity, launch buys, gas buffers, and CEX funding buffers when enabled.                                                                                                            |
| **Estimated Market Cap**          | Estimated from the pool composition after launch buys, using the ETH/USD reference price.                                                                                                               |
| **Dev Supply**                    | Read-only value derived from total supply minus pool-token percentage.                                                                                                                                  |
| **Bundle Buy**                    | Read-only value derived from supply-control target minus dev-retained supply.                                                                                                                           |
| **Bundle Wallets**                | Number of Robinhood Chain wallets used for launch buys. Robinhood launches support up to 200.                                                                                                           |
| **Funds Per Bundle Wallet**       | ETH reserved per bundle wallet for gas. Minimum 0.01 ETH.                                                                                                                                               |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                                    |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                               |
| **Token Cleanup Method**          | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to holder wallets and sweeps residual native balances after the launch buys confirm. New Robinhood drafts default to Sell / Buy. |
| **Holder Wallets**                | Shown when token cleanup is enabled. Use at least one holder per bundle wallet and no more than 100 holders per bundle wallet.                                                                          |
| **CEX Funding**                   | Optional funding wallet path for distributing ETH to launch wallets.                                                                                                                                    |
| **CEX Funding Buffer Per Wallet** | Extra ETH added per wallet when CEX funding is enabled. Minimum 0.01 ETH.                                                                                                                               |
| **Advanced Controls**             | Slippage (labelled Pool Setup Slippage for V3), bundle supply jitter, holder supply jitter, cleanup delay, and - for V2 - bundle priority fee in gwei.                                                  |

### Tax Controls (V2 only)

Robinhood Uniswap V2 launch tokens support configurable taxes, wallet limits, and tax clog behavior. Tax controls are optional and disabled by default; when disabled, the token deploys from the no-tax contract template. Robinhood Uniswap V3 launch tokens are always tax-free.

| Setting                                | Description                                                                                           |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Initial Buy Tax / Initial Sell Tax** | Taxes used during the initial post-launch tax window.                                                 |
| **Final Buy Tax / Final Sell Tax**     | Taxes used after the tax switchover block window.                                                     |
| **Tax Switchover Blocks**              | Number of blocks before final taxes replace initial taxes. Robinhood defaults to 3,000 blocks.        |
| **Max Supply Per Wallet Limit**        | Optional maximum token balance per non-excluded wallet.                                               |
| **Tax Clog**                           | Accumulates tax tokens on the contract and allows swaps to ETH for the tax wallet through Uniswap V2. |
| **Max Tax Swap Amount**                | Maximum tax-token amount sold in one automatic swap.                                                  |
| **Min Blocks Between Tax Swaps**       | Cooldown between automatic tax-token swaps.                                                           |

### 3. Wallets

Add, import, or generate wallets for each required Robinhood Chain role.

| Role                  | Description                                                                                             |
| --------------------- | ------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Deploys the token, creates the pool, adds liquidity, opens trading, and receives retained supply.       |
| **Tax Wallet**        | V2 launches with tax enabled only. Receives tax proceeds and submits later tax or limit updates.        |
| **Bundle Wallets**    | Execute launch buys before public trading is opened.                                                    |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup. |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is enabled.                               |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Sniper wallets are not used by Robinhood Uniswap launches.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Robinhood Chain ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH. If CEX funding is disabled, fund the dev, tax, and bundle wallets directly and use **Check Balances**.

The funding table tracks ETH requirements for the dev and bundle wallets. It supports address copying, allocation randomization, per-wallet allocation edits, and balance checks. The dev allocation and final bundle allocation are auto-balanced from the target.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

For Robinhood Uniswap V2, the preview action sequence is:

1. **Deploy Token** - Deploys the generated Robinhood Chain ERC-20 launch token from the dev wallet.
2. **Create Pool** - Creates the token/WETH Uniswap V2 pair, sets launch-wallet fee exemptions, and adds initial liquidity while public trading remains closed.
3. **Launch** - Starts the durable launch runner. It submits bundle-wallet buys in batches, opens public trading after the launch buys are confirmed, runs token cleanup when enabled, activates the profile, and submits ownership renounce.

For Robinhood Uniswap V3, the sequence has the same shape:

1. **Deploy Token** - Deploys the ERC-20 launch token from the dev wallet with the selected fee tier baked in.
2. **Create Pool** - Creates the token/WETH Uniswap V3 pool, sets launch-wallet exemptions, and mints the full-range liquidity position while public trading remains closed. The preview shows the **Position NFT ID** once minted.
3. **Launch** - Starts the durable launch runner for bundle-wallet buys with live buy progress, opens public trading, runs token cleanup when enabled, activates the profile, and submits ownership renounce.

> **Background Launch Runner**
>
> Robinhood launches continue in the background after the Launch action starts. The preview shows launch progress while the runner submits and confirms launch buys.

## After Launch

When all launch buys confirm and public trading opens, the profile becomes active and opens in Live Trading. You can monitor trades, review launch logs, activate starter strategies, and - for V2 launches with tax enabled - manage taxes or limits and withdraw accumulated tax tokens from the supported launch-token controls.


---

# SushiSwap Robinhood Launch

> Launch a Robinhood Chain token through the SushiSwap Launchpad with a single creator transaction, ETH-denominated bundle commitments, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/robinhood-sushi-launch
- Markdown: https://docs.sumo.trade/launch-tokens/robinhood-sushi-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Robinhood SushiSwap** launches on Robinhood Chain. This is not a Uniswap-style pool launch: the SushiSwap Launchpad owns the token and seeds a one-sided position at its own start price, so the operator supplies no initial liquidity. Sumo plans the ordered buys, simulates them against the Launchpad, and submits the creation and every launch buy inside **one creator transaction**.

![Robinhood SushiSwap token launch buy setup](/images/robinhood-sushi-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. ETH on Robinhood Chain for the bundle commitments, the creator gas reserve, and per-wallet cleanup buffers
4. A launch plan: supply control target, bundle wallet count, and holder cleanup preference
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **The Commitment Is ETH, Not Supply**
>
> The supply control target sets how much ETH each bundle wallet commits. The ETH amount is what Sumo freezes when the draft is saved, and wallets are funded against it. The Launchpad prices the pool off ETH/USD at launch, so the supply that ETH actually buys is an estimate that moves with the market - a later price move changes the supply you receive, not the funding you need.

## Launch Flow

### 1. Info

Choose **Robinhood SushiSwap** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                       |
| ------------------------ | -------- | --------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Robinhood SushiSwap**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                      |
| **Token Name**           | Yes      | Public token name                                                                 |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                              |
| **Total Supply**         | Yes      | Token total supply before decimals                                                |
| **Decimals**             | Yes      | Token display decimals, commonly 18                                               |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                      |
| **Description**          | No       | Public token description                                                          |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                       |

### 2. Buy Mode

SushiSwap buy planning is ETH-denominated. There is no initial liquidity, fee tier, range mode, tax, or bundle tip - the Launchpad owns all of it.

| Setting                           | Description                                                                                                                                                                                                     |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**         | Sets how much ETH each bundle wallet commits. Range: 1% to 90%.                                                                                                                                                 |
| **Estimated ETH Required**        | ETH the bundle wallets commit. Unlike the Uniswap modes you supply no liquidity, so this is entirely outlay. The creator gas reserve is counted separately.                                                     |
| **Estimated Market Cap**          | Post-buy market cap from the Launchpad's start price and the current ETH/USD reference price.                                                                                                                   |
| **Bundle Wallets**                | Number of Robinhood Chain wallets used for launch buys. SushiSwap supports 1 to 100. Because every buy executes inside one creator transaction, this cap is a measured gas budget rather than a batching limit. |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                                            |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                                       |
| **Holder Wallets**                | Post-launch token destinations for holder cleanup. Up to 400.                                                                                                                                                   |
| **Token Cleanup Method**          | Off, Token Transfer, or Sell / Buy. Redistributes the bundle wallets' tokens to fresh holder wallets after the launch confirms, by direct transfer or by sells and buys through the shared cleanup contract.    |
| **CEX Funding**                   | Optional funding wallet path for distributing ETH to launch wallets.                                                                                                                                            |
| **CEX Funding Buffer Per Wallet** | Extra ETH held in the CEX funding budget for each launch wallet.                                                                                                                                                |
| **Advanced Controls**             | Bundle supply jitter, slippage, creator gas reserve, funding buffer per wallet, and holder supply jitter.                                                                                                       |

#### Advanced Controls

| Setting                       | Description                                                                                                                                                                             |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Bundle Supply Jitter**      | Randomizes each wallet's share of the committed ETH so the buys do not look uniform. Range 0% to 50%. The total committed is unchanged.                                                 |
| **Slippage**                  | Applied to every buyer's signed minimum output. Minimum 0.1% - zero slippage is rejected, because the pool's start tick can move within an accepted band before the launch is included. |
| **Creator Gas Reserve**       | ETH the creator keeps back for launch and cleanup gas. Checked against the creator's balance before the launch starts.                                                                  |
| **Funding Buffer Per Wallet** | Extra ETH funded to each bundle wallet beyond its buy amount. SushiSwap buyers do not pay launch gas, so this only needs to cover their own cleanup transaction.                        |
| **Holder Supply Jitter**      | Randomizes how much of the bundle supply each holder wallet receives during cleanup. Range 0% to 100%.                                                                                  |

### 3. Wallets

Add, import, or generate wallets for each required Robinhood Chain role.

| Role                  | Description                                                                                                                             |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | The creator. Submits the single launch transaction containing token creation and every bundle buy, and pays all launch and cleanup gas. |
| **Bundle Wallets**    | Receive the launch buys executed inside the creator transaction.                                                                        |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.                                 |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is enabled.                                                               |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

There is no tax wallet - the Launchpad owns the token, so SushiSwap launch tokens have no configurable tax. Freeze and sniper wallets are not used.

### 4. Funding

Save the draft before funding. Saving freezes the per-wallet ETH commitments, and the funding table is where those commitments are edited.

If CEX funding is enabled, deposit the estimated Robinhood Chain ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH. If CEX funding is disabled, fund the dev and bundle wallets directly and use **Check Balances**.

The funding table supports address copying, allocation randomization, per-wallet allocation edits, and balance checks.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview summarizes the committed ETH, total ETH to fund, estimated supply control, estimated market cap, slippage, and creator gas reserve.

There is no separate deploy or pool-creation step. Two actions are available:

1. **Simulate Launch** - Runs the planned transaction against the Launchpad and reports blockers: a simulation error, a concrete creator ETH shortfall, the number of underfunded buyer wallets, or term drift since the plan was frozen.
2. **Launch Bundle** - Hands the launch to the durable runner, which submits the single creator transaction, reads the receipt, runs token cleanup when enabled, and activates the profile.

While the runner owns the workflow the action card reports its state: **Admitted, starting**, **Submitted**, **Landed on-chain**, **Landed, reading receipt**, **Reconciled, finalizing**, and finally **Launched**. A failed launch reports whether it is retryable.

> **Background Launch Runner**
>
> SushiSwap launches continue in the background after the Launch action starts. Re-planning is not offered while the runner owns the workflow, because the transaction is either live or already landed.

## After Launch

When the launch transaction lands and reconciliation completes, the profile becomes active and opens in Live Trading. You can monitor trades, review launch logs, and activate starter strategies.

## Launch Logs

SushiSwap profiles add a **Launch Logs** tab covering plan simulation, transaction submission, receipt reconciliation, and holder cleanup.


---

# Pons V2 Robinhood Launch

> Launch a Robinhood Chain token on the Pons V2 native bonding curve with an atomic launch bundle, optional creator tax, protocol buyback mode, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/robinhood-pons-v2-launch
- Markdown: https://docs.sumo.trade/launch-tokens/robinhood-pons-v2-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Robinhood Pons V2** launches on Robinhood Chain. Pons V2 is a native-quote bonding curve rather than a pool launch: the token trades against the curve in ETH from the first block, and graduates to a Pons V4 pool once the curve reaches its threshold. Sumo plans the ordered curve buys with the same integer curve math the backend planner uses, simulates them, and submits creation plus every launch buy as one atomic bundle.

![Robinhood Pons V2 token launch buy setup](/images/robinhood-pons-v2-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. ETH on Robinhood Chain for the ordered curve buys, the Pons launch fee, the creator gas reserve, and per-wallet cleanup buffers
3. A launch plan: supply control target, optional dev buy, creator tax, bundle wallet count, and holder cleanup preference
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Fixed Pons V2 Parameters**
>
> The current Pons native launch config fixes total supply at 1 billion tokens with 18 decimals and ETH as the quote asset. Total supply and decimals are set automatically when you choose the launchpad and are not edited in the standard Sumo flow.

## Launch Flow

### 1. Info

Choose **Robinhood Pons V2** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                     |
| ------------------------ | -------- | ------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Robinhood Pons V2**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                    |
| **Token Name**           | Yes      | Public token name                                                               |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                            |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                    |
| **Description**          | No       | Public token description                                                        |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                     |

### 2. Buy Mode

Pons V2 buy planning runs against the native bonding curve. Two modes are available:

* **Bundle** keeps the curve active after launch. The dev buy and the bundle wallets control up to 71.4285% of supply.
* **Graduation Bundle** buys out the whole curve inside the launch transaction, graduates the token to its Uniswap V4 pool, and keeps buying from that pool with separate **Post-Graduation Wallets**, all atomically. The dev buy and the bundle wallets always control exactly 71.4285%; everything above that is the **Post-Graduation Buy**, split across the post-graduation wallets. The target can run up to the protocol ceiling of 91.8367% (the curve plus the tokens the factory seeds into the pool), although the pool's constant-product pricing makes the last fraction of a percent prohibitively expensive and the planner reports targets it cannot fill.

| Setting                           | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Quote Asset**                   | The asset the bonding curve is priced in: ETH, or any pair token the Pons factory has approved: the Robinhood stock tokens (TSLA, NVDA, AAPL, and the rest), the SPY, QQQ, GLD, and USO ETFs, cbBTC, and USDG. The picker groups them by kind and is searchable by ticker, name, or address. Each stock quote carries its own curve economics, so the estimates re-read the live terms when you change it. Both modes accept a stock quote: a Graduation Bundle then graduates into a pool paired with that asset, and its Post-Graduation Wallets buy from the pool in it.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Supply Control Target**         | Total supply controlled by the creator, bundle buys, and (in Graduation Bundle) post-graduation buys. Bundle: 1% to 71.4285%, the highest value that stays below the reviewed config's sellable-supply limit; hitting the cap is flagged as **Curve max** in the estimate row. Graduation Bundle: from 71.4285% plus 0.01% per post-graduation wallet up to 91.8367%, flagged **Beyond curve**.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Estimated ETH Required**        | Ordered curve buys, post-graduation pool buys when applicable, plus the live Pons launch fee, creator gas reserve, and configured per-wallet cleanup buffers. On a stock quote this is the ETH the funding swap will spend (the quote total at the live aggregator rate the swap itself executes on, plus a 5% margin and a 0.01 ETH gas allowance per swapping wallet; the swap itself sizes each wallet at its need divided by one minus the slippage and executes with the need as the minimum output, so a landed swap always covers the wallet) plus the ETH-denominated fee, gas, and buffers, and a second row shows the quote total itself. The 5% margin is only the funding target: a wallet reads as funded once it holds the swap's own sizing plus its reserve, so a small rate move after funding does not flag it, and a wallet that does fall under that bar is topped back up to the full target. Once the swap preview has sized the run, its exact per-wallet requirement (at the slippage chosen there) becomes that bar, so any wallet the preview flags reads short in the table and **Fund ETH** offers exactly the top-up the swap needs. If no aggregator can quote the pair the ETH column shows as unavailable and the swap stays disabled until it can. |
| **Estimated Market Cap**          | Projected post-bundle spot price from the same integer curve math used by the backend planner (or the seeded pool's price after the post-graduation buys), multiplied by the fixed one-billion-token supply.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| **Dev Buy**                       | Optional dev-wallet buy before the bundle, always on the curve. Set to 0 for no dev buy. In Graduation Bundle it is capped so every bundle wallet keeps at least 0.01% of the curve.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Post-Graduation Buy**           | Graduation Bundle only. Read-only: the target minus the 71.4285% curve, bought from the Uniswap V4 pool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| **Post-Graduation Wallets**       | Graduation Bundle only. Number of wallets that buy from the pool after graduation, 1 to 32. They are separate from the bundle wallets.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Creator Tax**                   | Optional fee on every Pons buy and sell, 0% to 10%. Token transfers are not taxed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Bundle Wallets**                | Number of launch-exempt external buyers. Pons supports at most 32. The optional dev buy is separate and does not consume one of these slots.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| **Holder Wallets**                | Post-launch destinations for transfer or Pons V2 sell/buy token cleanup. Up to 400.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| **Protocol Buyback Mode**         | Uses part of the creator fees to buy back and vest the token.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Holder Fee Sharing**            | After activation, deploys the token's Pons holder-fee distributor and hands it the creator-fee recipient, so creator fees and creator tax are shared pro-rata with holders, who claim on Pons. Permanent: fees cannot be routed back. The workflow card shows the distributor once routed; if the handoff fails, the launch still completes and the card offers **Retry holder fee routing**, which only redoes the steps that have not landed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Token Cleanup Method**          | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to fresh holder wallets after launch confirmation, by direct transfer or by sells and buys through the shared Pons V2 cleanup route.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **CEX Funding**                   | Funds the Pons launch wallets with ordinary Robinhood Chain ETH cashouts using the standard CEX funding flow.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **CEX Funding Buffer Per Wallet** | Extra ETH included in the CEX cashout budget for each launch wallet.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Advanced Controls**             | Bundle supply jitter, bundle slippage, creator gas reserve, funding buffer per wallet, cleanup delay, and holder supply jitter.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |

> **32 Bundle Wallets Is a Protocol Limit**
>
> The 32-wallet cap is the Pons factory exemption-list limit, not a Sumo batching choice. Only wallets on that list can buy before public trading opens, so the bundle cannot be widened by splitting it across more transactions.

### 3. Wallets

Add, import, or generate wallets for each required Robinhood Chain role.

| Role                        | Description                                                                                                                                                                                                                         |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**              | The creator. Deploys the token and curve, performs the optional dev buy, and pays launch and cleanup gas.                                                                                                                           |
| **Bundle Wallets**          | The launch-exempt buyers that execute ordered curve buys inside the atomic bundle.                                                                                                                                                  |
| **Injection Wallets**       | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.                                                                                                                             |
| **Post-Graduation Wallets** | Graduation Bundle only. Buy from the Uniswap V4 pool after the curve is bought out, in the same transaction. Like bundle wallets they are active project wallets from launch and are cleanup sources when token cleanup is enabled. |
| **Holder Wallets**          | Receive tokens through post-launch cleanup when token cleanup is enabled.                                                                                                                                                           |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Pons V2 launch tokens have no tax wallet - the optional creator tax is collected by the protocol against the creator, not routed to a separate role wallet. Freeze and sniper wallets are not used.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Robinhood Chain ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH. If CEX funding is disabled, fund the dev and bundle wallets directly and use **Check Balances**.

On a stock quote every wallet is still funded in ETH first. Once every wallet holds at least the swap's own ETH sizing (the funding table shows a wallet's balance in red until it does), &#x2A;*Swap ETH to \<QUOTE>** opens a preview of the swap: the live rate and provider, each wallet's quote shortfall, the ETH it will spend and keep, and an adjustable slippage (2% by default). Confirming asks SUMO to swap, per wallet, the ETH its remaining quote shortfall needs (at the best aggregator rate, sized so a fill at the slippage floor still covers the need) into the quote token; wallets that already hold their quote are skipped, and a draft whose wallets are all covered reports that nothing is left to swap. The creator keeps ETH for the launch fee and gas and receives quote for the optional dev buy, and every wallet must keep a 0.01 ETH gas allowance after its swap. The request is rejected up front if any wallet cannot cover its share, and while a swap is still executing a second one is refused. The swaps then land wallet by wallet, so a wallet whose swap fails on-chain keeps its ETH: **Check Balances** shows the shortfall and the swap can simply be run again for what is missing. Small leftover quote balances after launch are expected.

The funding table supports address copying, allocation randomization, per-wallet allocation edits, and balance checks.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview summarizes supply control, dev buy, bundle buy, estimated ETH required, estimated market cap, creator tax, and whether protocol buyback mode is enabled.

There is no separate deploy or pool-creation step. Two actions are available:

1. **Simulate Launch** - Plans the ordered curve buys and reports any blockers before funds move.
2. **Launch Bundle** - Hands the launch to the durable runner, which submits the atomic bundle, reads the launch receipt, runs token cleanup when enabled, and activates the profile.

While the runner owns the workflow the action card reports its state: **Launch admitted**, **Submitting atomic bundle**, **Bundle included**, **Reading launch receipt**, **Activating project**, and finally **Launch complete**. Once reconciled, the card also shows the token and curve addresses.

## After Launch

When the bundle lands and reconciliation completes, the profile becomes active and opens in Live Trading. The Pons V2 workflow card continues to track curve progress after launch:

| Metric         | Description                                                        |
| -------------- | ------------------------------------------------------------------ |
| **Spot Price** | Current curve spot price in ETH.                                   |
| **Graduation** | Progress toward the curve's graduation threshold, as a percentage. |

At graduation the curve migrates to a Pons V4 pool. Migration is automatic, but if pool creation does not complete, the workflow card exposes a **Retry V4 Pool Creation** action to submit it manually.

A Graduation Bundle launch lands already graduated: the profile activates directly on the Uniswap V4 pool, the workflow card shows the pool instead of curve progress, and no migration step remains.

## Launch Logs

Pons V2 profiles add a **Launch Logs** tab for plan simulation, bundle submission, receipt reconciliation, holder cleanup, and V4 pool migration.

## Further Reading

* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — this launchpad's curve overlaid on every other supported launchpad, with graduation math
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — simulate launch cost, starting market cap, and supply held for this launchpad

## Creator Fee Claims

Pons pays the creator a share of every trade fee (per the Pons protocol, 70% of the 1% curve and hook fee) plus the whole creator tax, credited to the launch's creator-fee recipient in the Pons fee escrow. Fees arrive in the asset the trade was quoted in — ETH on a native launch, the pair token on a stock pair — and, after graduation, sometimes in the launched token itself. Pons sweeps them into the escrow on its own schedule; only swept fees can be claimed.

Pons profiles expose **Claim creator fees** in the profile wallet toolbar. The claim reads the recipient from the Pons factory on-chain, so it works for tokens launched on Sumo and for imported Pons tokens still trading on their curve alike, as long as that recipient wallet belongs to the profile (archived launch wallets included). One click claims every non-zero balance, one transaction per asset from that wallet in order, each recorded on its own; the wallet pays only the gas and the fees land in it in full, with no platform cut. The same action is available in Telegram groups through `/fees` and `/claim`.

Claims appear in Treasury Logs as **Creator Fee Claim** entries with the transaction details. A launch with **Holder Fee Sharing** has no creator fees to claim: they belong to holders, and `/fees` says so.

### Holder reward claims

Holder rewards cannot currently be claimed through the Sumo interface because Pons's reward data service is unreliable.


---

# lunch.fun Robinhood Launch

> Launch a Robinhood Chain token on lunch.fun straight into its permanent Uniswap pool, quoted in ETH, HOOD, USDG, or a tokenized stock, with an atomic launch bundle, optional creator tax, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/robinhood-lunch-fun-launch
- Markdown: https://docs.sumo.trade/launch-tokens/robinhood-lunch-fun-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Robinhood lunch.fun** launches on Robinhood Chain. lunch.fun is a pool launchpad with no bonding curve and no migration: the launcher mints the whole supply into a single single-sided position in the pool the coin trades on from block one, and buys walk the price up from the launch tick. Sumo plans the ordered launch buys with the same integer pool math the backend planner uses, simulates them, and submits creation plus every launch buy as one atomic bundle.

Because there is no curve to buy out and no pool to migrate into, Sumo offers **Bundle mode only** on lunch.fun. There is no Graduation Bundle and there are no post-graduation wallets.

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. ETH on Robinhood Chain for the launch buys (or, on a non-ETH quote, for the funding swap that acquires it), the creator gas reserve, and per-wallet cleanup buffers
3. A launch plan: quote asset, total supply, supply control target, optional dev buy, creator tax setting, bundle wallet count, and holder cleanup preference
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

## Fair Launch and Tax Launch

The **Creator Tax** setting picks which lunch.fun launcher creates the token, and with it the pool the coin lives in permanently. Both branches accept the same quote allowlist and price the launch from the same per-quote launch tick.

|                      | Creator tax off (fair launch)                                           | Creator tax on (tax launch)                                                                                       |
| -------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Pool**             | Uniswap V3, 1% fee tier                                                 | Uniswap V4, 0.3% LP fee, bound to the lunch.fun tax hook                                                          |
| **Tax**              | None                                                                    | Buy tax and sell tax, 0% to 5% each (0 to 500 bps), charged on the quote side                                     |
| **Creator earnings** | 50% of the pool's 1% trading fee, through the lunch.fun pair fee locker | The creator tax, less the 20% lunch.fun keeps. The pool's 0.3% LP fee compounds into the locked position instead. |
| **After launch**     | Fixed                                                                   | The creator can retune both tax rates on-chain (`setRates`), and lunch.fun's admin can reassign the creator       |

> **Tax Launches Tax Cleanup Too**
>
> On a tax launch the pool is hooked, so a **Sell / Buy** holder cleanup round trip pays the sell tax and the buy tax once each. Budget for it, or use **Token Transfer** cleanup instead.

## Quote Assets

lunch.fun launches can be quoted in ETH or in any token both launchers allow:

| Quote                         | Notes                                                                                                                                                                                                                                                      |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ETH**                       | The native quote. The launchers price it through WETH, and every buyer wraps its own ETH inside the launch transaction.                                                                                                                                    |
| **HOOD**                      | lunch.fun's vault-backed HOOD share token.                                                                                                                                                                                                                 |
| **USDG**                      | Global Dollar, 6 decimals.                                                                                                                                                                                                                                 |
| **Tokenized stocks and ETFs** | 38 Robinhood stock and ETF tokens the launchers allow: TSLA, NVDA, AAPL, GOOGL, AMZN, MSFT, and the rest of the stock catalogue, plus the SPY, QQQ, USO, SGOV, and SLV ETFs. The picker groups them by kind and is searchable by ticker, name, or address. |

Not every Robinhood pair token Sumo supports elsewhere is allowed on lunch.fun; the picker only offers the ones the launchers accept, and the quote is re-validated against the live on-chain allowlist when the plan is built.

> **HOOD Is a Vault Share, and Its Liquidity Is Thin**
>
> HOOD here is lunch.fun's vault-backed HOOD share token (`HoodLighterShare`, `0x32aC8C1D7672667D5EbdEa22935F7B06fC8D496f`), not a Robinhood-issued stock token; its liquidity is thin, so the funding-swap preview shows the price impact of acquiring it — that, not the launch pool, is what bounds a HOOD bundle.

## Launch Flow

### 1. Info

Choose **Robinhood lunch.fun** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                       |
| ------------------------ | -------- | --------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Robinhood lunch.fun**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                      |
| **Token Name**           | Yes      | Public token name                                                                 |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                              |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                      |
| **Description**          | No       | Public token description                                                          |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                       |

### 2. Buy Mode

lunch.fun buy planning runs against the single-sided position the launcher seeds. Only **Bundle** mode exists: the pool the launch creates is the pool the coin trades on forever.

| Setting                           | Description                                                                                                                                                                                                                                                                                                                         |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Quote Asset**                   | The asset the pool is priced in: ETH, HOOD, USDG, or an allowed tokenized stock or ETF. Each quote carries its own launch tick, so the estimates re-read the live terms when you change it.                                                                                                                                         |
| **Total Supply**                  | User-configurable, unlike most launchpads. Defaults to 1,000,000,000 tokens, the figure lunch.fun's own site presents. Decimals are fixed at 18. The supply must be at least 1,000,000 tokens and at most the launcher's `int128` ceiling of 2<sup>127</sup>-1 base units.                                                          |
| **Supply Control Target**         | Total supply controlled by the creator plus the bundle buys, capped at 90%. Beyond that the last buys price in tens of quote tokens, because they walk the far end of the position's range. Each bundle wallet needs a positive allocation that can be quoted and executed; there is no fixed minimum supply percentage per wallet. |
| **Estimated ETH Required**        | The ordered launch buys plus the creator gas reserve and configured per-wallet cleanup buffers. On a non-ETH quote this is the ETH the funding swap will spend, and a second row shows the quote total itself.                                                                                                                      |
| **Estimated Market Cap**          | Projected post-bundle spot price from the same pool math the backend planner uses, multiplied by the configured total supply.                                                                                                                                                                                                       |
| **Dev Buy**                       | Optional dev-wallet buy, executed before the bundle wallets in the same transaction. Set to 0 for no dev buy.                                                                                                                                                                                                                       |
| **Creator Tax**                   | Off for a Uniswap V3 fair launch, or on for a Uniswap V4 tax launch with buy and sell tax of 0% to 5% each. See [Fair Launch and Tax Launch](#fair-launch-and-tax-launch).                                                                                                                                                          |
| **Bundle Wallets**                | Number of launch buyers inside the atomic bundle. lunch.fun launches support at most 32. The optional dev buy is separate and does not consume one of these slots.                                                                                                                                                                  |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                                                                                                                                                                |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                                                                                                                                                           |
| **Holder Wallets**                | Post-launch destinations for transfer or sell/buy token cleanup. Up to 400.                                                                                                                                                                                                                                                         |
| **Token Cleanup Method**          | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to fresh holder wallets after launch confirmation, by direct transfer or by sells and buys through the launch pool.                                                                                                                                          |
| **CEX Funding**                   | Funds the launch wallets with ordinary Robinhood Chain ETH cashouts using the standard CEX funding flow.                                                                                                                                                                                                                            |
| **CEX Funding Buffer Per Wallet** | Extra ETH included in the CEX cashout budget for each launch wallet.                                                                                                                                                                                                                                                                |
| **Advanced Controls**             | Bundle supply jitter, bundle slippage, creator gas reserve, funding buffer per wallet, cleanup delay, and holder supply jitter.                                                                                                                                                                                                     |

> **One Transaction, Real Buyers**
>
> The token creation, the optional dev buy, and every bundle wallet's buy land in a single atomic transaction. Each Sumo wallet is the Uniswap swap sender and the token recipient in its own buy, so the pool records 32 distinct buyers rather than one address distributing afterwards. If any part fails, the whole transaction reverts and nothing is spent beyond gas.

### 3. Wallets

Add, import, or generate wallets for each required Robinhood Chain role.

| Role                  | Description                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Dev Wallet**        | The creator. Deploys the token and seeds the pool, performs the optional dev buy, and pays launch and cleanup gas. |
| **Bundle Wallets**    | The launch buyers that execute the ordered pool buys inside the atomic bundle.                                     |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.            |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is enabled.                                          |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

lunch.fun launch tokens have no tax wallet - the optional creator tax is collected by the tax hook against the creator, not routed to a separate role wallet. Freeze and sniper wallets are not used.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Robinhood Chain ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH. If CEX funding is disabled, fund the dev and bundle wallets directly and use **Check Balances**.

On an ETH-quoted launch that is all: each buyer wraps its own ETH into WETH inside the launch transaction.

On every other quote the wallets are funded in ETH first and then swapped into the quote **before** the bundle, through the treasury aggregator route. This is the same funding swap the Pons V2 flow uses. Once every wallet holds at least the swap's own ETH sizing (the funding table shows a wallet's balance in red until it does), &#x2A;*Swap ETH to \<QUOTE>** opens a preview of the swap: the live rate and provider, each wallet's quote shortfall, the ETH it will spend and keep, and an adjustable slippage. Confirming asks Sumo to swap, per wallet, the ETH its remaining quote shortfall needs into the quote token; wallets that already hold their quote are skipped. The swaps land wallet by wallet, so a wallet whose swap fails on-chain keeps its ETH: **Check Balances** shows the shortfall and the swap can simply be run again for what is missing. Small leftover quote balances after launch are expected.

> **The Launch Never Zaps Through the Quote Pool**
>
> Buyers hold the quote asset before the bundle is submitted. The launch transaction only buys the new coin; it never routes ETH through the thin HOOD or stock pools, so the funding swap's price impact is visible and adjustable in its own preview instead of being buried in the launch.

The funding table supports address copying, allocation randomization, per-wallet allocation edits, and balance checks.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview summarizes quote asset, total supply, supply control, dev buy, bundle buy, estimated ETH required, estimated market cap, and the creator tax setting with its buy and sell rates.

There is no separate deploy or pool-creation step. Two actions are available:

1. **Simulate Launch** - Plans the ordered pool buys and reports any blockers before funds move.
2. **Launch Bundle** - Hands the launch to the durable runner, which submits the atomic bundle, reads the launch receipt, runs token cleanup when enabled, and activates the profile.

While the runner owns the workflow the action card reports its state: **Launch admitted**, **Submitting atomic bundle**, **Bundle included**, **Reading launch receipt**, **Activating project**, and finally **Launch complete**. Once reconciled, the card also shows the token and pool addresses.

## Fees and Referral

lunch.fun charges no launch fee: the V3 pair launcher's `launchFeeWei` is 0 and the V4 pair launcher charges none. You still pay Sumo's usual launch charge - one **Launch Ticket** or the **0.25% token-supply dev allocation** - as on every other launchpad. See [Platform Fees](/platform-fees).

lunch.fun's own revenue comes from the pool: 30% of the 1% trading fee on a fair launch, and 20% of the creator tax on a tax launch. Its `ReferralSplitter` pays a registered referrer 10% of that platform share, and Sumo is registered as the referrer on launches created through Sumo.

## After Launch

When the bundle lands and reconciliation completes, the profile becomes active and opens in Live Trading, on the Uniswap V3 pool for a fair launch or the Uniswap V4 pool for a tax launch. There is no curve to track and no graduation or migration step: the launch pool is the permanent pool, so live trading, strategies, and holder cleanup all run against it immediately.

lunch.fun shows a "graduation" badge on its own site once a coin passes a net-principal threshold. It is cosmetic - it does not move liquidity or change the pool - and Sumo does not model it.

## Launch Logs

lunch.fun profiles add a **Launch Logs** tab for plan simulation, bundle submission, receipt reconciliation, and holder cleanup.

## Further Reading

* [How to Launch a Memecoin in 2026](https://blog.sumo.trade/how-to-launch-a-memecoin/) — the full launch playbook, from wallet prep to post-launch market making
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — simulate launch cost, starting market cap, and supply held across supported launchpads


---

# LetsCash Robinhood Launch

> Launch a Robinhood Chain token through LetsCash on Uniswap V4 with an atomic launch bundle, selectable trading-fee configuration, optional buyback-and-burn, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/robinhood-letscash-launch
- Markdown: https://docs.sumo.trade/launch-tokens/robinhood-letscash-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Robinhood LetsCash** launches on Robinhood Chain. LetsCash launches the token straight into a Uniswap V4 pool: Sumo plans the ordered V4 buys with the same math the backend planner uses, simulates them, and submits creation plus every launch buy as one atomic bundle. The launch configuration you pick sets the pool's trading fee and whether the protocol runs buyback-and-burn.

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. ETH on Robinhood Chain for the ordered V4 buys, the launch fee, the creator gas reserve, and per-wallet cleanup buffers
3. A launch plan: supply control target, optional dev buy, trading-fee configuration, bundle wallet count, and holder cleanup preference
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Fixed LetsCash Parameters**
>
> LetsCash launch tokens use a fixed total supply of 1 billion tokens with 18 decimals and ETH as the quote asset. Total supply and decimals are set automatically when you choose the launchpad and are not edited in the standard Sumo flow.

## Launch Flow

### 1. Info

Choose **Robinhood LetsCash** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                      |
| ------------------------ | -------- | -------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Robinhood LetsCash**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                     |
| **Token Name**           | Yes      | Public token name                                                                |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                             |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                     |
| **Description**          | No       | Public token description                                                         |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                      |

### 2. Buy Mode

LetsCash buy planning runs against the Uniswap V4 pool the launch creates.

| Setting                           | Description                                                                                                                                                                              |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**         | Total supply controlled by the creator plus bundle buys. Range: 1% to 99%.                                                                                                               |
| **Estimated ETH Required**        | Ordered V4 buys plus the launch fee, creator gas reserve, and configured per-wallet cleanup buffers.                                                                                     |
| **Estimated Market Cap**          | Projected market cap after the complete bundle.                                                                                                                                          |
| **Dev Buy**                       | Optional dev-wallet buy before the bundle. Set to 0 for no dev buy.                                                                                                                      |
| **Trading Fee**                   | The LetsCash launch configuration's pool fee: 1%, 3%, 5%, or 10%, each with its creator fee share. Locked while Protocol Buyback Mode is enabled.                                        |
| **Bundle Wallets**                | Number of external launch buyers. LetsCash supports up to 100. The optional dev buy is separate and does not consume one of these slots.                                                 |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                     |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                |
| **Holder Wallets**                | Post-launch destinations for transfer or V4 sell/buy token cleanup. Up to 400.                                                                                                           |
| **Protocol Buyback Mode**         | Switches to the LetsCash buyback-and-burn launch configuration.                                                                                                                          |
| **Token Cleanup Method**          | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to fresh holder wallets after launch confirmation, by direct transfer or by V4 sells and buys through Uniswap V4. |
| **CEX Funding**                   | Funds the launch wallets with ordinary Robinhood Chain ETH cashouts using the standard CEX funding flow.                                                                                 |
| **CEX Funding Buffer Per Wallet** | Extra ETH included in the CEX cashout budget for each launch wallet.                                                                                                                     |
| **Advanced Controls**             | Bundle supply jitter, bundle slippage, creator gas reserve, funding buffer per wallet, cleanup delay, and holder supply jitter.                                                          |

### 3. Wallets

Add, import, or generate wallets for each required Robinhood Chain role.

| Role                  | Description                                                                                              |
| --------------------- | -------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | The creator. Deploys the token and pool, performs the optional dev buy, and pays launch and cleanup gas. |
| **Bundle Wallets**    | The launch buyers that execute ordered V4 buys inside the atomic bundle.                                 |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.  |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is enabled.                                |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

LetsCash launch tokens have no tax wallet - fees are collected by the pool per the selected launch configuration, not routed to a separate role wallet. Freeze and sniper wallets are not used.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Robinhood Chain ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH. If CEX funding is disabled, fund the dev and bundle wallets directly and use **Check Balances**.

The funding table supports address copying, allocation randomization, per-wallet allocation edits, and balance checks.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview summarizes supply control, dev buy, bundle buy, estimated ETH required, estimated market cap, and the selected trading-fee configuration.

There is no separate deploy or pool-creation step. Two actions are available:

1. **Simulate Launch** - Plans the ordered V4 buys and reports any blockers before funds move.
2. **Launch Bundle** - Hands the launch to the durable runner, which submits the atomic bundle, reads the V4 receipt, runs token cleanup when enabled, and activates the profile.

While the runner owns the workflow the action card reports its state: **Launch admitted**, **Submitting atomic bundle**, **Bundle included**, **Reading V4 receipt**, **Activating project**, and finally **Launch complete**. A failed launch reports whether it is retryable.

## After Launch

When the bundle lands and reconciliation completes, the profile becomes active and opens in Live Trading. You can monitor trades, review launch logs, and activate starter strategies.

## Launch Logs

LetsCash profiles add a **Launch Logs** tab covering plan simulation, bundle submission, receipt reconciliation, and holder cleanup.


---

# Pools.trade Robinhood Launch

> Launch a Robinhood Chain token through Pools.trade on Uniswap V4 with an atomic launch bundle, protocol-fixed creator fees, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/robinhood-pools-trade-launch
- Markdown: https://docs.sumo.trade/launch-tokens/robinhood-pools-trade-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Robinhood Pools.trade** launches on Robinhood Chain. Pools.trade launches the token straight into a Uniswap V4 pool: Sumo plans the ordered V4 buys with the same integer range math the backend planner uses, simulates them, and submits creation plus every launch buy as one atomic bundle.

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. ETH on Robinhood Chain for the ordered V4 buys, the creator gas reserve, and per-wallet cleanup buffers
3. A launch plan: supply control target, optional dev buy, creator-fee preference, bundle wallet count, and holder cleanup preference
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Fixed Pools.trade Parameters**
>
> Pools.trade launch tokens use a fixed total supply of 1 billion tokens with 18 decimals and ETH as the quote asset. Total supply and decimals are set automatically when you choose the launchpad and are not edited in the standard Sumo flow.

## Launch Flow

### 1. Info

Choose **Robinhood Pools.trade** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                         |
| ------------------------ | -------- | ----------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Robinhood Pools.trade**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                        |
| **Token Name**           | Yes      | Public token name                                                                   |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                                |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                        |
| **Description**          | No       | Public token description                                                            |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                         |

### 2. Buy Mode

Pools.trade buy planning runs against the Uniswap V4 pool the launch creates.

| Setting                           | Description                                                                                                                                                                                                       |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**         | Total supply controlled by the creator plus bundle buys. Range: 1% to 99%.                                                                                                                                        |
| **Estimated ETH Required**        | Ordered Uniswap V4 buys plus the creator gas reserve and configured per-wallet cleanup buffers.                                                                                                                   |
| **Estimated Market Cap**          | Projected post-bundle spot price from the same integer V4 range math used by the backend planner, multiplied by the fixed one-billion-token supply.                                                               |
| **Dev Buy**                       | Optional dev-wallet buy before the bundle. Set to 0 for no dev buy.                                                                                                                                               |
| **Creator Fees**                  | Pays the creator a protocol-fixed 0.05% of swap volume (5 bps) from the pool's 0.25% swap fee. The rate is not editable.                                                                                          |
| **Bundle Wallets**                | Number of external launch buyers. Sumo supports up to 128 Pools.trade buyers under the measured transaction gas envelope. The optional dev buy is separate and does not consume one of these slots.               |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with ETH for activity after launch. They do not buy in the launch or take part in cleanup.                                                                              |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. ETH sent to each injection wallet during funding. Defaults to 0.                                                                                                         |
| **Holder Wallets**                | Post-launch destinations for transfer or V4 sell/buy token cleanup. Up to 400.                                                                                                                                    |
| **Token Cleanup Method**          | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to fresh holder wallets after launch confirmation, by direct transfer or by sells and buys through the shared Uniswap V4 cleanup contract. |
| **CEX Funding**                   | Funds the launch wallets with ordinary Robinhood Chain ETH cashouts using the standard CEX funding flow.                                                                                                          |
| **CEX Funding Buffer Per Wallet** | Extra ETH included in the CEX cashout budget for each launch wallet.                                                                                                                                              |
| **Advanced Controls**             | Bundle supply jitter, bundle slippage, creator gas reserve, funding buffer per wallet, cleanup delay, and holder supply jitter.                                                                                   |

> **128 Bundle Wallets Is a Gas Budget**
>
> The 128-buyer cap is a measured transaction gas envelope: every launch buy executes inside the one atomic bundle, so the cap reflects what fits in that transaction rather than a protocol exemption list.

### 3. Wallets

Add, import, or generate wallets for each required Robinhood Chain role.

| Role                  | Description                                                                                              |
| --------------------- | -------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | The creator. Deploys the token and pool, performs the optional dev buy, and pays launch and cleanup gas. |
| **Bundle Wallets**    | The launch buyers that execute ordered V4 buys inside the atomic bundle.                                 |
| **Injection Wallets** | Optional wallets funded with ETH for activity after launch. They take no part in the launch or cleanup.  |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is enabled.                                |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Pools.trade launch tokens have no tax wallet - the creator fee is protocol-fixed and collected from the pool's swap fee, not routed to a separate role wallet. Freeze and sniper wallets are not used.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated Robinhood Chain ETH into the funding wallet, check the balance, then use **Fund** to distribute ETH. If CEX funding is disabled, fund the dev and bundle wallets directly and use **Check Balances**.

The funding table supports address copying, allocation randomization, per-wallet allocation edits, and balance checks.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview summarizes supply control, dev buy, bundle buy, estimated ETH required, estimated market cap, and whether creator fees are enabled.

There is no separate deploy or pool-creation step. Two actions are available:

1. **Simulate Launch** - Plans the ordered V4 buys and reports any blockers before funds move.
2. **Launch Bundle** - Hands the launch to the durable runner, which submits the atomic bundle, reads the V4 receipt, runs token cleanup when enabled, and activates the profile.

While the runner owns the workflow the action card reports its state: **Launch admitted**, **Submitting atomic bundle**, **Bundle included**, **Reading V4 receipt**, **Activating project**, and finally **Launch complete**. A failed launch reports whether it is retryable.

## After Launch

When the bundle lands and reconciliation completes, the profile becomes active and opens in Live Trading. You can monitor trades, review launch logs, and activate starter strategies.

## Launch Logs

Pools.trade profiles add a **Launch Logs** tab covering plan simulation, bundle submission, receipt reconciliation, and holder cleanup.


---

# Uniswap V3 Stable Launch

> Launch a Stable Mainnet ERC-20 token on Uniswap V3 with USDT0 liquidity, staged launch buys, holder cleanup, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/stable-uniswap-launch
- Markdown: https://docs.sumo.trade/launch-tokens/stable-uniswap-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Stable Mainnet launches through **Stable Uniswap V3**. The flow deploys an ERC-20 launch token on Stable, creates a token/USDT0 Uniswap V3 pool at the selected fee tier, mints a full-range liquidity position while public trading is still closed, runs launch-wallet buys, then opens public trading and activates the profile.

![Stable Uniswap V3 token launch buy setup](/images/stable-uniswap-launch-buy-setup.png)

> **Stable Network and USDT0 Quote**
>
> Stable Mainnet is a stablecoin-native chain: gas is paid in USDT0, and Stable Uniswap V3 launches use USDT0 (6 decimals) as the quote token. All liquidity, launch buy, and buffer amounts in the wizard are entered in USDT0 rather than ETH.

> **Funding Path**
>
> CEX funding is not available for Stable launches - the privacy provider does not support Stable Mainnet, so the toggle is disabled. Fund the dev and bundle wallets directly by cashout.

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. USDT0 on Stable for deployment, pool setup, initial liquidity, launch buys, and gas buffers
4. A launch plan: target supply control, pool-token percentage, pool fee tier, bundle wallet count, and holder cleanup preference
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new Stable wallets / buy aged EVM wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

## Launch Flow

### 1. Info

Choose **Stable Uniswap V3** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                     |
| ------------------------ | -------- | ------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Stable Uniswap V3**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                    |
| **Token Name**           | Yes      | ERC-20 token name                                                               |
| **Ticker**               | Yes      | ERC-20 token symbol, auto-uppercased                                            |
| **Total Supply**         | Yes      | ERC-20 total supply before decimals                                             |
| **Decimals**             | Yes      | ERC-20 display decimals, commonly 18                                            |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                    |
| **Description**          | No       | Public token description                                                        |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                     |

### 2. Buy Mode

Stable Uniswap V3 uses the EVM buy setup controls with USDT0 labels.

| Setting                        | Description                                                                                                                                                                                   |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**      | Total supply controlled by dev-retained supply plus launch-wallet buys. Range: 1% to 99.99%.                                                                                                  |
| **Initial Liquidity USDT0**    | USDT0 supplied by the dev wallet during pool setup.                                                                                                                                           |
| **Initial Liquidity Tokens**   | Percentage of total supply supplied to the pool. The remainder stays with the dev wallet.                                                                                                     |
| **Pool Fee Tier**              | Fee charged by the Uniswap V3 pool on every swap: 0.01%, 0.05%, 0.30% (default), or 1.00%. Initial liquidity always uses the canonical full range.                                            |
| **Estimated USDT0 Required**   | Estimated initial liquidity, launch buys, and gas buffers.                                                                                                                                    |
| **Estimated Market Cap**       | Estimated from pool composition after launch buys. USDT0 is treated as pegged to $1.                                                                                                          |
| **Dev Supply**                 | Read-only value derived from total supply minus pool-token percentage.                                                                                                                        |
| **Bundle Buy**                 | Read-only value derived from supply-control target minus dev-retained supply.                                                                                                                 |
| **Bundle Wallets**             | Number of Stable wallets used for launch buys. Stable Uniswap V3 supports up to 200.                                                                                                          |
| **Funds Per Bundle Wallet**    | USDT0 reserved per bundle wallet for gas. Minimum 1 USDT0.                                                                                                                                    |
| **Injection Wallets**          | Optional extra wallets, up to 100, funded with USDT0 for activity after launch. They do not buy in the launch or take part in cleanup.                                                        |
| **Funds Per Injection Wallet** | Shown when Injection Wallets is above 0. USDT0 sent to each injection wallet during funding. Defaults to 0.                                                                                   |
| **Token Cleanup Method**       | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to holder wallets and sweeps residual balances after the launch buys confirm. New Stable drafts default to Sell / Buy. |
| **Holder Wallets**             | Shown when token cleanup is enabled. Use at least one holder per bundle wallet and no more than 100 holders per bundle wallet.                                                                |
| **Advanced Controls**          | Pool Setup Slippage, bundle supply jitter, holder supply jitter, and cleanup delay.                                                                                                           |

Stable Uniswap V3 launch tokens are always tax-free; there are no tax controls, tax wallet, or clog settings.

### 3. Wallets

Add, import, or generate wallets for each required Stable role.

| Role                  | Description                                                                                               |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Deploys the token, creates the pool, adds liquidity, opens trading, and receives retained supply.         |
| **Bundle Wallets**    | Execute launch buys before public trading is opened.                                                      |
| **Injection Wallets** | Optional wallets funded with USDT0 for activity after launch. They take no part in the launch or cleanup. |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is enabled.                                 |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Tax and sniper wallets are not used by Stable Uniswap V3 launches.

### 4. Funding

Save the draft before funding, then fund the dev and bundle wallets directly with USDT0 and use **Check Balances**.

The funding table tracks USDT0 requirements for the dev and bundle wallets. It supports address copying, allocation randomization, per-wallet allocation edits, and balance checks. The dev allocation and final bundle allocation are auto-balanced from the target.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

For Stable Uniswap V3, the preview action sequence is:

1. **Deploy Token** - Deploys the ERC-20 launch token from the dev wallet with the selected fee tier baked in.
2. **Create Pool** - Creates the token/USDT0 Uniswap V3 pool, sets launch-wallet exemptions, and mints the full-range liquidity position while public trading remains closed. The preview shows the **Position NFT ID** once minted.
3. **Launch** - Starts the durable launch runner. It approves and submits bundle-wallet buys with live buy progress, opens public trading after the launch buys are confirmed, runs token cleanup when enabled, activates the profile, and submits ownership renounce.

> **Background Launch Runner**
>
> Stable launches continue in the background after the Launch action starts. The preview shows launch progress while the runner submits and confirms launch buys.

## After Launch

When all launch buys confirm and public trading opens, the profile becomes active and opens in Live Trading. The launched pool trades through Uniswap on Stable, and Stable profiles support the normal treasury, reporting, holder analysis, and strategy tooling.


---

# PancakeSwap V2 BSC Launch

> Launch a BNB Smart Chain ERC-20 token on PancakeSwap V2 with WBNB liquidity, BSC bundle submission, tax controls, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/pancakeswap-v2-bsc-launch
- Markdown: https://docs.sumo.trade/launch-tokens/pancakeswap-v2-bsc-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports BNB Smart Chain launches through **PancakeSwap V2 BSC**. The flow deploys an ERC-20 launch token, creates a WBNB pair, adds initial liquidity while public trading is closed, submits atomic BSC bundle buys, and then opens trading.

![PancakeSwap V2 BSC token launch buy setup](/images/pancakeswap-v2-bsc-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. Total supply and token decimals
3. BNB for deployment, pool setup, initial liquidity, bundle buys, and gas buffers
4. A launch plan: target supply control, pool-token percentage, bundle wallet count, and optional tax settings
5. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new BSC wallets / buy aged BSC wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **BNB and WBNB**
>
> Operators enter BNB amounts in the launch wizard. Sumo creates a WBNB-quoted PancakeSwap V2 pool and stores WBNB quote metadata on the active profile.

## Launch Flow

### 1. Info

Choose **PancakeSwap V2 BSC** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                      |
| ------------------------ | -------- | -------------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **PancakeSwap V2 BSC**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                     |
| **Token Name**           | Yes      | ERC-20 token name                                                                |
| **Ticker**               | Yes      | ERC-20 token symbol, auto-uppercased                                             |
| **Total Supply**         | Yes      | ERC-20 total supply before decimals                                              |
| **Decimals**             | Yes      | ERC-20 display decimals, commonly 18                                             |
| **Image**                | Yes      | JPG or PNG image, up to 2 MB                                                     |
| **Description**          | No       | Public token description                                                         |
| **X, Telegram, Website** | No       | Public social links attached to the profile                                      |

### 2. Buy Mode

PancakeSwap V2 BSC uses the shared EVM buy setup controls with BNB labels.

| Setting                            | Description                                                                                                                                                                                   |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**          | Total supply controlled by dev-retained supply plus bundle-wallet buys.                                                                                                                       |
| **Initial Liquidity BNB**          | BNB supplied by the dev wallet during pool setup.                                                                                                                                             |
| **Initial Liquidity Tokens**       | Percentage of total supply supplied to the pool. The remainder stays with the dev wallet.                                                                                                     |
| **Estimated BNB Required**         | Estimated initial liquidity, launch buys, gas buffers, and CEX funding buffers when enabled.                                                                                                  |
| **Estimated Market Cap**           | Estimated from PancakeSwap V2 pool reserves after launch buys, using the BNB/USD reference price.                                                                                             |
| **Dev Supply**                     | Read-only value derived from total supply minus pool-token percentage.                                                                                                                        |
| **Bundle Buy**                     | Read-only value derived from supply-control target minus dev-retained supply.                                                                                                                 |
| **Bundle Wallets**                 | Number of BSC wallets used for bundle buys. PancakeSwap V2 BSC supports up to 48 bundle wallets.                                                                                              |
| **Funds Per Bundle Wallet**        | BNB reserved per bundle wallet for gas.                                                                                                                                                       |
| **Injection Wallets**              | Optional extra wallets, up to 100, funded with BNB for activity after launch. They do not buy in the launch or take part in cleanup.                                                          |
| **Funds Per Injection Wallet**     | Shown when Injection Wallets is above 0. BNB sent to each injection wallet during funding. Defaults to 0.                                                                                     |
| **Token Cleanup Method**           | Off, Token Transfer, or Sell / Buy. Redistributes bundle-wallet tokens to holder wallets and sweeps residual native balances after the launch buys confirm. New drafts default to Sell / Buy. |
| **Holder Wallets**                 | Shown when token cleanup is not Off. Use at least one holder per bundle wallet and no more than 100 holders per bundle wallet.                                                                |
| **Native Funds Per Holder Wallet** | Shown with Sell / Buy. BNB sent to each holder wallet during funding for its cleanup buy, seeded at 0.01 BNB. Each holder must hold at least 0.002 BNB before the launch is accepted.         |
| **CEX Funding**                    | Optional Husher funding path for distributing BNB.                                                                                                                                            |
| **CEX Funding Buffer Per Wallet**  | Extra BNB added per wallet when CEX funding is enabled.                                                                                                                                       |
| **Advanced Controls**              | Slippage, bundle supply jitter, and BSC bundle priority fee in gwei.                                                                                                                          |

### Tax Controls

PancakeSwap V2 BSC launch tokens use the shared EVM tax controls. Tax controls are optional and disabled by default; when disabled, the token deploys from the no-tax contract template.

| Setting                                | Description                                                                        |
| -------------------------------------- | ---------------------------------------------------------------------------------- |
| **Initial Buy Tax / Initial Sell Tax** | Taxes used during the initial post-launch tax window.                              |
| **Final Buy Tax / Final Sell Tax**     | Taxes used after the tax switchover block window.                                  |
| **Tax Switchover Blocks**              | Number of blocks before final taxes replace initial taxes.                         |
| **Max Supply Per Wallet Limit**        | Optional maximum token balance per non-excluded wallet.                            |
| **Tax Clog**                           | Accumulates tax tokens on the contract and allows swaps to BNB for the tax wallet. |
| **Max Tax Swap Amount**                | Maximum tax-token amount sold in one automatic swap.                               |
| **Min Blocks Between Tax Swaps**       | Cooldown between automatic tax-token swaps.                                        |

### 3. Wallets

Add, import, or generate wallets for each required BSC role.

| Role                  | Description                                                                                                      |
| --------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**        | Deploys the token, creates the PancakeSwap V2 pool, adds liquidity, opens trading, and receives retained supply. |
| **Tax Wallet**        | Receives tax proceeds and submits later tax or limit updates when tax is enabled.                                |
| **Bundle Wallets**    | Execute BSC bundle buys before public trading opens.                                                             |
| **Injection Wallets** | Optional wallets funded with BNB for activity after launch. They take no part in the launch or cleanup.          |
| **Holder Wallets**    | Receive tokens through post-launch cleanup when token cleanup is not Off.                                        |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Sniper wallets are not used by PancakeSwap V2 BSC launches.

### 4. Funding

Save the draft before funding. If CEX funding is enabled, deposit the estimated BNB into the funding wallet, check the balance, then use **Fund** to distribute BNB through Husher. If CEX funding is disabled, fund the dev, tax, and bundle wallets directly and use **Check Balances**.

The funding table tracks BNB requirements for the dev and bundle wallets. It supports address copying, allocation randomization, per-wallet allocation edits, and balance checks.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

For PancakeSwap V2 BSC, the preview action sequence is:

1. **Deploy Token** - Deploys the generated BSC ERC-20 launch token from the dev wallet.
2. **Create Pool** - Creates the PancakeSwap V2 WBNB pool, sets launch-wallet exemptions, and adds initial liquidity while public trading remains closed.
3. **Launch** - Submits the atomic BSC bundle, confirms landed transactions on-chain, opens public trading, activates the profile, and submits ownership renounce when configured.

> **BSC Bundles**
>
> PancakeSwap V2 BSC launches use BSC bundle submission for the launch sequence. Sumo still checks landed transactions on-chain instead of relying only on builder status.

## After Launch

When the bundle lands and public trading opens, the profile becomes active and opens in Live Trading.

## Launch Logs

PancakeSwap V2 BSC profiles add a **Launch Logs** tab for deploy, pool creation, bundle submission, confirmation, and post-launch actions.


---

# Four.meme BSC Launch

> Launch a BNB Smart Chain token through Four.meme with fixed launch parameters, optional tax settings, BSC bundle buys, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/fourmeme-bsc-launch
- Markdown: https://docs.sumo.trade/launch-tokens/fourmeme-bsc-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Four.meme BSC** launches on BNB Smart Chain. Four.meme is not a Uniswap-style pool launch: Sumo obtains the create transaction through the Four.meme API, predicts the token address, builds bundle buys against the Four.meme curve, and submits the launch atomically through BSC bundle builders.

![Four.meme BSC token launch buy setup](/images/fourmeme-bsc-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. BNB for token creation, dev buy, bundle buys, gas reserves, and bundle priority fee
3. A launch plan: target supply control, dev buy, bundle wallet count, and optional tax settings
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new BSC wallets / buy aged BSC wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Fixed Four.meme Parameters**
>
> Four.meme fixes total supply at 1 billion tokens with 18 decimals, 80% sale allocation, and PancakeSwap as the migration DEX. The quote asset and its raise target come from Four.meme's published presets: 18 BNB on the native curve, 12,000 on a stablecoin, and a per-stock target on a tokenized stock.

## Launch Flow

### 1. Info

Choose **Four.meme BSC** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                                 |
| ------------------------ | -------- | --------------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Four.meme BSC**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                                |
| **Token Name**           | Yes      | Public token name                                                           |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                        |
| **Image**                | Yes      | JPG or PNG image, uploaded to Four.meme when saved                          |
| **Description**          | No       | Public token description                                                    |
| **X, Telegram, Website** | No       | Public social links included with the Four.meme metadata                    |

Total supply and decimals are fixed by Four.meme and are not edited in the standard Sumo flow.

### 2. Buy Mode

Four.meme uses BNB buy planning against the Four.meme curve.

#### Launch mode

| Mode                  | Description                                                                                                                                                                                                                                                                                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Bundle**            | Dev and bundle wallets buy the curve only, and the launch stops under Four.meme's 80% sale curve so it never completes it.                                                                                                                                                                                                                                               |
| **Graduation Bundle** | Requires a tax token. Dev and bundle wallets buy out the whole 80% sale curve. The last bundle buy takes every remaining offer, which completes the curve and makes Four.meme migrate the token to PancakeSwap V2 inside that same transaction, and **Post-Graduation Wallets** keep buying from the new pair — all in one atomic BSC bundle. The target runs up to 99%. |

The mode and the quote asset are fixed once the draft is saved; start a new draft to change them.

#### Graduation Bundle

A Graduation Bundle turns one BSC block into the whole life of the curve: create, buy it out, migrate, and buy back from the pair.

* **The token must be a tax token.** Selecting Graduation Bundle turns **Tax Controls** on and locks the switch, and the API refuses a graduation draft without it. Only a taxed (Token8) Four.meme token runs TradeStop and the PancakeSwap V2 migration inside the buy that completes the curve; an untaxed token sells its curve out and waits for Four.meme's operator to migrate it minutes later, which would leave the Post-Graduation Wallets with no pair to buy from in the same block. The fee presets and the tax split stay yours to set.
* **The curve leg is fixed at 80%.** Dev buy plus every bundle wallet always sums to Four.meme's full `maxOffers` (800M of the 1B supply). The **Bundle Buy** field is derived: 80% minus the dev buy.
* **The last bundle wallet is the crossing wallet.** It targets whatever offers are left rather than a fixed share, because that is what TokenManager2 fills before it stops trading. Sumo funds it with 2% extra so it still passes the launch-time balance check if the earlier legs over-deliver slightly; Four.meme fills only to the cap and refunds the rest in the same transaction. The crossing wallet must keep a floor of its own — **0.41% of supply** on BNB and stablecoin quotes, &#x2A;*1.21%** on a tokenized stock — which is why the Dev Buy ceiling drops in this mode. That floor is not protection against outside buyers: if someone else's buy lands before the crossing, the launch still migrates, the crossing wallet just receives less than it planned for.
* **Post-Graduation Buy is everything above 80%.** The Supply Control Target runs from `80% + 0.01% per Post-Graduation Wallet` up to &#x2A;*99%**, and the difference is split across the Post-Graduation Wallets. They buy from the migrated pair, which receives 98% of the raise (Four.meme keeps 2% as its migration fee), the liquidity-directed share of accrued curve buy tax, and the unsold token seed. When tax is directed to liquidity, that token seed is slightly below 200M and funding estimates include a margin for the adjustment. Recipient-only tax keeps the nominal seed. Those buys pay the pair's 0.25% fee, and the token's buy tax—always on in this mode—is skimmed from the pair's output as well. Although the controls allow 99%, tax can make targets near that limit unreachable; the launch planner rejects those targets.
* **Bundle and Post-Graduation Wallets share one budget.** The quote asset's gas class sets it — 48 on BNB, 40 on a stablecoin, 30 on a tokenized stock — and the two counts must add up to at most that. Raising one lowers the other's ceiling.
* **On an ERC-20 quote the crossing headroom comes back as the quote token.** Four.meme's Helper swaps the whole funded BNB into the raised token and the manager pulls only what the curve still needs, so the leftover stays in the crossing wallet as the stock or stablecoin, not as BNB. The Funding table's tooltip on that row says roughly how much.
* **Post-launch cleanup.** Four.meme's token restricts wallet-to-wallet transfers until the curve migrates, so holder cleanup is admitted only for a Graduation Bundle that actually migrated; a Bundle launch has no cleanup step. See [Holder cleanup](#holder-cleanup) below.
* **If the crossing completes the sale without migrating** (for example the migration ran out of gas), the profile activates on the curve and Sumo notifies you that the sale is complete and awaiting Four.meme's migration. Four.meme's operator migrates the token to PancakeSwap shortly after; curve buys revert until then, and the profile moves to the pair automatically once the migration lands.

#### Holder cleanup

After the bundle lands, Sumo can move the controlled supply out of the launch wallets and into fresh **holder wallets**, so the token's holder list does not read as a handful of bundle addresses. Pick the method with the **Token Cleanup Method** selector in Buy Setup.

| Method             | Description                                                                                                                                                                                                    |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Off**            | No cleanup. The bundle and post-graduation wallets keep what they bought.                                                                                                                                      |
| **Token Transfer** | Each launch wallet transfers its tokens straight to holder wallets. Cheapest, but the transfer is visible as a transfer on the holder's history.                                                               |
| **Sell / Buy**     | Each launch wallet sells on the migrated PancakeSwap V2 pair and the holder wallet buys the tokens back from it, so every holder's first transaction is an ordinary pair buy. Default for a Graduation Bundle. |

**Why a Bundle launch cannot clean up.** A Four.meme token reverts wallet-to-wallet transfers until TokenManager2 migrates it, and a plain Bundle deliberately stops under the 80% sale curve, so it never migrates inside the launch. Both methods are therefore unavailable: a transfer would revert, and there is no pair to sell into. In Bundle mode the selector shows **Off** and is disabled, and the API refuses a Bundle draft that carries holder cleanup. Switching the draft back to Bundle mode turns cleanup off.

**The tax is paid on every pair leg.** A Graduation Bundle is always a tax token, and the Token8 tax is skimmed on the base side of a pair trade — so Sell / Buy pays the pair's 0.25% fee plus the sell tax on the way out and the pair fee plus the buy tax on the way back in. At the default 5% presets that is roughly 10.5% of the redistributed supply, on top of price impact. The Buy Setup summary shows the result as **Final Supply Control** next to the initial target. Token Transfer pays no pair fee and no tax, because the token's tax applies to pair trades, not to a plain transfer after migration.

**Sources are both launch wallet groups.** Cleanup redistributes from the bundle wallets *and* the Post-Graduation Wallets, so the holder count must be at least one holder per source wallet and at most 100 per source wallet, up to 400 holders in total. Injection wallets take no part in cleanup.

| Setting                            | Description                                                                                                                                                                       |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Token Cleanup Method**           | Off, Token Transfer, or Sell / Buy. Graduation Bundle only; a Bundle draft is locked on Off.                                                                                      |
| **Holder Wallets**                 | Fresh BSC wallets receiving the redistributed supply. Between one and 100 per bundle and post-graduation wallet, up to 400. Defaults to 100.                                      |
| **Native Funds Per Holder Wallet** | Sell / Buy only: BNB sent to each holder wallet whose balance is below the cleanup buy's gas requirement. Defaults to 0.01 BNB. Leave empty to skip automatic holder gas funding. |
| **Cleanup Delay**                  | Advanced control: seconds between each launch wallet's cleanup sequence. Defaults to 5.                                                                                           |
| **Holder Supply Jitter**           | Advanced control: randomizes the token amounts each holder wallet receives, 0-100%. Defaults to 10%.                                                                              |

#### Quote asset

A Four.meme curve is priced in one **raised token** — the asset every buy pays into. Sumo offers the presets Four.meme publishes as launchable:

| Option               | Description                                                                                                                                                                                                                              |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **BNB**              | The native curve. Every buy pays BNB straight into the curve, and the dev buy rides on the create transaction.                                                                                                                           |
| **Stablecoins**      | USD1, USDT, and UUSD. Each curve raises 12,000 of the stablecoin.                                                                                                                                                                        |
| **Tokenized stocks** | Four.meme's bStocks — NVDAB, SPCXB, QQQB, GMEB, FLNCB, DJTB, MRNAB, and HOODB. Each has its own raise target in that stock (60 NVDAB, 90 SPCXB, 16 QQQB, and so on), so a "Stock Meme" is priced and graduates in the stock, not in BNB. |

Launch wallets stay funded in **BNB** for every quote. On an ERC-20 quote each buy goes through Four.meme's Helper, which swaps BNB into the raised token on the way in, so no wallet ever has to hold the stock or stablecoin. Sumo reads the live BNB-to-quote rate to size each wallet: while it is loading the BNB requirement reads "Quoting"; if it cannot be priced, the launch cannot be sized and the draft is refused.

Two things change on an ERC-20 quote:

* **The dev buy becomes its own transaction.** The create carries no pre-sale, and the dev wallet buys immediately after it, so the dev wallet keeps gas for that buy on top of its deploy reserve.
* **The bundle is smaller.** Each hop buy costs more gas than a native curve buy, so the wallet budget follows the quote: 48 wallets on BNB, 40 on a stablecoin, 30 on a tokenized stock. Lowering the budget re-clamps the Bundle Wallets count.

The quote asset is fixed once the draft is saved; start a new draft to change it.

| Setting                           | Description                                                                                                                                                                                                                                                                                                                                                                   |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**         | Total supply controlled by dev and bundle wallets. In **Bundle** mode Four.meme's sale curve completes at 80% of supply and a launch must leave part of it unsold, so the ceiling is 79.6% on BNB and stablecoin quotes and 78.8% on a tokenized stock. In **Graduation Bundle** mode it is the curve plus the pair, from `80% + 0.01% per Post-Graduation Wallet` up to 99%. |
| **Dev Buy**                       | First buy on the curve, defaulting to 1%. On BNB it rides on the create transaction; on a catalogue quote it is its own transaction right after the create. In a Graduation Bundle its ceiling is 80% minus the crossing wallet's floor minus 0.01% for every other bundle wallet.                                                                                            |
| **Bundle Buy**                    | Allocation assigned across bundle wallets after the create transaction. In a Graduation Bundle it is 80% minus the dev buy: the wallets buy the whole sale curve.                                                                                                                                                                                                             |
| **Post-Graduation Buy**           | Graduation Bundle only, read-only: the Supply Control Target above 80%, bought from the migrated PancakeSwap V2 pair.                                                                                                                                                                                                                                                         |
| **Post-Graduation Wallets**       | Graduation Bundle only: BSC wallets buying from the pair after the crossing buy migrates it. Shares the quote asset's wallet budget with Bundle Wallets.                                                                                                                                                                                                                      |
| **Quote Asset**                   | Asset the curve prices every buy in: native BNB or a catalogue stablecoin / tokenized stock. Locked after the draft is saved.                                                                                                                                                                                                                                                 |
| **Bundle Wallets**                | Number of BSC wallets used for bundle buys. The budget follows the quote asset: up to 48 on BNB, 40 on a stablecoin, 30 on a tokenized stock. A Graduation Bundle shares that budget with the Post-Graduation Wallets.                                                                                                                                                        |
| **Estimated BNB Required**        | Create value, dev buy, bundle buys, gas reserve, and funding buffers when enabled. Quote-denominated buys are converted at the live hop rate.                                                                                                                                                                                                                                 |
| **Estimated `<QUOTE>` Required**  | On a catalogue quote: the raised token the ordered buys need on the curve. The BNB above is what Four.meme's Helper converts into it.                                                                                                                                                                                                                                         |
| **Estimated Market Cap**          | Estimated from the selected quote's curve math, its USD price, and the BNB/USD reference price. In a Graduation Bundle it comes from the migrated pair's spot price after the planned post-graduation buys.                                                                                                                                                                   |
| **Funds Per Bundle Wallet**       | BNB gas reserve per bundle wallet.                                                                                                                                                                                                                                                                                                                                            |
| **Injection Wallets**             | Optional extra wallets, up to 100, funded with BNB for activity after launch. They do not buy in the launch or take part in cleanup.                                                                                                                                                                                                                                          |
| **Funds Per Injection Wallet**    | Shown when Injection Wallets is above 0. BNB sent to each injection wallet during funding. Defaults to 0.                                                                                                                                                                                                                                                                     |
| **CEX Funding**                   | Optional Husher funding path for distributing BNB.                                                                                                                                                                                                                                                                                                                            |
| **CEX Funding Buffer Per Wallet** | Extra BNB added per wallet when CEX funding is enabled.                                                                                                                                                                                                                                                                                                                       |
| **Advanced Controls**             | Supply jitter and BSC bundle priority fee.                                                                                                                                                                                                                                                                                                                                    |

### Tax Controls

Four.meme tax settings are different from the shared Uniswap-style tax contract.

| Setting            | Description                                                                          |
| ------------------ | ------------------------------------------------------------------------------------ |
| **Buy Fee Rate**   | Four.meme buy fee preset. Allowed values are 1%, 3%, 5%, and 10%.                    |
| **Sell Fee Rate**  | Four.meme sell fee preset. Allowed values are 1%, 3%, 5%, and 10%.                   |
| **Burn Rate**      | Percentage of collected tax allocated to burn.                                       |
| **Dividend Rate**  | Percentage of collected tax allocated to holder dividends.                           |
| **Recipient Rate** | Percentage of collected tax allocated to the tax recipient wallet. Defaults to 100%. |
| **Liquidity Rate** | Read-only remainder after burn, dividend, and recipient rates.                       |
| **Tax Wallet**     | Wallet used as the tax recipient when tax is enabled.                                |

The four split rates must add up to 100%. In the wizard, liquidity rate is derived from the other three values.

### 3. Wallets

Add, import, or generate wallets for each required BSC role.

| Role                        | Description                                                                                                                                                                        |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**              | Authenticates with Four.meme, uploads metadata, creates the token, pays create value, and performs the dev buy.                                                                    |
| **Bundle Wallets**          | Execute Four.meme curve buys in the BSC launch bundle.                                                                                                                             |
| **Post-Graduation Wallets** | Graduation Bundle only. Buy the launched token from the migrated PancakeSwap V2 pair in the same block.                                                                            |
| **Holder Wallets**          | Graduation Bundle with cleanup on. Receive the bundle and post-graduation wallets' supply after the migration. On Sell / Buy they are also funded with BNB for their own pair buy. |
| **Injection Wallets**       | Optional wallets funded with BNB for activity after launch. They take no part in the launch or cleanup.                                                                            |
| **Tax Wallet**              | Required only when Four.meme tax is enabled.                                                                                                                                       |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Sniper wallets are not used by Four.meme BSC launches, and holder wallets appear only for a Graduation Bundle with [holder cleanup](#holder-cleanup) enabled.

### 4. Funding

Save the draft before funding. Sumo uploads the image to Four.meme when needed and stores the Four.meme image URL on the launch draft.

The funding table tracks BNB requirements for token creation, dev buy, bundle buys, gas reserves, and BSC bundle priority fee. With Sell / Buy holder cleanup it also carries one fixed BNB row per holder wallet for its cleanup buy. If CEX funding is enabled, deposit the estimated BNB into the funding wallet and use **Fund** to distribute it through Husher. If CEX funding is disabled, fund the dev and bundle wallets directly and use **Check Balances**.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview shows:

* Four.meme metadata and uploaded image status
* Predicted token address
* Dev and bundle wallet counts
* BNB funding rows
* Supply split across dev and bundle buys
* Optional tax configuration and tax wallet

When launched, Sumo builds the Four.meme create transaction, appends bundle buys, simulates the BSC bundle, submits it to supported BSC builders, and confirms the landed transactions on-chain.

## After Launch

When the bundle lands, the profile becomes active and opens in Live Trading. Four.meme profiles use the Four.meme connector for quotes, trades, migration progress, and post-launch spot-price data.

## Launch Logs

Four.meme profiles add a **Launch Logs** tab for metadata upload, create transaction preparation, bundle simulation, bundle submission, and confirmation.

## Further Reading

* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — this launchpad's curve overlaid on every other supported launchpad, with graduation math
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — simulate launch cost, starting market cap, and supply held for this launchpad


---

# Flap BSC Launch

> Launch a BNB Smart Chain token through Flap with a BNB or catalogue quote asset, Bundle or Graduation Bundle mode, Tax V3 controls, dividend distribution, BSC bundle buys, and starter strategies.

- URL: https://docs.sumo.trade/launch-tokens/flap-bsc-launch
- Markdown: https://docs.sumo.trade/launch-tokens/flap-bsc-launch.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports **Flap BSC** launches on BNB Smart Chain. Flap is a bonding-curve launchpad rather than a Uniswap-style pool launch: Sumo builds the Flap Portal create call, predicts the token address, plans bundle buys against the Flap curve, and submits the launch atomically through BSC bundle builders. Flap launch tokens deploy from the **Tax V3** implementation, which adds tax duration, anti-farmer, and dividend behavior on top of the buy/sell fee split.

![Flap BSC token launch buy setup](/images/flap-bsc-launch-buy-setup.png)

## Prerequisites

Before launching, make sure you have:

1. Token metadata ready: name, ticker, image, description, and social links
2. BNB for token creation, dev buy, bundle buys, gas reserves, and bundle priority fee
3. A launch plan: supply control target, dev buy, bundle wallet count, holder cleanup preference, and tax settings
4. A wallet plan: use ready wallets from private keys, [Wallet Farm](/wallet-farm/overview), or another profile, or create new BSC wallets / buy aged BSC wallets through [Wallet Marketplace](/wallets/wallet-marketplace) during the wizard

> **Fixed Flap Parameters**
>
> Flap fixes total supply at 1 billion tokens with 18 decimals. Total supply and decimals are set automatically when you choose the launchpad and are not edited in the standard Sumo flow. The quote asset the curve is priced in is yours to choose: native BNB or a supported token from the quote picker.

## Launch Flow

### 1. Info

Choose **Flap BSC** in the Launchpad field, then enter the token and profile details.

| Field                    | Required | Description                                                            |
| ------------------------ | -------- | ---------------------------------------------------------------------- |
| **Launchpad**            | Yes      | Select **Flap BSC**. The launchpad is locked after the draft is saved. |
| **Profile Name**         | Yes      | Internal Sumo profile name used after launch                           |
| **Token Name**           | Yes      | Public token name                                                      |
| **Ticker**               | Yes      | Public token symbol, auto-uppercased                                   |
| **Image**                | Yes      | JPG or PNG image, uploaded with the Flap metadata                      |
| **Description**          | No       | Public token description                                               |
| **X, Telegram, Website** | No       | Public social links included with the Flap metadata                    |

### 2. Buy Mode

Flap plans every buy against the Flap bonding curve in the selected quote asset. Launch wallets are always funded in BNB: when the quote is an ERC-20, the Flap Portal converts each buy into the quote on the way in (its native-to-quote hop), so there is no separate funding swap.

#### Launch mode

| Mode                  | Description                                                                                                                                                                                                                                                                                       |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Bundle**            | Dev and bundle wallets buy the curve only, capped one point under Flap's 80% graduation threshold (79%).                                                                                                                                                                                          |
| **Graduation Bundle** | Dev and bundle wallets buy out the curve exactly (80%). The last bundle buy crosses the threshold, Flap migrates the token to PancakeSwap V2 inside that transaction, and **Post-Graduation Wallets** keep buying from the new pair, all inside one atomic BSC bundle. The target runs up to 99%. |

The mode and the quote asset are fixed once the draft is saved; start a new draft to change them.

#### Quote asset

| Option                     | Description                                                                                                                                                         |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **BNB**                    | The native curve. Every buy pays BNB straight into the curve.                                                                                                       |
| **Stablecoins and crypto** | USDT, USD1, U, BTCB, SOL, ETH, DOGE, and 币安人生. Wallets stay funded in BNB.                                                                                          |
| **Tokenized assets**       | XAUT, 27 bStocks, and six Ondo tokens: BILIon, DISon, FXIon, GMEon, PDDon, and SQQQon. Each quote has its own curve profile, which Sumo reads live from the Portal. |

The picker offers 42 ERC-20 quotes whose BNB conversion routes are supported by Flap. Other tokens in Flap's Custom section, such as SHIB, require a separate launch flow and are not offered here.

Sumo shows the live BNB-to-quote rate of the Portal hop next to the estimates. While the rate is still loading the BNB requirement reads "Quoting"; if the Portal cannot price a quote, the launch cannot be sized.

Large hop swaps can require more BNB than the funding estimate because of price impact. The launch balance check uses the simulated plan and blocks submission if a wallet needs a top-up.

| Setting                            | Description                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supply Control Target**          | Bundle: total supply bought by dev and bundle wallets, up to 79%. Graduation Bundle: the curve (80%) plus the Post-Graduation Buy, up to 99%.                                                                                                                                                                                                                                                                                    |
| **Estimated BNB Required**         | Create value, dev buy, bundle buys, post-graduation buys, gas reserves, bundle priority fee, and funding buffers when enabled. Quote-denominated buys are converted at the live hop rate.                                                                                                                                                                                                                                        |
| **Estimated `<QUOTE>` Required**   | On a catalogue quote: the quote the ordered buys need on the curve and, in a Graduation Bundle, on the pair.                                                                                                                                                                                                                                                                                                                     |
| **Estimated Market Cap**           | Bundle: the curve's marginal price after the planned buys. Graduation Bundle: the migrated pair's spot price after the post-graduation buys. Uses the BNB/USD reference price and the hop rate.                                                                                                                                                                                                                                  |
| **Dev Buy**                        | First buy on the curve. On BNB it rides on the create transaction; on a catalogue quote it is its own transaction right after the create. In a Graduation Bundle it leaves every bundle wallet at least 0.01% of the curve.                                                                                                                                                                                                      |
| **Bundle Buy**                     | Read-only allocation assigned across bundle wallets. In a Graduation Bundle it is the rest of the curve up to 80%.                                                                                                                                                                                                                                                                                                               |
| **Post-Graduation Buy**            | Graduation Bundle only. Read-only: the Supply Control Target above 80%, bought from the PancakeSwap pair.                                                                                                                                                                                                                                                                                                                        |
| **Post-Graduation Wallets**        | Graduation Bundle only. Wallets buying from the pair after the crossing buy, at least one.                                                                                                                                                                                                                                                                                                                                       |
| **Bundle Wallets**                 | Number of BSC wallets used for curve buys. Bundle and Post-Graduation Wallets share one atomic bundle whose size follows the quote asset: 48 wallets on BNB, 40 on stablecoins and crypto quotes, 30 on tokenized stocks and XAUT, so the bundle fits one BSC block. In a Graduation Bundle the last bundle wallet makes the crossing buy and must hold at least 0.41% of supply (1.21% on a stock quote).                       |
| **Holder Wallets**                 | Post-launch token destinations for holder cleanup. Up to 400.                                                                                                                                                                                                                                                                                                                                                                    |
| **Funds Per Bundle Wallet**        | BNB gas reserve per bundle wallet.                                                                                                                                                                                                                                                                                                                                                                                               |
| **Injection Wallets**              | Optional extra wallets, up to 100, funded with BNB for activity after launch. They do not buy in the launch or take part in cleanup.                                                                                                                                                                                                                                                                                             |
| **Funds Per Injection Wallet**     | Shown when Injection Wallets is above 0. BNB sent to each injection wallet during funding. Defaults to 0.                                                                                                                                                                                                                                                                                                                        |
| **Token Cleanup Method**           | Off, Token Transfer, or Sell / Buy. After the Flap bundle lands, moves the launch wallets' token balances into fresh holder wallets. Sell / Buy appears only for a Graduation Bundle: it sells from the launch wallets and buys for the holder wallets on the migrated PancakeSwap V2 pair through the shared cleanup contract. Each holder wallet needs BNB for its buy, and the launch is refused until every holder holds it. |
| **Native Funds Per Holder Wallet** | Shown with Sell / Buy. BNB sent to each holder wallet during funding for its cleanup buy, seeded at 0.01 BNB.                                                                                                                                                                                                                                                                                                                    |
| **CEX Funding**                    | Optional Husher funding path for distributing BNB.                                                                                                                                                                                                                                                                                                                                                                               |
| **CEX Funding Buffer Per Wallet**  | Extra BNB added per wallet when CEX funding is enabled.                                                                                                                                                                                                                                                                                                                                                                          |
| **Advanced Controls**              | Bundle supply jitter, BSC bundle priority fee, cleanup delay, and holder supply jitter.                                                                                                                                                                                                                                                                                                                                          |

### Tax Controls

Flap Tax V3 settings are configured per launch. Buy and sell taxes are selected from fixed presets, and either may be 0% as long as the other is positive.

| Setting                  | Description                                                                                                                         |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Buy Tax**              | Tax applied to Flap bonding-curve buys. Options: Off (0%), 1%, 3%, 5%, 10%.                                                         |
| **Sell Tax**             | Tax applied to Flap bonding-curve sells. Options: Off (0%), 1%, 3%, 5%, 10%.                                                        |
| **Burn**                 | Percentage of collected tax allocated to burns.                                                                                     |
| **Dividend**             | Percentage of collected tax allocated to holder dividends.                                                                          |
| **Tax Wallet**           | Percentage of collected tax sent to the configured tax wallet.                                                                      |
| **Liquidity**            | Read-only remainder after burn, dividend, and tax wallet rates.                                                                     |
| **Tax Duration**         | Duration of the configured taxes, in days. Defaults to and cannot be lower than 365; maximum 36,500.                                |
| **Anti-Farmer Duration** | After graduation, taxes apply across every registered pool for this many days. Defaults to and cannot be lower than 1; maximum 365. |

The four distribution rates must add up to 100%; liquidity is derived from the other three.

> **Tax Duration Minimum**
>
> The deployed Flap Portal requires at least one year of tax duration, at least one day of anti-farmer protection, and a tax duration that runs at least 24 hours beyond the anti-farmer window. The wizard raises the tax duration minimum as you increase the anti-farmer duration, so set anti-farmer first.

#### Dividend Settings

These appear only when the **Dividend** allocation is above 0%.

| Setting                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dividend Token**        | On a BNB quote: choose native BNB, the launched token, or a featured Flap-supported BSC route from the searchable token catalogue. Token logos, symbols, names, and categories are shown in the selector. A custom ERC-20 address can still be entered and is validated against Flap's SwapRegistry during launch simulation. On a catalogue quote: Flap pays dividends only in the quote itself (the default) or in the launched token. |
| **Minimum Share Balance** | Minimum launched-token balance eligible for dividends, entered in 18-decimal atomic units. Minimum 10,000 tokens.                                                                                                                                                                                                                                                                                                                        |

The selector only showcases tokens whose WBNB dividend conversion routes currently pass Flap's launch simulation. Custom ERC-20 addresses remain available for newly registered routes and are checked by the same simulation before launch. Pre-existing drafts keep recognizable token metadata while requiring that route check.

### 3. Wallets

Add, import, or generate wallets for each required BSC role.

| Role                        | Description                                                                                                                                                                        |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dev Wallet**              | Creates the token through the Flap Portal, pays create value, and performs the dev buy.                                                                                            |
| **Bundle Wallets**          | Execute Flap curve buys in the BSC launch bundle.                                                                                                                                  |
| **Injection Wallets**       | Optional wallets funded with BNB for activity after launch. They take no part in the launch or cleanup.                                                                            |
| **Post-Graduation Wallets** | Graduation Bundle only. Buy from the PancakeSwap pair inside the same bundle, after the crossing buy migrates the token. Created active, and included in token cleanup as sources. |
| **Tax Wallet**              | Required only when a buy or sell tax is enabled. Receives the tax wallet share of collected tax.                                                                                   |
| **Holder Wallets**          | Receive tokens through post-launch cleanup when token cleanup is enabled.                                                                                                          |

You can use ready wallets, create new wallets, or buy aged wallets at this step. Ready-wallet paths include importing private keys, pulling wallets from [Wallet Farm](/wallet-farm/overview), or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from [Wallet Marketplace](/wallets/wallet-marketplace).

Freeze and sniper wallets are not used by Flap BSC launches.

### 4. Funding

Save the draft before funding. The funding table tracks BNB requirements for token creation, dev buy, bundle buys, post-graduation buys, gas reserves, and the BSC bundle priority fee. Every row is BNB, whatever the quote asset: the Portal hop converts each buy at launch time. Each buy is funded with the headroom the launch signs: 2% on the crossing buy, refunded by the Portal past the threshold, and 1% on every buy priced through the hop.

If CEX funding is enabled, deposit the estimated BNB into the funding wallet and use **Fund** to distribute it through Husher. If CEX funding is disabled, fund the dev, tax, and bundle wallets directly and use **Check Balances**.

### 5. Strategies

Optionally add starter strategies to the profile before launch. You can configure [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), and [Limit Order](/strategies/limit-orders) strategies by hand, or apply a strategy preset: Sumo ships built-in **Hyped**, **Standard**, and **Staircase** presets, and your org can save its own presets for reuse across launches and imports. Strategies are saved with the draft and can be reviewed after the token is live.

### 6. Launch Preview

The preview shows:

* Supply control, dev buy, and bundle buy split
* Estimated BNB required and estimated market cap
* Buy / sell tax, tax duration, and anti-farmer duration
* Burn, dividend, tax wallet, and liquidity distribution rates
* Dividend token and minimum share balance when the dividend allocation is above 0%

When launched, Sumo builds the Flap create call, plans every buy against a full-bundle simulation of the Portal (which is how the BNB each hop-priced buy needs and the migrated pair's reserves are sized), appends the buys in order, simulates the BSC bundle, submits it to supported BSC builders, and confirms the landed transactions on-chain. A Graduation Bundle activates the profile directly on the PancakeSwap pair. Token cleanup runs afterwards when enabled.

## After Launch

When the bundle lands, the profile becomes active and opens in Live Trading. Flap profiles use the Flap connector for quotes, trades, graduation progress, and post-launch spot-price data.

## Launch Logs

Flap profiles add a **Launch Logs** tab for metadata preparation, create transaction building, bundle simulation, bundle submission, confirmation, and holder cleanup.

## Further Reading

* [What Are Memecoin Bonding Curves?](https://blog.sumo.trade/what-is-a-bonding-curve/) — this launchpad's curve overlaid on every other supported launchpad, with graduation math
* [How Much Does It Cost to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-simulator/) — simulate launch cost, starting market cap, and supply held for this launchpad


---

# Strategies Overview

> An introduction to Sumo's automated trading strategies.

- URL: https://docs.sumo.trade/strategies/overview
- Markdown: https://docs.sumo.trade/strategies/overview.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo provides automated strategies for market making plus Instant Trade for one-off manual interventions. You can run multiple strategies simultaneously across different wallets or wallet groups.

> **Video: Getting Started with Sumo Trading Strategies**
>
> An overview of creating, managing, and activating Counter Trade, DCA, and Limit Order strategies.
>
> https://www.youtube.com/watch?v=RnDACIB77ds

## Strategy Types

| Strategy                                       | What It Does                                                  | Best For                             |
| ---------------------------------------------- | ------------------------------------------------------------- | ------------------------------------ |
| [**Counter Trade**](/strategies/counter-trade) | Automatically counters external buys/sells to stabilize price | Price stability, market making       |
| [**DCA**](/strategies/dca)                     | Executes trades at regular intervals                          | Gradual accumulation or distribution |
| [**Limit Orders**](/strategies/limit-orders)   | Executes trades when market cap conditions are met            | Buying dips, selling at targets      |
| [**Instant Trade**](/strategies/instant-trade) | One-click manual buys and sells                               | Quick market interventions           |

## Creating a Strategy

1. Navigate to your profile's **Strategies** tab
2. Click **+ Create Strategy**
3. Select the strategy type (Counter Trade, DCA, or Limit Order)
4. Configure the strategy parameters
5. Choose which wallets to use
6. Set slippage and, on supported EVM profiles, private relay protection
7. Click **Create Strategy**
8. Review the strategy, then activate it when you're ready

## Strategy Presets

The Strategies step of the token launch and import wizards includes a preset bar that configures a full set of strategies in one click. Each preset tile shows a projected hourly volume estimate before you apply it.

Three built-in presets ship with Sumo, ordered by intensity:

| Preset        | Setup                                                                                 |
| ------------- | ------------------------------------------------------------------------------------- |
| **Hyped**     | Aggressive counter-sell plus larger DCA buy and sell legs for high-attention launches |
| **Standard**  | Moderate counter-sell with smaller DCA legs for steady market making                  |
| **Staircase** | Counter-sell and counter-buy pairing with minimal DCA legs for stepped price support  |

You can also save your own: **Save preset** stores the currently configured strategies as an org-level preset with a name and icon, reusable across every launch and import in your organization. Presets can be renamed or deleted from the preset menu, and saving requires the trader role or higher.

Presets whose amounts are denominated in a quote or native asset are pinned to the project they were saved from; when applied on a project with a different quote or native asset, those entries are skipped and Sumo tells you how many applied. USD-denominated presets apply everywhere.

## Managing Strategies

### Activate / Deactivate

New strategies are created inactive so you can review them before they run. Each strategy has a status toggle: activate it to start execution, or deactivate it to pause without deleting.

To change a strategy's settings, pause it first. Active strategies can be opened for review, but Sumo keeps their settings locked while they are running.

### Filter View

Use the strategy filter to view strategies by type:

* **All** — Show every strategy
* **Counter Trade** — Counter trade strategies only
* **DCA** — DCA strategies only
* **Limit Order** — Limit order strategies only

### Clone a Strategy

Click the clone icon on any strategy to duplicate it. You can clone to the same profile or a different one, and assign different wallets.

### Edit a Strategy

Click the edit icon to modify a paused strategy's parameters. The strategy type cannot be changed after creation — create a new one instead.

### Delete a Strategy

Click the trash icon to delete a strategy you no longer want to use. Sumo asks for confirmation before deleting it.

Deleting a strategy removes it from the active strategy list, but keeps its historical trades and reporting data. Use delete when a strategy should no longer be reused or reactivated, and use deactivate when you only want to pause it temporarily.

## Wallet Assignment

When creating a strategy, you choose which wallets execute the trades:

* **All wallets** — The strategy uses every active wallet in the profile
* **Wallet group** — The strategy uses only wallets in the selected group
* **Individual wallet** — The strategy uses a single specific wallet

Only active assigned wallets are used for execution. This lets you run different strategies on different subsets of wallets. For example, you might run Counter Trade on one group and DCA on another.

## Strategy Metrics

Each strategy in the list shows **Net Change** — the cumulative base and quote asset changes from all trades executed by that strategy. DCA and Limit Order rows also show budget progress when a spend budget is configured.

- [Counter Trade](/strategies/counter-trade): Sumo's flagship strategy for price stability.

- [DCA](/strategies/dca): Scheduled buys or sells at regular intervals.

- [Limit Orders](/strategies/limit-orders): Conditional trades based on market cap.

- [Instant Trade](/strategies/instant-trade): One-click manual trading from the dashboard.

## Further Reading

* [Counter Trading: Sell Tokens Without Hurting the Chart](https://blog.sumo.trade/counter-trade-strategy/) — the flagship strategy explained from a founder's point of view
* [How to Choose a Market Making Bot](https://blog.sumo.trade/how-to-choose-a-market-making-bot/) — landing rates, anti-MEV, routing, and the hidden costs of market making tools
* [What Is MEV and Why Do Token Teams Care?](https://blog.sumo.trade/mev-protection-for-traders/) — how serious trading systems defend against frontrunners and sandwich bots


---

# Counter Trade

> Sumo's flagship strategy that counters external trades to maintain price stability.

- URL: https://docs.sumo.trade/strategies/counter-trade
- Markdown: https://docs.sumo.trade/strategies/counter-trade.md
- Docs index: https://docs.sumo.trade/llms.txt

Counter Trade is Sumo's flagship strategy. It monitors your token's pool for external trades and automatically executes a counter-trade to offset the price impact — buying when others sell, and selling when others buy.

> **Video: Counter Trade Deep Dive**
>
> A focused walkthrough of trigger thresholds, capture percentages, delay settings, and price-stability workflows.
>
> https://www.youtube.com/watch?v=spY_kz9aMFk

![Create Counter Trade strategy](/images/strategy-counter-trade.png)

## How It Works

1. Sumo watches your token's pool for external trades in real time
2. When a trade exceeds your trigger threshold, Sumo calculates a counter-trade
3. The counter-trade executes from your wallets, offsetting the price movement
4. MEV bots are automatically excluded (when enabled) to avoid counter-trading against bots

## Strategy Types

Counter Trade has two directions:

* **Auto Buy Into Sells** — When someone sells your token, Sumo automatically buys to support the price
* **Auto Sell Into Buys** — When someone buys your token, Sumo automatically sells to take profit or manage supply

You can run both simultaneously to maintain a tight price range.

## Configuration

### Trigger Size

The minimum (and optional maximum) external trade size that triggers a counter-trade. You can set this in:

* **USD** — Dollar value of the trade
* **Quote** (e.g. SOL, WETH, WBNB) — Quote asset amount
* **Token** — Number of tokens traded

| Field   | Description                                                       |
| ------- | ----------------------------------------------------------------- |
| **Min** | Minimum trade size to trigger a counter (required)                |
| **Max** | Maximum trade size to counter (optional — leave empty for no cap) |

> **Filter Out Noise**
>
> Set the minimum trigger high enough to ignore small trades that don't meaningfully impact price. This keeps your wallets from being drained by dust trades.

### Capture Percentage

How much of the detected trade to counter:

| Field               | Description                                                   |
| ------------------- | ------------------------------------------------------------- |
| **Capture Min (%)** | Minimum percentage of the trade to counter (required, 1–100%) |
| **Capture Max (%)** | Maximum percentage (optional — for a randomized range)        |

For example, if someone sells $1,000 of your token and capture is set to 40%, Sumo buys back $400 worth.

Setting a capture range (e.g. 30–50%) randomizes the counter amount, making your trading pattern less predictable on-chain.

### Delay

How long to wait after detecting a trade before executing the counter:

* **None** — Execute immediately
* **10s / 15s / 20s** — Preset delays
* **Custom** — Enter any delay in seconds

A short delay can help avoid appearing as an obvious counter-trade on-chain.

### Exclude MEV

When enabled, Sumo automatically identifies and ignores trades from known MEV bots. This prevents your strategy from counter-trading against sandwich attacks and other MEV activity.

MEV wallets are managed in [Profile Settings](/getting-started/profile-settings) — both manually added and auto-detected wallets.

### Wallet

Choose which wallets execute the counter-trades:

* **All wallets** — Rotate across all active wallets
* **Wallet group** — Use wallets from a specific group
* **Individual wallet** — Use a single wallet

### Slippage

Set the maximum price movement Sumo should allow for each counter-trade. Use a tighter value when you want stricter execution, and a wider value when fast execution matters more than exact output.

### Private Relay

On supported EVM profiles, you can enable **MEV protection using Private Relays**. This routes eligible counter-trades through private relays to reduce public mempool exposure.

## Strategy List View

Active counter trade strategies display:

| Column         | Description                                                  |
| -------------- | ------------------------------------------------------------ |
| **Trigger**    | The trigger range (e.g. "$500–$10,000")                      |
| **Capture**    | Capture percentage or range (e.g. "40%" or "30–50%")         |
| **Delay**      | Execution delay (e.g. "15s" or "None")                       |
| **Net Change** | Cumulative base and quote asset changes from executed trades |
| **Status**     | Whether the strategy is active, paused, completed, or failed |

## Tips

* Start with **Auto Buy Into Sells** to support your token's price, then add **Auto Sell Into Buys** once you're comfortable
* Use a capture range (e.g. 30–50%) instead of a fixed percentage to make trades less predictable
* Enable **Exclude MEV** to avoid wasting funds counter-trading bots
* Set a reasonable trigger minimum to filter out small trades
* Pause the strategy before changing its settings

- [DCA](/strategies/dca): Schedule regular buys or sells at fixed intervals.

- [Impact Calculator](/strategies/impact-calculator): Estimate the price impact of a trade before executing.

## Further Reading

* [Counter Trading: Sell Tokens Without Hurting the Chart](https://blog.sumo.trade/counter-trade-strategy/) — how counter trading lets founders take profit without printing red candles
* [What Is MEV and Why Do Token Teams Care?](https://blog.sumo.trade/mev-protection-for-traders/) — what sandwich bots take from your trades and why Exclude MEV matters


---

# DCA

> Dollar-cost averaging strategy for scheduled, automated trades.

- URL: https://docs.sumo.trade/strategies/dca
- Markdown: https://docs.sumo.trade/strategies/dca.md
- Docs index: https://docs.sumo.trade/llms.txt

DCA (Dollar Cost Averaging) executes trades at regular intervals, spreading your buying or selling over time to reduce the impact of price volatility.

> **Video: DCA Strategies Deep Dive**
>
> A walkthrough of configuring DCA buys and sells, intervals, budgets, durations, and jitter.
>
> https://www.youtube.com/watch?v=yk6gVUyLfL4

![Create DCA strategy](/images/strategy-dca.png)

## How It Works

1. You configure a trade amount, frequency, and duration
2. Sumo executes a trade at each interval
3. Jitter randomizes both the timing and amount to make trades less predictable on-chain
4. The strategy runs until the duration or budget is reached, or you deactivate it

## Strategy Types

* **Buy** — Accumulate tokens over time by buying at regular intervals
* **Sell** — Distribute tokens over time by selling at regular intervals

## Configuration

### Trade Amount

The size of each individual trade. Select the unit:

* **USD** — Dollar value per trade
* **Quote** (e.g. SOL, WETH, WBNB) — Quote asset amount per trade
* **Token** — Number of tokens per trade

### Spend Budget

Optional maximum total amount to trade before the strategy stops. You can set the budget in **USD**, **Quote**, or **Token** units. Leave empty for no budget limit.

### Frequency

How often the strategy executes a trade:

* Enter a number and select the unit: **Seconds**, **Minutes**, **Hours**, or **Days**
* Example: "5 Minutes" means one trade every 5 minutes

### Jitter

Randomize the trade timing and amount to make your pattern less detectable on-chain:

| Field                       | Description                                                                                                                     |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Trade Amount Jitter (%)** | Randomizes the trade size by this percentage. E.g. 10% jitter on a $500 trade means each trade is between $450–$550.            |
| **Interval Jitter (%)**     | Randomizes the interval by this percentage. E.g. 10% jitter on a 60s interval means trades execute between 54–66 seconds apart. |

### Duration

How long the strategy runs:

* **Cycles** — Execute a fixed number of trades, then stop
* **Infinite** (∞) — Run indefinitely until manually deactivated

### Wallet

Choose which wallets execute the trades — all wallets, a wallet group, or an individual wallet.

### Slippage

Set the maximum price movement Sumo should allow for each DCA trade.

### Private Relay

On supported EVM profiles, you can enable **MEV protection using Private Relays**. This routes eligible trades through private relays to reduce public mempool exposure.

### Sell All Available Tokens

For DCA Sell strategies, you can enable **Sell all available tokens on insufficient balance**. If a planned sell is larger than the wallet's token balance, Sumo retries once using the wallet's available token balance instead of simply skipping that wallet.

## Strategy List View

Active DCA strategies display:

| Column           | Description                                            |
| ---------------- | ------------------------------------------------------ |
| **Trade Amount** | Amount per trade with jitter range (e.g. "$450–$550")  |
| **Interval**     | Time between trades with jitter range (e.g. "54s–66s") |
| **Duration**     | Number of cycles or ∞ for infinite                     |
| **Budget**       | Spend progress when a budget is configured             |
| **Net Change**   | Cumulative base and quote asset changes                |

## Use Cases

* **Accumulating a position** — DCA Buy to gradually build a token position without spiking the price
* **Distributing tokens** — DCA Sell to offload tokens smoothly over time
* **Market activity** — Run both buy and sell DCA strategies to maintain consistent trading activity on your token
* **Low-balance cleanup** — Use sell-all-on-insufficient-balance when you want a DCA Sell to drain smaller wallet balances gracefully

- [Limit Orders](/strategies/limit-orders): Execute trades when market cap conditions are met.

- [Counter Trade](/strategies/counter-trade): Automatically counter external trades to stabilize price.


---

# Limit Orders

> Execute trades when market cap conditions are met.

- URL: https://docs.sumo.trade/strategies/limit-orders
- Markdown: https://docs.sumo.trade/strategies/limit-orders.md
- Docs index: https://docs.sumo.trade/llms.txt

Limit Orders execute trades when your token's market cap falls within a specified range. This lets you set up conditional buy and sell orders that trigger automatically based on market conditions.

> **Video: Limit Orders Deep Dive**
>
> A walkthrough of market-cap triggers, buy and sell ranges, spend budgets, and automated execution frequency.
>
> https://www.youtube.com/watch?v=Wx-1b8dzOco

![Create Limit Order strategy](/images/strategy-limit-order.png)

## How It Works

1. You set a market cap range (min and/or max) and a trade amount
2. Sumo monitors your token's market cap in real time
3. When the market cap is within your specified range, the strategy starts executing trades at the configured frequency
4. Trades stop when the market cap moves outside the range, the duration is reached, or the budget is spent

## Strategy Types

* **Buy** — Buy when market cap drops to your target range (buy the dip)
* **Sell** — Sell when market cap rises to your target range (take profit)

## Configuration

### Trade Amount

The size of each individual trade. Select the unit: **USD**, **Quote** (e.g. SOL, WETH, WBNB), or **Token**.

### Spend Budget

Optional maximum total amount to trade before the strategy stops. You can set the budget in **USD**, **Quote**, or **Token** units. Leave empty for no limit.

### Market Cap Range

| Field                  | Description                                                           |
| ---------------------- | --------------------------------------------------------------------- |
| **Min Market Cap ($)** | Strategy only executes when market cap is above this value (optional) |
| **Max Market Cap ($)** | Strategy only executes when market cap is below this value (optional) |

Set both for a range, or just one for a floor/ceiling trigger.

**Examples:**

* Buy when market cap drops below $1M: set Max to $1,000,000
* Sell when market cap exceeds $10M: set Min to $10,000,000
* Buy only between $500K–$1M: set Min to $500,000 and Max to $1,000,000

### Frequency

How often the strategy executes while the market cap condition is met. Enter a number and select: **Seconds**, **Minutes**, **Hours**, or **Days**.

### Jitter

| Field                       | Description                              |
| --------------------------- | ---------------------------------------- |
| **Trade Amount Jitter (%)** | Randomizes trade size by this percentage |
| **Interval Jitter (%)**     | Randomizes interval by this percentage   |

### Duration

* **Cycles** — Execute a fixed number of trades, then stop
* **Infinite** (∞) — Run indefinitely while conditions are met

### Wallet

Choose which wallets execute the trades — all wallets, a wallet group, or an individual wallet.

### Slippage

Set the maximum price movement Sumo should allow for each limit-order trade.

### Private Relay

On supported EVM profiles, you can enable **MEV protection using Private Relays**. This routes eligible trades through private relays to reduce public mempool exposure.

### Sell All Available Tokens

For Sell limit orders, you can enable **Sell all available tokens on insufficient balance**. If a planned sell is larger than the wallet's token balance, Sumo retries once using the wallet's available token balance.

## Strategy List View

Active limit order strategies display:

| Column           | Description                                                  |
| ---------------- | ------------------------------------------------------------ |
| **Trade Amount** | Amount per trade with jitter range                           |
| **Interval**     | Time between trades with jitter range                        |
| **Duration**     | Cycles or ∞                                                  |
| **Budget**       | Circular gauge showing spend progress (spent / total budget) |
| **Net Change**   | Cumulative base and quote asset changes                      |

## Use Cases

* **Buy the dip** — Set a Buy limit order with a max market cap to accumulate when price drops
* **Take profit** — Set a Sell limit order with a min market cap to distribute tokens as price rises
* **Range trading** — Combine buy and sell limit orders at different market cap ranges to trade within a band
* **Wallet cleanup** — Use sell-all-on-insufficient-balance when a Sell limit order should clear smaller token balances without manual resizing

- [Instant Trade](/strategies/instant-trade): Execute one-click manual trades from the dashboard.

- [DCA](/strategies/dca): Schedule regular trades at fixed intervals.


---

# Instant Trade

> Execute one-off buy or sell trades immediately from the dashboard.

- URL: https://docs.sumo.trade/strategies/instant-trade
- Markdown: https://docs.sumo.trade/strategies/instant-trade.md
- Docs index: https://docs.sumo.trade/llms.txt

Instant Trade lets you execute manual buys and sells on demand from the Live Trading page. Sumo offers quick presets for fast intervention, a custom trade panel for exact one-off trades, and a Swap modal with both **Instant Trade** and **Treasury Swap** tabs.

> **Video: Instant Trade Deep Dive**
>
> A walkthrough of quick presets, custom trades, treasury swaps, and manual execution from the Live Trading workspace.
>
> https://www.youtube.com/watch?v=l22QOf5Hp9A

## Quick Trade Presets

The Instant Trade panel is available on the [Live Trading](/reporting/live-trading) page. It shows:

* **Quick Buy** - preset buttons for instant buy trades
* **Quick Sell** - preset buttons for instant sell trades

Each preset shows a configured range. When you click a preset, Sumo picks a random amount within that range and submits the trade across the profile's active wallets.

### Presets

Each side can have up to six presets. Presets are configured separately for buys and sells in [Profile Settings](/getting-started/profile-settings).

| Preset Unit        | Description                                                                                        |
| ------------------ | -------------------------------------------------------------------------------------------------- |
| **USD**            | Trade a random dollar value in the configured range.                                               |
| **Quote / Native** | Trade a random amount in the profile quote asset, such as SOL, USDC, WETH, or another quote asset. |
| **Token**          | Trade a random amount of the profile token.                                                        |

Preset labels reflect the configured unit, for example `$100-$300`, `1-2 SOL`, or `10K-20K TOKEN`.

### Volume Tracking

The Instant Trade panel shows cumulative volume for each side:

* **Buy Volume** - Total value of instant buys executed
* **Sell Volume** - Total value of instant sells executed

## Custom Trade

Use **Custom Trade** when you want the speed of Instant Trade but need to choose the exact amount.

| Field                    | Description                                                                                                                                                                                                                                                                                                       |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Buy / Sell / Convert** | Select the trade direction. **Convert** runs a [Treasury Swap](/treasury/stable-swap) between the native asset, the quote token, and the chain's supported stablecoins in the same rows. It appears on every profile whose chain supports Treasury Swap (not Stable Mainnet) and is hidden for read-only viewers. |
| **Amount**               | Enter the trade amount.                                                                                                                                                                                                                                                                                           |
| **Amount Currency**      | Choose whether the amount is in USD, quote/native, or token units. In Convert mode, choose which asset to spend (native, quote, or a stablecoin).                                                                                                                                                                 |
| **Receive**              | Convert mode only. A second row under the balance shows the estimated amount you receive and its asset picker. Defaults to the quote token, or a stablecoin when buys already spend the native asset; only assets the treasury swap can pair with the spend asset are listed.                                     |
| **Wallet**               | Choose all active wallets, a wallet group, or an individual wallet.                                                                                                                                                                                                                                               |
| **Slippage**             | Maximum price movement allowed for the trade.                                                                                                                                                                                                                                                                     |
| **Private Relay**        | On supported EVM profiles, routes eligible trades through private relays for MEV protection.                                                                                                                                                                                                                      |

The **Max** button fills the largest available amount for the selected direction, unit, and wallet target when a balance is available.

## Swap Modal

For more control over manual trades, use the **Swap** button in the top navigation bar. This opens a swap modal with two tabs.

![Swap Tokens modal](/images/swap-modal.png)

### Instant Trade Tab

The **Instant Trade** tab swaps between the profile token and the profile quote/native asset.

| Field             | Description                                                                                  |
| ----------------- | -------------------------------------------------------------------------------------------- |
| **From**          | The token you're selling and the amount. Shows your current balance with a **Max** button.   |
| **To**            | The token you're receiving. The estimated output updates as you type.                        |
| **Reverse**       | Click the arrow button to flip the swap direction.                                           |
| **Wallet**        | Choose all active wallets, a wallet group, or an individual wallet.                          |
| **Slippage**      | Maximum price movement allowed for the trade.                                                |
| **Private Relay** | On supported EVM profiles, routes eligible trades through private relays for MEV protection. |

Enter an amount in the **From** field, review the estimated output in the **To** field, and click **Swap** to execute.

## Treasury Swap

The **Treasury Swap** tab is available from the same Swap modal on every profile.

![Treasury Swap modal](/images/stable-swap-modal.png)

Use Treasury Swap when you want to move between a supported profile asset and a registered stablecoin, or between the native asset and a custom quote token. The available assets depend on the profile's chain and configured token/quote assets. The Custom Trade panel's **Convert** mode runs the same treasury swap between the native asset, the quote token, and stablecoins without opening the modal (the project token is only traded through Buy and Sell); if your wallets hold the native asset but none of the quote token, a notice above Quick Buy switches the panel to that mode.

| Field               | Description                                                                                                                                                 |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **From**            | The asset you're selling and the aggregate amount.                                                                                                          |
| **To**              | The asset you're receiving. Market quote output is shown after quoting.                                                                                     |
| **Asset Selectors** | Choose the **From** asset first; the **To** list then shows only the assets that pair with it. Picking the current **To** asset as **From** flips the pair. |
| **Reverse**         | Swap the **From** and **To** assets.                                                                                                                        |
| **Wallet**          | Choose all active wallets, a wallet group, or an individual wallet.                                                                                         |
| **Mode**            | **Pro-rata** spreads the input across wallets proportionally. **Rebalance** uses wallets with more available balance first to even out balances.            |
| **Slippage**        | Maximum price movement allowed for the trade.                                                                                                               |
| **Private Relay**   | On supported EVM profiles, routes eligible trades through private relays for MEV protection.                                                                |

Enter the amount, choose the wallet target and mode, then click **Treasury Swap**.

## When to Use

* **Price support** - Quickly buy when you see a large sell hitting the pool
* **Taking profit** - Sell a portion when price spikes
* **Precise amounts** - Use Custom Trade or the Swap modal when you need to trade an exact amount rather than a random preset range
* **Stablecoin rotation** - Use Treasury Swap to move between supported stablecoin/profile asset pairs
* **Testing** - Verify your wallets and pool are working before setting up automated strategies

For automated trading, use [Counter Trade](/strategies/counter-trade), [DCA](/strategies/dca), or [Limit Orders](/strategies/limit-orders) instead.

- [Counter Trade](/strategies/counter-trade): Automate counter-trading for hands-off price stability.

- [Impact Calculator](/strategies/impact-calculator): Estimate the price impact before you trade.


---

# Snipe Token Supply

> Buy the project token across many wallets at once, capped by a maximum premium over the current price.

- URL: https://docs.sumo.trade/strategies/snipe-token-supply
- Markdown: https://docs.sumo.trade/strategies/snipe-token-supply.md
- Docs index: https://docs.sumo.trade/llms.txt

Snipe Token Supply fires one buy from every selected wallet in parallel. Use it to accumulate supply quickly across your treasury — after a launch, on a dip, or when you want many wallets positioned at once. Anti-MEV routing is always on.

![Snipe Token Supply dialog](/images/snipe-token-supply.png)

It is available on Solana and EVM profiles.

## How It Works

Every selected wallet submits its own buy at the same time. Because your own buys move the price, the wallets that land last pay more than the wallets that land first — so instead of a fixed price limit, you set a **maximum premium**: how far above the current price the last-landing wallet is allowed to pay. Wallets that would exceed the cap simply do not buy.

The preview translates your settings into concrete outcomes before you commit: how many of the selected wallets are expected to fill, the expected token amount, and the maximum premium actually paid.

## How to Use

1. Open the profile's **Strategies** tab and click the **snipe** action
2. Select the **wallets** — individual wallets, wallet groups, or everything
3. Choose the **allocation** and amount
4. Set the **max premium**
5. Review the execution settings — method, priority, tip, and pacing
6. Click **Preview** to see expected fills, tokens, and spend
7. Confirm to fire

## Wallets

The selected wallets buy in parallel. Groups expand to their eligible members. Each wallet's spendable balance excludes fees, tips, rent, and the reserve buffer.

## Allocation

| Mode                        | Description                                                                              |
| --------------------------- | ---------------------------------------------------------------------------------------- |
| **% of balance per wallet** | Each wallet spends this share of its spendable balance.                                  |
| **Fixed per wallet**        | Every wallet spends the same fixed amount.                                               |
| **Total split**             | One total is split across the wallets, with optional jitter to vary each wallet's share. |

## Max Premium

The price control. It caps what the **last wallet to land** can pay, as a percentage above the price your own buys are expected to reach — protection against other buyers landing at the same time, not a cap on today's market cap. Preset chips offer +10%, +25%, +50%, and +100%, or enter a custom value.

Wallets that would exceed the cap do not buy; the preview shows how many wallets are expected to fill within it. The derived absolute price cap is persisted with the snipe, so it stays meaningful if the pool moves.

## Execution Settings

| Setting                       | Description                                                                                                           |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Execution Method** (Solana) | **Helius Sender** lands fastest with MEV protection — the tip picks the pathway. **RPC** submits plainly with no tip. |
| **Priority Fee**              | Compute-unit priority applied to every transaction.                                                                   |
| **Tip Per Wallet** (Solana)   | Tip attached to each wallet's transaction. Tips below 0.001 SOL are unlikely to be competitive.                       |
| **Gas Priority** (EVM)        | Gas pricing applied to every transaction.                                                                             |
| **Extra Reserve Buffer**      | Extra native kept out of every wallet's spendable balance, on top of fees, tips, and rent (or gas on EVM).            |

## Pacing

| Mode       | Description                                                                                                    |
| ---------- | -------------------------------------------------------------------------------------------------------------- |
| **Burst**  | Sends every wallet at once. Maximum speed; the premium cap alone bounds the price, so slippage does not apply. |
| **Waves**  | Sends wallets in groups, waiting for observed landings before releasing the next wave.                         |
| **Serial** | Sends one wallet at a time with a delay.                                                                       |

In waves and serial pacing, a **Slippage** setting adds room above each leg's modeled floor. **Duration** controls how long failed buys keep retrying.

> **Why the last wallet pays more**
>
> Your own buys move the price while they land. Burst pacing embraces this: all wallets fire together and the premium cap decides which fills are acceptable, rather than sequencing wallets and hoping the price holds.

## Preview and Results

The preview shows expected fills (≈K of N wallets), expected tokens, total spend, and the maximum premium paid before you commit. After firing, the progress view tracks wallets filled, tokens acquired, actual spend, and tips as landings confirm.

- [Instant Trade](/strategies/instant-trade): One-off buys and sells from single wallets.

- [Wallet Groups](/wallets/wallet-groups): Organize wallets for group-based selection.


---

# Impact Calculator

> Estimate the market impact of your trades before executing.

- URL: https://docs.sumo.trade/strategies/impact-calculator
- Markdown: https://docs.sumo.trade/strategies/impact-calculator.md
- Docs index: https://docs.sumo.trade/llms.txt

The Impact Calculator helps you estimate how a trade could affect price and market cap based on current pool depth before you execute it. It's accessible from the Strategies page via the calculator icon.

> **Video: Using the Impact Calculator**
>
> A walkthrough of trade scenarios, market flow assumptions, price deltas, and market-cap impact estimates.
>
> https://www.youtube.com/watch?v=IHlXP9N8aug

![Impact Calculator with buy scenario results](/images/impact-calculator.png)

## How to Use

1. Go to your profile's **Strategies** tab
2. Click the **calculator icon** next to the Create Strategy button
3. Configure the scenario and review the results

## Configuration

### Trade Side

Select **Buy** or **Sell** to simulate the direction of the trade.

### Trade Size

Enter the size of the trade you want to simulate. Select the unit: **USD**, **Quote/Native** (e.g. SOL, USDC, WETH), or **Token**.

### Market Flow

Simulate additional market pressure alongside your trade:

* **Negative (%)** — Additional flow offsets your simulated trade
* **Positive (%)** — Additional flow moves in the same direction as your simulated trade
* **0%** — No additional market pressure, just your trade

Use the slider or type a value directly. The slider gradient goes from red (negative) to green (positive).

## Results

Once calculated, the Impact Calculator shows:

| Metric                 | Description                                               |
| ---------------------- | --------------------------------------------------------- |
| **Token Flow**         | How many tokens move in/out (shown with +/- prefix)       |
| **Quote Flow**         | How much quote asset (e.g. SOL, WETH) moves in/out        |
| **Current Price**      | The token's current price in USD                          |
| **Current Market Cap** | The token's current market cap                            |
| **Price Delta**        | How much the price changes (absolute and percentage)      |
| **Market Cap Delta**   | How much the market cap changes (absolute and percentage) |
| **Final Price**        | Projected price after the trade                           |
| **Final Market Cap**   | Projected market cap after the trade                      |

Positive deltas show a green up arrow, negative deltas show a red down arrow.

If the trade size may be too large for current liquidity, a warning is displayed and the estimate may be less reliable.

## Use Cases

* **Size your trades** — Check how much a $10K buy would move the price before executing
* **Plan DCA amounts** — Find the right trade size that moves the price without excessive impact
* **Evaluate counter-trade settings** — Understand the impact of different capture percentages
* **Scenario planning** — Model how your trades perform under different market flow conditions

- [Counter Trade](/strategies/counter-trade): Set up automated counter-trading based on your impact analysis.

- [Strategies Overview](/strategies/overview): Compare all strategy types and learn when to use each.


---

# Wallet Farm

> Manage wallets centrally, independent of any trading profile — fund them early, build on-chain history, and import them when you're ready to trade.

- URL: https://docs.sumo.trade/wallet-farm/overview
- Markdown: https://docs.sumo.trade/wallet-farm/overview.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Managing Wallets with Wallet Farm**
>
> A tour of Wallet Farm for preparing, funding, organizing, and importing wallets before a token launch.
>
> https://www.youtube.com/watch?v=0JuO-dukdAs

![Wallet Farm dashboard showing wallets, folders, and toolbar](/images/wallet-farm-wallets.png)

Wallet Farm is a centralized workspace for managing wallets outside the context of any specific trading profile. It is designed for teams that need to prepare wallets **before** a token launches — funding them, organizing them into folders, and building natural on-chain transaction history — so they are ready to import into a profile the moment trading begins.

## Why Wallet Farm?

Trading profiles in Sumo are tied to a specific token and DEX pool, and a profile can only be created once that pool exists on-chain. For most token launches, this means you cannot set up wallets inside a profile until launch day.

Wallet Farm removes that constraint:

* **Fund wallets early** — Deposit native assets (SOL, ETH, etc.) days or weeks before a launch so wallets are ready to trade immediately.
* **Build on-chain history** — Use [Generate Activity](/wallet-farm/generate-activity) to execute real swaps on trending tokens, giving each wallet a natural transaction footprint.
* **Distribute funds privately** — Use [Privacy Funding](/wallet-farm/privacy-funding) to fund multiple wallets from a single source without creating an obvious on-chain link between them.
* **Move value across chains** — Use [Cross-Chain Swap](/treasury/cross-chain-swap#wallet-farm) to swap between two Wallet Farm wallets on different chains.
* **Organize with folders** — Group wallets by purpose, team, or strategy using color-coded folders.
* **Import on launch day** — When the token launches and a trading profile is created, [import wallets](/wallet-farm/import-to-profile) from Wallet Farm into the profile in one step.

> **Pre-launch Profiles**
>
> For tokens launching on PumpFun, Sumo supports **pre-launch profiles** that let you set up wallets within a profile before the bonding curve completes. Wallet Farm is most useful for launches on other DEXes where pre-launch profiles are not available, or when you want to prepare wallets across multiple potential launches.

## Dashboard Overview

The Wallet Farm page separates wallet preparation from operational logs:

| Tab               | Description                                                                                                |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| **In Progress**   | Wallets that still need more preparation before they are ready to import into a profile.                   |
| **Ready**         | Wallets with stronger preparation signals, such as enough age, known funding source, and activity history. |
| **Activity Logs** | Audit trail of all activity generation runs — timestamps, wallet counts, swap outcomes.                    |
| **Funding Logs**  | History of privacy funding sessions — provider, status, amounts, and deposit tracking.                     |

The toolbar provides quick access to the main operations:

* **Add wallets** — Generate new wallets or import existing ones
* **Generate activity** — Run token swaps to build on-chain history (requires wallet selection)
* **Manage folders** — Create and organize wallet folders
* **Cross-Chain Swap** — Move value between Wallet Farm wallets on different chains
* **Privacy funding** — Fund wallets via privacy-preserving providers
* **Withdraw*&#x2A; — Sweep native balances from selected wallets to a destination address (in the &#x2A;*⋯** menu)
* **Filter folders** — Filter the wallet table by folder

## Wallet Table

Each wallet row shows:

| Column      | Description                                                                                              |
| ----------- | -------------------------------------------------------------------------------------------------------- |
| **Address** | On-chain public address with folder color indicator                                                      |
| **Swaps**   | Number of successful activity swaps completed by the wallet                                              |
| **Age**     | Time since the wallet was first funded                                                                   |
| **Source**  | Detected funding source, such as a known exchange, privacy provider, wallet, contract, or unknown source |
| **Chain**   | Network the wallet belongs to (e.g., Solana Mainnet)                                                     |
| **Balance** | Native asset balance (SOL, ETH, etc.)                                                                    |
| **Value**   | USD value of native balance                                                                              |
| **Status**  | Active/inactive toggle                                                                                   |

The readiness icons beside **Swaps**, **Age**, and **Source** make it easier to scan which wallets are ready to use. Green means the signal is strong, yellow means it is partially prepared, and red means the wallet still needs attention. Active wallets can be used for funding and activity operations; inactive wallets stay in Wallet Farm but are skipped by those actions.

## Readiness Thresholds

Wallet readiness is based on the preparation signals shown in the table:

| Signal     | Green                                          | Yellow                               | Red                                                     |
| ---------- | ---------------------------------------------- | ------------------------------------ | ------------------------------------------------------- |
| **Swaps**  | At least 10 successful activity swaps          | At least 5 successful activity swaps | Fewer than 5 successful activity swaps                  |
| **Age**    | Funded at least 7 days ago                     | Funded at least 2 days ago           | Funded less than 2 days ago, or funding date is missing |
| **Source** | Known exchange, exchanger, or privacy provider | Not used                             | Wallet, contract, unknown, or missing source            |

Use these signals together. A wallet with good swap activity but an unknown funding source may still need review before it is imported into a profile.

- [Add Wallets](/wallet-farm/add-wallets): Generate new wallets or import existing ones into Wallet Farm.

- [Generate Activity](/wallet-farm/generate-activity): Build on-chain transaction history for your wallets.

- [Privacy Funding](/wallet-farm/privacy-funding): Fund wallets privately using supported providers.

- [Cross-Chain Swap](/treasury/cross-chain-swap#wallet-farm): Swap between Wallet Farm wallets on different chains.

- [Withdraw](/wallet-farm/withdraw): Sweep native balances from farm wallets to a destination address.

- [Import to Profile](/wallet-farm/import-to-profile): Move wallets from Wallet Farm into a trading profile.

## Further Reading

* [How to Launch a Memecoin in 2026](https://blog.sumo.trade/how-to-launch-a-memecoin/) — where aged wallets fit into a launch plan
* [The Memecoin Dictionary](https://blog.sumo.trade/memecoin-dictionary/) — bundling, sniping, and the other slang that describes what Wallet Farm prepares you for


---

# Add Wallets

> Generate new wallets, buy Wallet Marketplace inventory, import from private keys or seed phrases, or pull wallets from an existing trading profile into Wallet Farm.

- URL: https://docs.sumo.trade/wallet-farm/add-wallets
- Markdown: https://docs.sumo.trade/wallet-farm/add-wallets.md
- Docs index: https://docs.sumo.trade/llms.txt

Click **Add Wallets** in the Wallet Farm toolbar to open the Add Wallets dialog. Available tabs depend on your role and marketplace inventory access. The main paths are:

## Create New

Generate fresh wallets derived from a seed phrase.

![Add Wallets dialog with Create New tab selected](/images/wallet-farm-add-wallets-create-new.png)

1. Select the target **Chain** (Solana Mainnet, Ethereum, Base, etc.)
2. Choose the **Number of Wallets** — use the quick-select buttons (5, 10, 15, 20) or enter a custom count
3. Optionally assign a **Wallet Folder** to organize the new wallets
4. Optionally provide a **Seed Phrase** — if left blank, Sumo uses the first Wallet Farm seed for your organization (or creates one automatically)
5. Click **Confirm**

Wallets are derived using BIP-44 HD derivation, so they are deterministically reproducible from the seed. Names are auto-generated when creating multiple wallets.

## Import Keys

Import existing wallets using private keys.

![Add Wallets dialog with Import Keys tab selected](/images/wallet-farm-add-wallets-import-keys.png)

1. Select the **Import Keys** tab
2. Choose the target **Chain**
3. Paste private keys — one per line
4. Optionally assign a folder
5. Click **Confirm**

> **Key Security**
>
> Imported private keys are encrypted immediately using AES-256-GCM before storage. They never exist in plaintext in the database. See [Security & Encryption](/wallets/security-encryption) for details.

## From Marketplace

Buy aged wallet marketplace inventory into Wallet Farm. This is useful when you want wallets prepared outside a specific trading profile, then later import them into a launch or trading profile.

See [Wallet Marketplace](/wallets/wallet-marketplace#buy-into-wallet-farm) for the full Wallet Farm marketplace flow.

## From Profile

Pull wallets from an existing trading profile into Wallet Farm. This is useful when you want to reuse wallets from a completed or inactive profile for a future launch.

![Add Wallets dialog with From Profile tab selected](/images/wallet-farm-add-wallets-from-profile.png)

1. Select the **From Profile** tab
2. Choose a **Source Profile** from the dropdown
3. Select which wallets to import
4. Optionally assign a folder
5. Click **Confirm**

Source wallets remain in their original profile — Wallet Farm creates independent copies that share the same on-chain addresses and key material.

## Wallet Folders

Folders help you organize wallets by purpose, team member, or launch. You can create folders from the Add Wallets dialog or from the **Manage Folders** toolbar button.

* Each folder has a name and a color indicator
* Wallets can belong to at most one folder
* Use the **Filter folders** toolbar button to show only wallets in a specific folder
* Bulk-assign wallets to folders via the Manage Folders dialog

- [Generate Activity](/wallet-farm/generate-activity): Build on-chain history for your new wallets.

- [Privacy Funding](/wallet-farm/privacy-funding): Fund wallets privately before launch day.


---

# Generate Activity

> Build natural on-chain transaction history for Wallet Farm wallets by executing real token swaps through an aggregator or directly against a DEX pool.

- URL: https://docs.sumo.trade/wallet-farm/generate-activity
- Markdown: https://docs.sumo.trade/wallet-farm/generate-activity.md
- Docs index: https://docs.sumo.trade/llms.txt

![Generate Activity dialog showing swap configuration](/images/wallet-farm-generate-activity.png)

Generate Activity executes real token swaps across your selected Wallet Farm wallets to build on-chain transaction history. Each wallet performs a configurable number of buy-and-sell swap pairs on tokens drawn from a token pool, creating a diverse and organic-looking footprint of normal trading behavior. Successful swaps are reflected in the Wallet Farm table so you can quickly see which wallets have enough activity.

## How It Works

1. **Select wallets** in the Wallet Farm table using the checkboxes
2. Click the **Generate Activity** toolbar button
3. Configure the parameters (see below)
4. Click **Confirm** to start

For each selected wallet, Sumo:

1. Picks a random number of swap pairs (between your min and max)
2. For each pair, selects a token from the token pool
3. Executes a **native-to-token swap** (buy) with a randomized amount within your configured range
4. Executes a **token-to-native swap** (sell) to convert back, minus the configured dust percentage
5. Waits the configured delay before the next swap pair

Each wallet runs as its own background job. Sumo processes wallets in batches, with wallets in the current batch progressing in parallel while the swap pairs within a single wallet run one after another. The next batch starts after every wallet in the current batch finishes.

## Configuration

| Parameter                         | Description                                                                                                                                                                              |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Min/Max Swaps Per Wallet**      | The number of buy-sell swap pairs each wallet executes, up to 1000. A random count is chosen per wallet within this range.                                                               |
| **Min/Max {'{Native}'} Per Swap** | The native asset amount used for each buy. The label follows the chain, such as **Min SOL Per Swap** or **Min ETH Per Swap**. A random amount is chosen per swap within this range.      |
| **Batch Size**                    | The number of wallets processed concurrently, from 1 to 250. Defaults to `8`. The next batch starts after every wallet in the current batch finishes. This also applies to cleanup runs. |
| **Dust Percentage**               | The percentage of purchased tokens to leave behind after selling back. Defaults to `0`, which sells the full amount. A value of `10` leaves 10% of purchased tokens in the wallet.       |
| **Delay Between Swap**            | Seconds to wait between consecutive swap pairs on the same wallet, up to 3600. Defaults to `5`. Adds natural timing variation.                                                           |
| **Execution Provider**            | How swaps are routed. The options and default depend on the chain — see [Execution Providers](#execution-providers).                                                                     |
| **Token Source**                  | **Trending Tokens** (default) pulls from trending markets, or **Custom Tokens** lets you paste your own mints.                                                                           |
| **Token Pool**                    | The set of tokens to swap against, up to 25. Deselect any tokens you want to exclude.                                                                                                    |
| **Slippage**                      | Direct DEX only. Maximum slippage per swap, from 0.1% to 25%. Defaults to `1`%.                                                                                                          |
| **Allowed DEXs**                  | Direct DEX only. Which venues pool discovery may search. Defaults to **All DEXs** for the chain.                                                                                         |

A single run covers up to 250 wallets.

### Custom Tokens

Switching **Token Source** to **Custom Tokens** reveals a text box where you can paste mint addresses, one per line or comma separated, then click **Add**. Sumo validates each address for the chain, ignores duplicates, and rejects the chain's wrapped native asset. The result is reported back as the number added, ignored, and invalid. Custom tokens are required on chains where Sumo does not source trending markets.

## Execution Providers

| Chain                                      | Options                                             | Default     |
| ------------------------------------------ | --------------------------------------------------- | ----------- |
| Solana                                     | DFlow, Jupiter, OKX DEX, Direct DEX                 | DFlow       |
| Ethereum, BNB Chain, Base, Robinhood Chain | 0x, Uniswap API, Direct DEX                         | 0x          |
| Ethereum Sepolia                           | Uniswap API, Direct DEX                             | Uniswap API |
| Stable Mainnet                             | Direct DEX                                          | Direct DEX  |
| Tron                                       | Routes directly through SunSwap; no provider choice | —           |

### Direct DEX

**Direct DEX** skips aggregators entirely and trades against a single token/wrapped-native pool per token. When you confirm the run, Sumo searches your **Allowed DEXs** for every token in the pool, quotes the actual trade size against each candidate pool, and locks in the venue that returns the most output. Every wallet in the run then trades that same pool.

Choose Direct DEX when you want control over which venues your wallets touch, or on chains where no aggregator is available. Points to keep in mind:

* **Confirming takes longer.** Pool discovery runs before any swap is queued and can take up to 45 seconds.
* **Slippage is manual.** Auto-slippage is disabled, so the **Slippage** field is the only tolerance applied.
* **Tokens without a pool are dropped** from the run rather than failing it. If none of your tokens have a token/wrapped-native pool, the run is rejected so you can pick different tokens.
* **Universal routers cannot be selected alone.** Pick the underlying venues, such as Uniswap V2, V3, and V4, rather than only a router.
* On EVM chains that support it, direct swaps are submitted through a private relay for MEV protection.

> **Pool Discovery Timed Out**
>
> If a venue is slow to respond, Sumo stops searching it for the rest of the run. When tokens are still unresolved at that point, the request fails with a retryable error rather than silently trading fewer tokens. Retry, select fewer tokens, or narrow **Allowed DEXs** to healthy venues.

## Supported Chains

Generate Activity works on Solana, Ethereum, Ethereum Sepolia, BNB Chain, Base, Robinhood Chain, Stable Mainnet, and Tron. All selected wallets must be on a single chain per run.

* **Solana and EVM chains** — Swaps route through the selected execution provider, either an aggregator or Direct DEX.
* **Stable Mainnet** — Direct DEX only, with custom tokens.
* **Tron** — Swaps execute directly on SunSwap against WTRX pools. Trending tokens without a SunSwap pool are skipped automatically.

## Cleanup Mode

Setting **both** Min and Max Swaps Per Wallet to `0` switches the dialog into **Sell/Cleanup Tokens** mode. Instead of generating new activity, Sumo sells the token balances already held by the selected wallets back to the native asset. The amount, dust, and delay fields disappear, and on Solana the token pool is discovered from wallet balances automatically. The submit button becomes **Cleanup Tokens**.

> **Dust Tokens**
>
> Leaving a small dust percentage of tokens in each wallet creates a more natural-looking wallet profile, since real traders often hold small residual balances across many tokens. If the dust percentage is set to `0`, Sumo waits for the buy transaction to confirm before executing the sell to ensure the exact token balance is known.

## Monitoring Results

After starting an activity generation run, you can track progress in the **Activity Logs** tab. Each run creates:

* A **summary entry** with the total wallet count, swap count, and success/failure breakdown
* **Per-swap entries** with individual transaction hashes, amounts, and confirmation status

Activity and funding logs are scoped to the inventory you are viewing, so a run started from Wallet Farm appears under Wallet Farm logs and a run started from Wallet Marketplace appears under Marketplace logs. Switching inventory keeps you on the logs tab and swaps in that inventory's rows.

Swap transactions are submitted and then confirmed best-effort in the background. The summary status will be one of:

| Status             | Meaning                             |
| ------------------ | ----------------------------------- |
| **Accepted**       | Run is in progress                  |
| **Completed**      | All swaps succeeded                 |
| **Partial Failed** | Some swaps failed, others succeeded |
| **Failed**         | All swaps failed                    |

Individual swaps are skipped without retrying when the selected pool is no longer usable — for example if a bonding curve graduated, or the pool was drained or migrated after the run started.

> **Wallet Balance Required**
>
> Each wallet needs a sufficient native asset balance to cover the maximum possible swap amount plus transaction fees. Fund your wallets before running activity generation — see [Privacy Funding](/wallet-farm/privacy-funding) for a private funding approach.

- [Privacy Funding](/wallet-farm/privacy-funding): Fund wallets before generating activity.

- [Import to Profile](/wallet-farm/import-to-profile): Import prepared wallets into a trading profile.


---

# Privacy Funding

> Distribute funds to multiple Wallet Farm wallets using privacy-preserving providers, so destination wallets are not publicly linked to the funding source.

- URL: https://docs.sumo.trade/wallet-farm/privacy-funding
- Markdown: https://docs.sumo.trade/wallet-farm/privacy-funding.md
- Docs index: https://docs.sumo.trade/llms.txt

![Privacy Funding dialog showing provider selection and destination wallet configuration](/images/wallet-farm-privacy-funding.png)

Privacy Funding lets you distribute native assets (SOL, ETH, etc.) to multiple Wallet Farm wallets through a supported privacy provider. The provider acts as an intermediary, so the on-chain link between the funding source and the destination wallets is not directly visible.

## How It Works

1. Click the **Privacy Funding** toolbar button in Wallet Farm
2. Select a **Provider** (e.g., Husher)
3. Choose a **Mode** — Direct deposit or Existing wallet
4. Select **Destination Wallets** and assign the amount each wallet should receive
5. Optionally configure a **Staggered delay** (minutes between deliveries)
6. Click **Preview** to see the funding quote with provider fees
7. Confirm to start the session

The provider receives a single deposit and distributes the funds to your destination wallets according to the specified amounts.

## Funding Modes

### Direct Deposit

You receive a deposit address and send funds to it from any external wallet or exchange. Sumo monitors the deposit address for incoming transactions and notifies the provider once the deposit is detected.

This mode is useful when funding from a source outside of Sumo.

### Existing Wallet

Select one of your Wallet Farm wallets as the funding source. Sumo submits the deposit transaction directly from that wallet and monitors the provider's distribution to destination wallets.

This mode is convenient when the funds are already in a Wallet Farm wallet.

## Quote and Fees

Before confirming, the **Preview** step shows:

| Field                    | Description                                             |
| ------------------------ | ------------------------------------------------------- |
| **Total funding amount** | The amount you need to deposit, including provider fees |
| **Provider fee**         | The intermediary fee charged by the privacy provider    |
| **Per-wallet amounts**   | How much each destination wallet will receive           |
| **Quote expiration**     | How long the quote remains valid                        |

## Variable Amounts

You can assign different amounts to each destination wallet. Two input modes are available:

* **Interactive** — Add wallet rows one at a time and set individual amounts
* **CSV** — Paste wallet address and amount pairs in bulk for faster configuration

## Session Tracking

Each funding session progresses through these states:

| Status               | Meaning                                                              |
| -------------------- | -------------------------------------------------------------------- |
| **Awaiting deposit** | (Direct mode) Waiting for you to send funds to the deposit address   |
| **Monitoring**       | Deposit detected, provider is processing the distribution            |
| **Completed**        | All destination wallets received their funds                         |
| **Failed**           | Distribution failed — check session details for the reason           |
| **Expired**          | Quote expired before a deposit was made                              |
| **Timed out**        | Provider did not complete distribution within the expected timeframe |

Track all sessions in the **Funding Logs** tab. Each row shows the provider and mode, destination wallet count, requested amount, current status, and transaction link when one is available.

![Wallet Farm Funding Logs table showing privacy funding sessions, providers, destination wallet counts, amounts, statuses, and transactions](/images/wallet-farm-funding-logs.png)

> **Staggered Delivery**
>
> Use the staggered delay option to space out deliveries over time. Rather than all destination wallets receiving funds simultaneously, each delivery is separated by the configured number of minutes.

- [Generate Activity](/wallet-farm/generate-activity): Build transaction history after funding your wallets.

- [Import to Profile](/wallet-farm/import-to-profile): Import funded wallets into a trading profile.


---

# Withdraw

> Send or sweep native balances from Wallet Farm wallets to a destination address.

- URL: https://docs.sumo.trade/wallet-farm/withdraw
- Markdown: https://docs.sumo.trade/wallet-farm/withdraw.md
- Docs index: https://docs.sumo.trade/llms.txt

Withdraw sends native balance (SOL, ETH, BNB, TRX, and so on) from selected Wallet Farm wallets to one destination address, either a fixed total amount or a full sweep. Use it to recover funds from wallets you no longer plan to import into a profile, or to consolidate a folder into a single wallet.

## How to Withdraw

1. Open **Wallet Farm** and pick the **Ready** or **In Progress** tab
2. Optionally check the wallets you want to sweep in the table
3. Open the &#x2A;*⋯** menu in the toolbar and click **Withdraw**
4. Adjust the wallet selection — folders act as group rows over their member wallets, and each wallet row shows its native balance
5. Enter the **amount** to send, or click **Sweep** to drain every selected wallet
6. Enter the **destination address**
7. Click **Withdraw**

The checked wallets are pre-selected when the modal opens. Empty wallets are skipped automatically, and wallets keep their current status after the withdrawal.

## Amount or Sweep

The summed balance of the selected wallets is shown under the amount field, and each wallet row in the picker shows its own balance. A typed amount is the **total** to send: it is split across the selected wallets in proportion to their balances, so a wallet holding a third of the total contributes a third of the amount. Each wallet keeps a small native reserve to pay its own network fee, so the maximum you can send is slightly below the displayed balance.

If the amount exceeds what the selected wallets can send after those reserves, the withdrawal is rejected and the error shows the amount actually available. Lower the amount or use **Sweep**, which ignores the amount and drains every selected wallet.

## One Chain per Withdrawal

A withdrawal targets one chain. The first wallet you check sets the chain; wallets on other chains are marked **Different chain** and cannot be added until you clear the selection. The destination address is validated for that chain, and the server rejects any request that mixes chains.

## Native Only

Withdraw moves native balance only. Token dust left behind by activity swaps is cleaned up by [Generate Activity](/wallet-farm/generate-activity) in cleanup-only mode, which sells it back to native. Run cleanup first, then withdraw.

## Destinations and Roles

| Role                | Allowed destinations                                                                                                                |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Trader**          | Wallets your organization manages: profile wallets, other Wallet Farm wallets, the Rewards settlement wallet, and the MM fee wallet |
| **Admin** and above | Any address                                                                                                                         |

> The platform withdrawal fee configured for your organization applies to Wallet Farm withdrawals exactly as it does to profile withdrawals.

## Tracking a Withdrawal

Each swept wallet appears as its own row in the **Activity logs** tab with the transaction link and status. On Solana the transfers are submitted immediately; on EVM and Tron chains they run in the background and the rows update as they confirm. A Wallet Hub notification is sent when the whole withdrawal completes or fails.

- [Generate Activity](/wallet-farm/generate-activity): Clean up token dust before withdrawing.

- [Profile Withdraw](/treasury/withdraw): Withdraw from profile wallets with amounts, tokens and multiple destinations.


---

# Import to Profile

> Import prepared Wallet Farm wallets into a trading profile so they can participate in strategies and treasury operations.

- URL: https://docs.sumo.trade/wallet-farm/import-to-profile
- Markdown: https://docs.sumo.trade/wallet-farm/import-to-profile.md
- Docs index: https://docs.sumo.trade/llms.txt

Once your wallets are funded, have on-chain history, and a trading profile is ready, you can import wallets from Wallet Farm into the profile.

## How to Import

There are two directions for importing wallets between Wallet Farm and profiles:

### From Wallet Farm to a Profile

Use this flow when your wallets are prepared in Wallet Farm and you are ready to move them into a specific trading profile.

![Import From Farm modal with Wallet Farm folder selector and profile wallet group assignment](/images/profile-funding-from-farm.png)

1. Navigate to the target **trading profile's Wallets** tab
2. Click **+ New Wallets**
3. Select the **From Farm** tab
4. Choose one or more Wallet Farm folders
5. Assign the imported wallets to an existing profile wallet group or create a new group
6. Click **Confirm**

### From a Profile to Wallet Farm

If you have wallets in an existing profile that you want to manage centrally:

![Wallet Farm Add Wallets dialog with From Profile tab selected](/images/wallet-farm-add-wallets-from-profile.png)

1. Open **Wallet Farm** from the dashboard
2. Click the &#x2A;*+** (Add wallets) button
3. Select the **From Profile** tab
4. Choose the source profile and source wallet groups
5. Optionally assign the imported wallets to a Wallet Farm folder
6. Click **Confirm**

## What Happens on Import

* **Wallets are cloned** — the import creates independent copies in the target location. Source wallets remain unchanged in their original location.
* **Same on-chain address** — cloned wallets share the same public address and key material, so the on-chain balance and history are identical.
* **Audit trail** — every import is logged with the source profile and wallet IDs for full traceability in [Audit Logs](/reporting/audit-logs).

> **No Duplicate Risk**
>
> If a wallet already exists in the target profile or Wallet Farm, it is skipped during import. No duplicate entries are created.

## Typical Workflow

A complete Wallet Farm preparation flow looks like this:

1. **Create wallets** in Wallet Farm — [Add Wallets](/wallet-farm/add-wallets)
2. **Fund wallets** using privacy-preserving providers — [Privacy Funding](/wallet-farm/privacy-funding)
3. **Build on-chain history** by swapping trending tokens — [Generate Activity](/wallet-farm/generate-activity)
4. **Wait for token launch** — the token launches and a DEX pool is created
5. **Create a trading profile** for the new token in Sumo
6. **Import wallets** from Wallet Farm into the profile
7. **Start trading** — wallets are funded, have history, and are ready to execute strategies

- [Wallet Farm Overview](/wallet-farm/overview): Return to the Wallet Farm overview.

- [How Wallets Work](/wallets/how-wallets-work): Learn about Sumo's wallet architecture.


---

# How Wallets Work

> Understanding Sumo's secure wallet architecture.

- URL: https://docs.sumo.trade/wallets/how-wallets-work
- Markdown: https://docs.sumo.trade/wallets/how-wallets-work.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo manages real on-chain wallets for your trading operations. Each wallet is a standard blockchain address that holds and trades your funds — there's no custodial pool or shared wallet.

## Wallet Architecture

### Seeds and Derivation

Sumo uses **BIP-39 mnemonic phrases** (12 or 24 words) as master seeds. From each seed, wallets are derived using **BIP-44 HD derivation**, which means:

* Each seed can generate an unlimited number of wallets
* All wallets from the same seed are deterministically reproducible
* You can have multiple seeds per profile

### On-Chain Addresses

Every wallet in Sumo maps to a real on-chain address:

* **Solana** — Standard Ed25519 keypairs
* **EVM** (Ethereum, BSC, Base) — Standard ECDSA keypairs

You can view any wallet's public address on the Wallets page and use it to send/receive funds directly.

## Wallet Table

The Wallets page shows all your wallets in a sortable table:

| Column                    | Description                                             |
| ------------------------- | ------------------------------------------------------- |
| **Address**               | Wallet public address with group color indicator        |
| **SOL** (or native asset) | Native asset balance                                    |
| **Tokens**                | Your token balance in this wallet                       |
| **% Supply**              | What percentage of total token supply this wallet holds |
| **$ Value**               | Total USD value of all assets in the wallet             |
| **Status**                | Active, archived, or excluded                           |

Click any column header to sort. Use the search bar to filter by wallet address.

## Profile and Wallet Actions

The profile workspace combines wallet-table actions with treasury operations:

* **Copy addresses** — Copy all filtered wallet addresses to clipboard
* **Edit groups** — Assign selected wallets to groups
* **Archive/Unarchive** — Toggle wallet active status
* **Exclude** — Move wallets to the Excluded tab when they should not be reused accidentally
* **Withdraw** — Send native assets, quote tokens, project tokens, or all balances to external destinations
* **Treasury Swap** — Rotate selected wallets between native assets and supported stablecoins from the Swap modal
* **Cross-Chain Swap** — Cash out from a project wallet to an address on a different chain
* **Privacy Cashout** — Move native assets or supported stablecoins privately between wallets
* **Swap Wallets** — Rotate wallet assignments
* **Token Cleanup** — Rebalance token holdings between wallet groups through direct transfers or market redistribution
* **Wrap/Unwrap** — Convert between native and wrapped assets
* **Bubblemaps analysis** — Review holder clusters and create wallet groups for matching Sumo wallets
* **Claim creator fees** — Claim eligible creator fees on supported PumpFun/PumpSwap profiles
* **Change creator** — Permanently route future PumpFun/PumpSwap creator fees to one wallet or a percentage split; admin only
* **Create or Import** — Add new wallets

## Wallet Statuses

Sumo wallets have three statuses:

* **Active** — Wallet participates in strategies and shows in wallet selectors
* **Archived** — Wallet is excluded from new operations but balances remain queryable. You can unarchive wallets at any time to make them active again.
* **Excluded** — Wallet is intentionally kept out of trading and strategies. Excluded wallets appear in a separate **Excluded** tab so they cannot be accidentally reactivated during bulk operations. Common examples include deployment wallets used for launching tokens or pools that are never meant to trade.

The Excluded tab only appears in the profile navigation when at least one wallet has been excluded.

> **Status Changes Don't Move Funds**
>
> Excluding or archiving a wallet only changes its status in Sumo. Funds remain in the wallet on-chain. To move funds out, use [Withdraw](/treasury/withdraw) or [Swap Wallets](/treasury/swap-wallets).

### When to Exclude vs. Archive

| Scenario                                             | Recommended Status                            |
| ---------------------------------------------------- | --------------------------------------------- |
| Wallet temporarily out of service (e.g. low balance) | **Archived** — unarchive when ready           |
| Deployment wallet (token launch, pool creation)      | **Excluded** — never meant to trade           |
| Wallet replaced through Swap Wallets                 | **Archived** — funds already moved            |
| Wallet reserved for non-trading purposes             | **Excluded** — prevents accidental activation |

- [Generate Wallets](/wallets/generate-wallets): Create new wallets from a seed phrase.

- [Import Wallets](/wallets/import-wallets): Bring existing wallets into Sumo.


---

# Import Wallets

> Add wallets to a trading profile using private keys, Wallet Farm, Wallet Marketplace, or another profile.

- URL: https://docs.sumo.trade/wallets/import-wallets
- Markdown: https://docs.sumo.trade/wallets/import-wallets.md
- Docs index: https://docs.sumo.trade/llms.txt

Use this page when you want to add wallets you already control to a trading profile. If you want to buy aged wallet inventory instead, see [Wallet Marketplace](/wallets/wallet-marketplace).

## Import via Private Keys

![Import Wallets modal with private key input](/images/import-wallets.png)

1. Navigate to your profile's **Wallets** tab
2. Click **+ New Wallets**
3. Select the **Import Keys** tab
4. Paste your **private keys** — one per line, or comma-separated (up to 300)
5. Optionally assign a **wallet group**
6. Click **Confirm**

Sumo encrypts each private key and adds the wallets to your profile.

## Import from Wallet Farm

Use this when you prepared wallets in [Wallet Farm](/wallet-farm/overview) before the profile existed.

![Import From Farm modal with Wallet Farm folder selector and profile wallet group assignment](/images/profile-funding-from-farm.png)

1. Navigate to the target profile's **Wallets** tab
2. Click **+ New Wallets**
3. Select the **From Farm** tab
4. Choose one or more Wallet Farm folders
5. Optionally assign the imported wallets to a wallet group or create a new group
6. Click **Confirm**

Only active Wallet Farm wallets on the same chain are available for import.

## Import via Seed Phrase

You can also import a seed phrase to derive wallets from it:

1. Click **+ New Wallets** → **Create New** tab
2. Enter your existing **seed phrase** in the optional seed field
3. Choose how many wallets to derive
4. Click **Confirm**

Sumo derives wallets from your seed using the same BIP-44 HD derivation path it uses for generated seeds.

> **Key Security**
>
> Imported private keys and seed phrases are encrypted immediately using AES-256-GCM before storage. They never exist in plaintext in Sumo's database. See [Security & Encryption](/wallets/security-encryption) for details.

## Import from Another Profile

You can copy wallets from one profile to another within the same organization, without needing to re-enter private keys or seed phrases. This is useful when you want to reuse existing wallets across multiple token profiles — for example, using the same set of trading wallets on a new token launch.

![Import From Profile modal](/images/import-from-profile.png)

1. Navigate to the **target** profile's **Wallets** tab
2. Click **+ New Wallets**
3. Select the **From Profile** tab
4. Choose a **Source Profile** from the dropdown — only profiles on the same network are shown
5. Select source wallets, wallet groups, or all wallets from that profile
6. Optionally assign the imported wallets to a **wallet group** on the target profile (or create a new one)
7. Click **Confirm**

> **How It Works**
>
> Imported wallets are cloned into the target profile with an **archived** status. This means they won't participate in any active strategies until you explicitly activate them. Wallets that already exist in the target profile are skipped — no duplicates are created.

After import, you'll be redirected to the **Archived** tab where you can review and activate the imported wallets. Each import is recorded in the [Audit Logs](/reporting/audit-logs) for traceability.

- [Generate Wallets](/wallets/generate-wallets): Create fresh wallets directly in Sumo.

- [Wallet Marketplace](/wallets/wallet-marketplace): Buy aged wallet inventory into a profile or Wallet Farm.

- [Wallet Groups](/wallets/wallet-groups): Organize imported wallets into groups.


---

# Generate Wallets

> Generate new HD-derived wallets within Sumo.

- URL: https://docs.sumo.trade/wallets/generate-wallets
- Markdown: https://docs.sumo.trade/wallets/generate-wallets.md
- Docs index: https://docs.sumo.trade/llms.txt

![Generate Wallets modal](/images/generate-wallets.png)

Generate fresh wallets directly in Sumo. Sumo can create the wallets from your profile seed automatically, or you can provide your own seed phrase if you need deterministic wallets from an existing mnemonic.

## How to Generate

1. Navigate to your profile's **Wallets** tab
2. Click **+ New Wallets**
3. Select the **Create New** tab
4. Choose the **number of wallets** to generate (1–100)
5. Use the quick buttons for common counts: 5, 10, 15, or 20
6. Optionally assign a **wallet group**
7. Optionally provide your own **seed phrase** — if left blank, Sumo uses the profile seed or creates one automatically
8. Click **Confirm**

Sumo creates the seed (if not provided), derives the requested wallets, and adds them to your profile.

## Wallet Groups on Creation

You can assign wallets to a group during creation:

* Select an existing group from the list
* Or create a new group inline with a name and color

This saves time versus creating wallets first and grouping them later.

## Adding More Wallets

You can generate additional wallets at any time by repeating the process. New wallets are derived from the next available index in the seed, so they won't conflict with existing ones.

- [Import Wallets](/wallets/import-wallets): Import existing wallets using private keys.

- [Wallet Groups](/wallets/wallet-groups): Organize wallets into color-coded groups.


---

# Wallet Marketplace

> Buy aged wallet inventory into a trading profile or Wallet Farm.

- URL: https://docs.sumo.trade/wallets/wallet-marketplace
- Markdown: https://docs.sumo.trade/wallets/wallet-marketplace.md
- Docs index: https://docs.sumo.trade/llms.txt

Wallet Marketplace lets you buy aged wallet inventory instead of generating every wallet from a seed or importing private keys. Marketplace wallets have prior centralized-exchange funding and trading activity, so they are less likely to look like brand-new wallets on Bubblemaps or common token screeners. External classifications are not controlled by Sumo, so this should be treated as inventory history rather than a guaranteed label.

Use Wallet Marketplace when you need aged operational wallets quickly for a trading profile, a launch draft, or Wallet Farm preparation.

Marketplace inventory is chain-specific and is available on **Solana**, **Ethereum**, **Base**, **Robinhood Chain**, **BNB Chain**, and **Tron**. The purchase dialog shows the selected network, available inventory, wallet tier, unit price, total price, and the Sumo wallet used to pay for the purchase. It also shows inventory statistics for the selected tier: the average and range of native balance, confirmed swaps, and funding age across wallets currently in stock. These statistics are refreshed a few times a day, and the dialog notes when they were last updated. Pricing is charged from your Sumo Balance in the chain's native asset.

Two quality tiers are offered:

| Tier        | Inventory profile                                                                                |
| ----------- | ------------------------------------------------------------------------------------------------ |
| **Basic**   | Aged wallets with a small native balance, 10+ swaps, CEX funding history, and 7+ days of aging   |
| **Premium** | Aged wallets with a larger native balance, 20+ swaps, CEX funding history, and 10+ days of aging |

Per-wallet pricing by chain:

| Chain               | Basic    | Premium  |
| ------------------- | -------- | -------- |
| **Solana**          | 0.1 SOL  | 0.15 SOL |
| **Ethereum**        | 0.04 ETH | 0.06 ETH |
| **Base**            | 0.02 ETH | 0.04 ETH |
| **Robinhood Chain** | 0.02 ETH | 0.04 ETH |
| **BNB Chain**       | 0.03 BNB | 0.06 BNB |
| **Tron**            | 100 TRX  | 200 TRX  |

## When to Use It

Use Wallet Marketplace when:

* You need aged wallets without managing your own private-key import files
* You want aged wallets added directly to a profile or Wallet Farm folder
* You are preparing launch wallets and want to avoid starting only from newly generated addresses
* You want wallets with prior funding and trade history instead of brand-new wallet activity

Use generated wallets instead when you want deterministic wallets from your own seed. Use imported wallets when you already control the private keys you want Sumo to manage.

![Import From Marketplace modal](/images/import-wallet-marketplace.png)

## Buy Into a Trading Profile

Use this path when you want the purchased wallets attached directly to a token profile.

1. Navigate to the target profile's **Wallets** tab
2. Click **+ New Wallets**
3. Select the **Marketplace** tab
4. Choose the wallet quality tier
5. Enter the **Number of Wallets**
6. Optionally assign the purchased wallets to a wallet group or create a new group
7. Review the total price and click **Confirm**

Purchased wallets are added to the profile and can be organized with normal [wallet groups](/wallets/wallet-groups).

## Buy Into Wallet Farm

Use this path when you want wallets prepared outside a specific trading profile, then later imported into a launch or trading profile.

1. Open [Wallet Farm](/wallet-farm/overview)
2. Click **Add Wallets**
3. Select the **Marketplace** tab
4. Choose the target **Chain**
5. Choose the wallet quality tier
6. Enter the **Number of Wallets**
7. Optionally assign the purchased wallets to a folder or create a new folder
8. Review the total price and click **Confirm**

After purchase, you can fund the wallets, generate activity, and later [import them into a profile](/wallet-farm/import-to-profile).

## Launch Workflows

Launch wizards also support wallet creation and marketplace purchase paths. During wallet setup, you can create new wallets, import ready wallets, pull wallets from Wallet Farm, reuse wallets from another profile, or buy aged inventory from Wallet Marketplace.

- [Import Wallets](/wallets/import-wallets): Add wallets to a trading profile from keys, Wallet Farm, Marketplace, or another profile.

- [Wallet Farm](/wallet-farm/overview): Prepare marketplace wallets before assigning them to a profile.


---

# Wallet Groups

> Organize wallets into groups for batch operations and strategy assignment.

- URL: https://docs.sumo.trade/wallets/wallet-groups
- Markdown: https://docs.sumo.trade/wallets/wallet-groups.md
- Docs index: https://docs.sumo.trade/llms.txt

![Edit Wallet Groups modal](/images/wallet-groups.png)

Wallet groups let you organize wallets into named, color-coded sets. Groups are used throughout Sumo for strategy assignment, treasury operations, and batch actions.

## Why Use Groups

* **Strategy isolation** — Run Counter Trade on one group and DCA on another
* **Treasury operations** — Withdraw from or swap a specific group of wallets
* **Visual organization** — Color-coded indicators make it easy to identify wallets at a glance
* **Launch bundles** — Select a wallet group as buyer wallets for token launches

## Creating a Group

### During Wallet Creation

When generating or importing wallets, you can create a new group inline:

1. Click **Create New Group** in the wallet creation modal
2. Enter a **group name**
3. Pick a **color** from the palette
4. The new group is assigned to the wallets being created

### From the Wallets Page

1. Select one or more wallets using the checkboxes
2. Click the **Edit Wallet Groups** button in the toolbar
3. Create a new group or toggle existing groups on or off for the selected wallets
4. Click **Save Changes**

## Managing Groups

The Edit Wallet Groups modal shows all groups with:

* Color indicator
* Group name
* Member count
* Selection state relative to the selected wallets

Groups marked as mixed stay unchanged unless you toggle them. This makes it safe to bulk-edit several wallets without accidentally removing existing group assignments.

## Groups in Strategies

When creating a strategy, the **Wallet** selector lets you choose:

* **All wallets** — Ignores groups, uses everything
* **A specific group** — Only wallets in that group participate
* **An individual wallet** — Single wallet only

## Groups in Treasury

Treasury operations like [Withdraw](/treasury/withdraw), [Privacy Cashout](/treasury/privacy-cashout), and [Wrap/Unwrap](/treasury/wrap-unwrap) also support filtering by wallet group.

- [How Wallets Work](/wallets/how-wallets-work): Understand Sumo's wallet architecture.

- [Security & Encryption](/wallets/security-encryption): Learn how Sumo protects your keys.


---

# Security & Encryption

> How Sumo protects your wallet keys with enterprise-grade encryption.

- URL: https://docs.sumo.trade/wallets/security-encryption
- Markdown: https://docs.sumo.trade/wallets/security-encryption.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo takes wallet security seriously. Your seed phrases and private keys are protected with multiple layers of encryption, and never exist in plaintext in the application database.

## Encryption Architecture

### Envelope Encryption

Sumo uses **envelope encryption** — a two-layer encryption scheme:

1. **Data Encryption Key (DEK)** — Each seed/key is encrypted with its own unique AES-256-GCM key
2. **Key Encryption Key (KEK)** — The DEK is itself encrypted with a master key stored in a hardware security module (HSM) or Kubernetes secret

This means even if the database is compromised, the encrypted seeds are useless without the KEK.

### AES-256-GCM

All encryption uses **AES-256-GCM**, which provides:

* 256-bit encryption strength
* Authenticated encryption (tamper detection)
* Unique nonce per encryption operation

## Key Storage

* **Seed phrases and private keys** — Encrypted at rest in the database, never in plaintext
* **Master keys (KEK)** — Stored in HashiCorp Vault, AWS KMS, or Kubernetes secrets — never in the application database
* **Transaction signing** — Handled by a dedicated Rust signing service that decrypts keys only in memory for the duration of signing

## Signing Service

Transaction signing runs in a separate, isolated **Rust service**. This service:

* Decrypts keys only in memory, only when needed
* Signs transactions and immediately discards the plaintext key
* Runs as a separate process with restricted network access
* Never exposes private keys to the main application

> **Zero Plaintext Storage**
>
> At no point do plaintext private keys or seed phrases exist in Sumo's application database, logs, or API responses. Keys are decrypted only in the signing service's memory for the brief moment needed to sign a transaction.

## Multi-Tenant Isolation

Each organization's wallets and seeds are cryptographically isolated:

* Seeds are scoped to the organization that created them
* Cross-organization access is enforced at the database, API, and encryption layers

## Exporting Keys

Private keys leave Sumo only through an explicit export, and every export is restricted to the admin role and written to [Audit Logs](/reporting/audit-logs):

* **Export Deployer PK** in the profile's **Wallets** tab exports the single **deployer wallet** that created a launch, for launchpads and explorers that require the deployer to sign externally.
* **[Export Keys](/wallets/export-keys)** exports the wallets you select, in a profile's **Wallets** tab or in Wallet Farm. It is available only while the organization owner allows it — see [Key Export](/account/key-export).

Once a key has been exported, the wallet shows a key icon in the wallet table, indicating that its private key is now also held outside Sumo.

- [How Wallets Work](/wallets/how-wallets-work): Understand Sumo's wallet architecture.

- [Generate Wallets](/wallets/generate-wallets): Create new wallets with Sumo's secure key generation.

## Further Reading

* [Do You Need a Dev to Launch a Memecoin?](https://blog.sumo.trade/memecoin-launch-dev/) — why handing a stranger your keys is the real risk in most launches
* [How to Choose a Market Making Bot](https://blog.sumo.trade/how-to-choose-a-market-making-bot/) — wallet hygiene and custody as buying criteria


---

# Export Keys

> Export private keys for profile wallets or Wallet Farm wallets, and the org policy that controls who may.

- URL: https://docs.sumo.trade/wallets/export-keys
- Markdown: https://docs.sumo.trade/wallets/export-keys.md
- Docs index: https://docs.sumo.trade/llms.txt

**Export Keys** reveals the private keys of wallets you pick — in a profile's **Wallets** tab or in **Wallet Farm** — so you can hold them outside Sumo: in your own wallet app, a hardware signer, or cold storage. Both surfaces share the same policy, dialog, and limits.

## Who Can Export

Key export is off by default for everyone except the organization **owner**, and the owner controls it from **Settings → Key Export**:

| Toggle                                  | Effect                                                                                                           |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Allow me to export private keys**     | The owner may export. On by default.                                                                             |
| **Allow admins to export private keys** | Every admin and above may export, for **1 hour**, **24 hours**, or until the owner turns it off. Off by default. |

Both toggles are owner-only, and changing either one — in either direction — requires a one-time security code sent to your email or Telegram. Exports themselves never ask for a code: the policy is the gate.

Below the admin role, and while an account is being impersonated, export is unavailable regardless of the toggles.

## How to Export

**Profile wallets**

1. Open the profile's **Wallets** tab
2. Optionally check the wallets you want to export
3. Open the **More** menu in the toolbar and click **Export Keys**

**Wallet Farm**

1. Open **Wallet Farm** and pick the **Ready** or **In Progress** tab
2. Optionally check the wallets you want to export
3. Open the &#x2A;*⋯** menu in the toolbar and click **Export Keys**

Then, in the dialog:

4. Adjust the selection in the **Wallets** picker, with search and select-all. For profile wallets it lists every wallet of the profile — active, archived, and excluded — whatever tab is open; in Wallet Farm it lists every farm wallet in the current tab, whatever the search box shows
5. Type `EXPORT` to confirm
6. Copy the keys — per wallet, or **Copy all** for one key per line

The rows you checked in the table are preselected when the dialog opens, and the action is available even with nothing checked — pick the wallets in the dialog instead. In Wallet Farm only farm wallets can be exported; Marketplace wallets are excluded.

Up to **250 wallets** can be exported at once; above that the confirm button stays disabled until you narrow the selection. The keys clear from the screen automatically after 60 seconds, and closing the modal clears them immediately.

> **Reveal in private**
>
> Anyone holding a private key controls that wallet permanently. Reveal keys only on a machine you trust, and never share a screen while the keys are visible.

## Custody Changes to Shared

An exported wallet's custody flips from **Sumo** to **Shared**: the key now exists outside Sumo as well, and the wallet table marks it with a key icon. Custody never flips back — the export cannot be undone. Every export is written to [Audit Logs](/reporting/audit-logs).

- [Security & Encryption](/wallets/security-encryption): How Sumo stores and protects wallet keys.

- [Key Export Policy](/account/key-export): The owner-controlled setting that gates every export.


---

# Treasury Dashboard

> Overview of your treasury balances and wallet holdings.

- URL: https://docs.sumo.trade/treasury/treasury-dashboard
- Markdown: https://docs.sumo.trade/treasury/treasury-dashboard.md
- Docs index: https://docs.sumo.trade/llms.txt

![Treasury dashboard with metrics, live chart, and wallet table](/images/treasury-dashboard.png)

The Treasury Dashboard gives you a real-time view of a profile's market, treasury, and wallet state in one workspace. The top area shows the profile's live metrics and chart, while the wallet table below shows the wallets and actions used to manage funds.

## Treasury Metrics

The header summarizes the profile's current treasury position:

| Metric                | Description                                                                  |
| --------------------- | ---------------------------------------------------------------------------- |
| **Market Cap**        | Current market cap and token price                                           |
| **Token Supply**      | Percentage of total token supply held by the profile wallets, with USD value |
| **Treasury (Native)** | Total native asset balance across the profile wallets, with USD value        |
| **Treasury (Quote)**  | Total quote-token balance across the profile wallets, with USD value         |

Click **Refresh** to update balances and treasury metrics manually.

## Live Chart

The chart shows live price or market-cap action for the profile's pool. Use the interval buttons to change the candle size: **1s**, **1m**, **5m**, **15m**, **1h**, or **4h**.

You can also switch between chart overlays and views such as volume, market cap/price, and Sumo trade markers. This makes it easier to compare wallet inventory and strategy activity against market movement.

## Wallet Table

The wallet table below the chart shows the wallets attached to the profile. Use it to inspect balances, select wallets, and run wallet actions.

| Area            | Description                                                                                                         |
| --------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Wallet tabs** | Switch between Active, Archived, and Excluded wallets                                                               |
| **Search**      | Find a wallet by address or label                                                                                   |
| **Balances**    | Review native, quote, and token balances with USD values                                                            |
| **Supply**      | See each wallet's share of token supply and estimated value                                                         |
| **Actions**     | Copy addresses, edit wallet groups, toggle wallet status, filter rows, create new wallets, or open treasury actions |

The totals row at the bottom summarizes the selected wallet view, including wallet count, balances, token holdings, and supply value.

## Treasury and Wallet Actions

The profile workspace provides treasury operations through the Swap controls, Wallets toolbar, and wallet overflow menu:

* **Withdraw** - Send native assets, quote tokens, project tokens, or all balances to external destinations.
* **Treasury Swap** - Rotate treasury between native assets and supported stablecoins in either direction from the Swap modal.
* **Cross-Chain Swap** - Move value from a project wallet to an address on a different chain.
* **Privacy Cashout** - Distribute native assets or supported stablecoins through a privacy provider, using either a single source wallet or multiple source wallets.
* **Wrap / Unwrap Native** - Convert between the chain's native asset and wrapped native asset, such as SOL/WSOL or ETH/WETH.
* **Swap Wallets** - Rotate funds from selected wallets into fresh replacement wallets.
* **Token Cleanup** - Rebalance token holdings between wallet groups using direct transfers or buy/sell redistribution.
* **Bubblemaps Analysis** - Analyze holder clusters and optionally create wallet groups for matching Sumo wallets.
* **Claim Creator Fees** - Claim PumpFun/PumpSwap creator fees when the profile has an eligible creator wallet.
* **Change Creator** - Permanently route future PumpFun/PumpSwap creator fees to one wallet or a percentage split. Admin only.
* **Claim LP Fees** - Claim accrued liquidity-pool fees to the liquidity provider wallet for the profile's pool.
* **Wallet management** - Copy addresses, edit names or wallet groups, toggle status, filter rows, and add new wallets.

## Claiming Fees

Two fee-claim actions live in the wallet actions menu when the profile is eligible:

* **Claim Creator Fees** — For PumpFun/PumpSwap launch profiles with an eligible creator wallet. See [Creator Fee Claims](/launch-tokens/pumpfun-launch) for details.
* **Claim LP Fees** — For profiles whose pool position accrues liquidity fees. Select the liquidity provider wallet for the pool and confirm; claimed fees land in that wallet and the claim is recorded in Treasury Logs.

## Changing a Pump Creator

Admins can select **Change creator** for PumpFun and PumpSwap profiles to assign future creator fees to one recipient or split them between up to 10 recipients. The unique recipient shares must total exactly 100%, and the final split cannot be changed again after confirmation. See [Changing the Creator](/launch-tokens/pumpfun-launch#changing-the-creator) for eligibility and graduated-pool requirements.

- [Withdraw](/treasury/withdraw): Withdraw funds from your wallets.

- [Privacy Cashout](/treasury/privacy-cashout): Distribute funds through a privacy provider.

- [Treasury Swap](/treasury/stable-swap): Rotate between native assets and stablecoins.

- [Cross-Chain Swap](/treasury/cross-chain-swap): Move funds to a wallet on another chain.

- [Wrap / Unwrap](/treasury/wrap-unwrap): Convert between native and wrapped assets.

- [Swap Wallets](/treasury/swap-wallets): Rotate funds into fresh wallets.

- [Token Cleanup](/treasury/token-cleanup): Rebalance token holdings between wallet groups.


---

# Withdraw

> Withdraw funds from your Sumo wallets to external addresses.

- URL: https://docs.sumo.trade/treasury/withdraw
- Markdown: https://docs.sumo.trade/treasury/withdraw.md
- Docs index: https://docs.sumo.trade/llms.txt

Withdraw lets you send native assets, quote tokens, project tokens, or all balances from your Sumo wallets to one or more external destination addresses.

> **Video: How to Withdraw Funds From Sumo**
>
> A walkthrough of single and multi-destination withdrawals, source wallet selection, fee settings, and transfer grouping.
>
> https://www.youtube.com/watch?v=ZHTGizS-2E4

## How to Withdraw

1. Open the profile's **Wallets** tab and click **Withdraw**
2. Select the **source wallets** — all wallets, a wallet group, or individual wallets
3. Choose a **destination mode** (single or multi)
4. Enter amounts and destination addresses
5. Click **Continue** to review the transfer plan and network fees
6. Click **Withdraw** to execute

## Destination Modes

### Single Destination

![Single Destination Withdraw modal](/images/withdraw.png)

Send funds from your source wallets to a single external address:

* Enter the **destination address**
* Set the **native amount** (or toggle **Sweep** to send all available native balance)
* Select the token asset and set the **token amount** (or toggle **Sweep** to send all of that token)
* Choose whether entered amounts are gross before fees or net after fees
* Choose how transfers are grouped per source wallet

### Multi Destination

![Multi Destination Withdraw modal](/images/withdraw-multi-destination.png)

Send funds to multiple addresses in one operation:

* **Interactive mode** — Add destination rows with address, native amount, and token amount
* **CSV mode** — Paste destination rows in the same format: `address,nativeAmount,tokenAmount`

Multi-destination withdrawals use explicit per-row amounts. Sweep is only available in Single Destination mode.

## Distribution Strategy

The distribution strategy controls how the total amount is drawn from the selected source wallets:

| Strategy       | Description                                                                                                        |
| -------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Rebalance**  | Default. Draws more from higher-balance wallets first so remaining balances even out                               |
| **Pro-rata**   | Each source wallet contributes proportionally from its available balance                                           |
| **Even split** | Each source wallet contributes the same amount                                                                     |
| **One to one** | Each source wallet maps to one destination row. Not available together with Sweep, and limited to 200 destinations |

## Transfer Batching

On Solana, the **Transfer Batching** setting chooses between **Multiple** (default) — consolidated transactions covering several source wallets — and **Single** — one transaction per source wallet. EVM and Tron withdrawals always send one transaction per source wallet.

## Amount Modes

| Mode                    | Description                                                                              |
| ----------------------- | ---------------------------------------------------------------------------------------- |
| **Gross (before fees)** | The amount you enter is the total sent — applicable fees are deducted from it            |
| **Net (after fees)**    | The amount you enter is what the destination receives — applicable fees are added on top |

## Destinations and Roles

Withdrawals support up to 2,000 destinations per request on Solana, 250 on EVM chains, and 200 on Tron.

Traders can withdraw to wallets managed by the same organization on the same chain. Withdrawing to external destination addresses requires the admin role or higher.

## Withdrawing from a Launch Profile

Pre-launch profiles have a simplified **Withdraw Funds** dialog for recovering funds from launch wallets before trading opens. It sweeps the native asset — and the quote token where the launch uses one — from the selected wallets to a single destination address. Empty wallets are skipped.

The launch variant intentionally omits the full withdraw controls: there are no destination modes, distribution strategies, or amount modes. Select the source wallets, paste the destination, and confirm. For everything else on this page, use the regular Withdraw from an active profile.

## Fees

> **No Withdrawal Platform Fee**
>
> Withdrawals do not have a Sumo platform fee. Source wallets still pay normal chain transaction fees. See [Platform Fees](/platform-fees) for details.

The preview step shows the transfer plan and estimated network fees before you confirm.

- [Privacy Cashout](/treasury/privacy-cashout): Move native assets or supported stablecoins privately between wallets.

- [Swap Wallets](/treasury/swap-wallets): Move funds to fresh wallets.


---

# Airdrops

> Send the project token to holders or a pasted address list with batched, monitored airdrop campaigns.

- URL: https://docs.sumo.trade/treasury/airdrops
- Markdown: https://docs.sumo.trade/treasury/airdrops.md
- Docs index: https://docs.sumo.trade/llms.txt

Airdrops let you send the project base token to up to 50,000 recipients in one campaign. On Solana you can target current holders of any token or a pasted address list; on EVM chains Sumo distributes through the Gaslite Drop contract to a pasted address list.

## Supported Chains

| Chain                | Recipient sources             | Mechanic                                                                   |
| -------------------- | ----------------------------- | -------------------------------------------------------------------------- |
| **Solana Mainnet**   | Token Holders or Address List | SPL / Token-2022 transfers with automatic recipient token-account creation |
| **Ethereum Mainnet** | Address List                  | Gaslite Drop batched ERC-20 transfers                                      |
| **BNB Smart Chain**  | Address List                  | Gaslite Drop batched ERC-20 transfers                                      |
| **Base Mainnet**     | Address List                  | Gaslite Drop batched ERC-20 transfers                                      |
| **Robinhood Chain**  | Address List                  | Gaslite Drop batched ERC-20 transfers                                      |
| **Stable Mainnet**   | Address List                  | Gaslite Drop batched ERC-20 transfers                                      |

Airdrops always send the **project base token**. Native assets and stablecoins cannot be airdropped from this flow.

## How to Create an Airdrop

1. Open the profile's **Strategies** tab
2. Click the **Create airdrop** button in the toolbar (next to Create Strategy)
3. Choose the recipient source: **Token Holders** (Solana) or **Address List**
4. Select the **source wallets** that will fund the airdrop
5. Set **Tokens Per Recipient** and any optional filters or advanced settings
6. Review the estimate and click **Create Airdrop**

Creating airdrops requires the trader role or higher. The airdrop button only appears on supported chains, and it is disabled in read-only Client Portal views.

## Recipient Sources

### Token Holders (Solana)

Paste any token address into **Holders To Reward** — the project token is offered as a preset. Sumo estimates the current holder count and total supply before you submit. Optional filters:

| Setting                      | Description                                                                                                                                                        |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Min / Max Holder Balance** | Only reward holders inside a balance range.                                                                                                                        |
| **Balance Unit**             | Express the filter in **Tokens** or &#x2A;*Supply %**.                                                                                                             |
| **Recipient Type**           | Controls whether program-owned addresses can receive the airdrop: normal wallets and multisigs (default), normal wallets only, or include program-owned addresses. |

### Address List

Paste recipient addresses — one per line, or separated by commas or spaces. Duplicates are removed automatically, invalid addresses are counted below the input, and campaigns support up to **50,000 unique addresses**.

## Amounts and Source Wallets

| Setting                   | Description                                                                                                                                                     |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Token To Send**         | Locked to the project base token.                                                                                                                               |
| **Source Wallets**        | Wallet groups or individual wallets that fund the airdrop. Nothing is preselected - you must choose the source wallets explicitly. Locked wallets are excluded. |
| **Tokens Per Recipient**  | Fixed amount per recipient, or set an optional max for randomized per-recipient sizing between min and max.                                                     |
| **Recipient Count Range** | Optional min/max recipient count. Leave blank to use all eligible recipients.                                                                                   |

The modal previews the combined native and token balances of the selected source wallets, and the estimate card shows recipient count, token maximum, execution time, and estimated cost before you submit.

> **Coupled Token and Gas Capacity**
>
> Each source wallet must hold both the tokens and the native asset needed for its share of recipients. On Solana, roughly 0.002 SOL rent is reserved per new recipient token account; on EVM, gas for the Gaslite batches is priced at current fees. A wallet with tokens but no native balance contributes zero capacity, and Sumo rejects the airdrop if the selected wallets cannot cover all recipients.

## Advanced Settings

| Setting                              | Description                                                                              |
| ------------------------------------ | ---------------------------------------------------------------------------------------- |
| **Transaction Batch Size**           | How many planned transactions execute per batch window: 1 (default) to 4.                |
| **Delay Between Batches In Seconds** | Optional pause after each batch, up to 86,400 seconds. Leave at 0 for fastest execution. |

Batching happens automatically underneath: Solana packs up to 9 recipients per transaction (10 once a campaign lookup table is prepared for larger runs), and EVM packs up to 100 recipients per Gaslite call, preceded by the required token approval.

## Monitoring

Airdrops run in the background after submission.

* **Last Airdrop** — The button in the airdrop modal opens the latest campaign status, with recipient and transaction progress meters and any error detail. Campaign statuses move through Planning, Planned, Executing, and end at Completed, Partial Failed, Failed, or Canceled.
* **Airdrop Logs** — Supported profiles add an **Airdrop Logs** tab to the Logs workspace with per-transaction rows: date, source, recipients, amount, status, and the explorer link. Search accepts a campaign ID or a transaction signature.

- [Withdraw](/treasury/withdraw): Send balances to external addresses instead of holder distributions.

- [Token Cleanup](/treasury/token-cleanup): Rebalance token holdings between wallet groups.


---

# Treasury Swap

> Swap between native treasury assets, stablecoins, and a custom quote token in either direction.

- URL: https://docs.sumo.trade/treasury/stable-swap
- Markdown: https://docs.sumo.trade/treasury/stable-swap.md
- Docs index: https://docs.sumo.trade/llms.txt

Treasury Swap helps you rotate treasury balances between a profile's native asset, supported stablecoins, and the profile's quote token. Use it when you want to derisk native exposure into stablecoins, move stablecoin balances back into SOL, ETH, BNB, or another native asset for trading and operations, or convert native into a custom quote token so buy strategies have something to spend.

![Treasury Swap modal](/images/stable-swap-modal.png)

## When to Use It

* You want to derisk treasury balances after funding wallets or after a trading campaign
* You want to convert stablecoin treasury back into native assets before trading or funding gas-heavy operations
* You want stablecoin balances available on the same profile wallets
* Your profile trades against a custom quote token (for example a stock token on Robinhood Chain) and your wallets were funded with the native asset, so you need to convert some native into the quote before buys can run
* You want to rebalance selected wallets, one wallet group, or all active wallets
* You want Sumo to quote and execute the native-to-stable or stable-to-native route through the supported aggregator for the project chain

Treasury Swap is not a privacy tool. If you need to break the visible link between source and destination wallets, use [Privacy Cashout](/treasury/privacy-cashout) instead.

## Fees

Every treasury swap pays a Sumo platform fee of 0.5% (50 bps) by default, already reflected in the live quote. The fee is normally taken from the asset you sell; it is never taken from your project token, and some routes can only collect it from the asset you buy. Organizations can carry a different rate, and profiles in the custom-fee program can raise their own rate above the organization minimum from **Profile Settings → Custom Fees**. Launch funding and AutoFix refills that route through Treasury Swap pay the same fee. Tron swaps execute fee-free. Wallets that cannot cover their own gas swap through a gasless provider: on EVM chains that provider collects the same fee, while on Solana the gasless leg executes fee-free.

## How to Use

1. Open the profile's **Wallets** tab
2. Click **Swap**
3. Select the **Treasury Swap** tab
4. Enter the amount
5. Choose the **From** asset, then the **To** asset. The **To** list only offers assets that pair with your **From** choice; use the arrow button to reverse the pair
6. Select the wallet target: all wallets, selected wallets, one wallet, or a wallet group
7. Choose the allocation mode
8. Review the live quote and click **Treasury Swap**

The quote refreshes while the payload is valid. After submission, Sumo records the action in Treasury logs and updates balances once the transaction flow completes.

## Allocation Modes

| Mode                 | Description                                                                                                          |
| -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Pro-rata**         | Pulls from the selected wallets proportionally based on available input balance.                                     |
| **Rebalance**        | Pulls more from higher-balance wallets first so the selected wallets end closer to the same remaining input balance. |
| **Fixed per wallet** | Uses the same input amount for each selected wallet.                                                                 |

Use pro-rata when you want to rotate a total treasury amount across several wallets without changing the relative wallet weights too much. Use rebalance when one or more wallets are heavier and you want the swap to even out the remaining balances. Use fixed per wallet when each selected wallet should swap the same amount.

## Supported Chains and Assets

Treasury Swap supports the native asset, the registered stablecoins for the project chain, and the profile's project and quote tokens. Every pair has exactly one stablecoin side, with one exception: a custom quote token (a quote that is neither a stablecoin nor the wrapped native asset) also pairs directly with the native asset, except on Tron. The **From** selector lists every asset with at least one valid partner, and the **To** selector lists only the assets that pair with it.

| Chain                                                | Providers                               |
| ---------------------------------------------------- | --------------------------------------- |
| **Solana**                                           | Best (default), Jupiter, DFlow, OKX DEX |
| **Ethereum, BNB Smart Chain, Base, Robinhood Chain** | Best (default), 0x, Uniswap API         |
| **Ethereum Sepolia**                                 | Uniswap API                             |
| **HyperEVM**                                         | 0x                                      |
| **Tron**                                             | SunSwap TRX/USDT pools                  |

**Best** quotes every provider available on the chain and executes through the one returning the most output. A provider that fails to quote is skipped, so a single provider outage does not block the swap. The quote row shows which provider was selected. Pick a specific provider to route through it exclusively.

Treasury Swap is not available on Stable Mainnet, where treasury balances are already stablecoin-denominated.

Examples:

* SOL to USDC on Solana
* USDC to SOL on Solana
* ETH to USDC on Ethereum or Base
* USDC to ETH on Ethereum or Base
* BNB to USDC or another supported stablecoin on BNB Smart Chain
* ETH to a custom quote token such as a stock token on Robinhood Chain, and back
* TRX to USDT on Tron

## Logs and Confirmations

After you submit a treasury swap:

1. Sumo submits the source transaction through the chain-specific execution path
2. Treasury logs show the submitted action
3. Balances refresh after confirmation
4. Failed swaps show the parsed failure reason in logs when available

- [Cross-Chain Swap](/treasury/cross-chain-swap): Move value between different chains.

- [Privacy Cashout](/treasury/privacy-cashout): Move funds privately through a provider.


---

# Custom Swap

> Trade an allowlisted custom token against a known profile asset across your wallets.

- URL: https://docs.sumo.trade/treasury/custom-swap
- Markdown: https://docs.sumo.trade/treasury/custom-swap.md
- Docs index: https://docs.sumo.trade/llms.txt

Custom Swap trades a token you have explicitly allowlisted on the profile against one of the profile's known assets — the project token, the native asset, the quote asset, or a registered stablecoin. Use it when treasury wallets hold, or need to hold, a token that is not part of the profile's own pair.

![Custom Swap tab of the Swap Tokens modal](/images/custom-swap-modal.png)

## When to Use It

* Wallets received an airdrop or an unsolicited token and you want to convert it into a known asset
* You want to move idle treasury into a yield-bearing asset — for example, converting SOL into a staked SOL token like JitoSOL or mSOL, which is neither a stablecoin nor the profile's quote asset
* You need to acquire a specific outside token for operations — seeding a partner liquidity pool, paying a vendor in their token, or holding an ecosystem token the project has committed to
* You are exiting a position in a token you no longer want spread across treasury wallets

The tab only appears when the profile's chain supports Custom Swap and there is something to trade — or when you are an admin, who can add the first token inline.

## Allowlisting a Custom Token

Tokens are not tradeable until an admin allows them. This is deliberate: the allowlist is what keeps a treasury swap from being pointed at an arbitrary address.

To add one from the modal:

1. Open the **Custom Swap** tab
2. Paste the token address into the **Add Custom Token** field
3. Pick the resolved token from the list — Sumo reads its symbol, name, and decimals on-chain
4. Click **Add**

The token becomes available to every wallet on the profile immediately. Non-admin members can trade allowlisted tokens but cannot add new ones.

To remove a token, open [Profile Settings](/getting-started/profile-settings) and use the **Custom Tokens** section. There is no delete control in the swap modal, so a token cannot be dropped mid-trade by accident.

## How to Use

1. Open the profile's **Wallets** tab and click **Swap**
2. Select the **Custom Swap** tab
3. Choose the custom token and the known asset, using the reverse control to set the direction
4. Enter the amount
5. Select the wallet target: all wallets, selected wallets, one wallet, or a wallet group
6. Choose the provider
7. Choose the allocation mode
8. Set slippage — custom tokens are volatile, so allow more room than you would on a stable pair
9. Review the live quote and click **Custom Swap**

## Allocation Modes

| Mode                 | Description                                                                                                          |
| -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Pro-rata**         | Pulls from the selected wallets proportionally based on available input balance.                                     |
| **Rebalance**        | Pulls more from higher-balance wallets first so the selected wallets end closer to the same remaining input balance. |
| **Fixed per wallet** | Uses the same input amount for each selected wallet.                                                                 |

Use pro-rata to move a total amount without changing relative wallet weights. Use rebalance when some wallets are heavier and you want the remainder evened out. Use fixed per wallet when each selected wallet should swap the same amount.

## Fees

Custom Swap charges the standard platform swap fee — the same fee that applies to instant trades. See [Platform Fees](/platform-fees) for the rates.

## Supported Chains and Providers

| Chain                                                | Providers                               |
| ---------------------------------------------------- | --------------------------------------- |
| **Solana**                                           | Best (default), Jupiter, DFlow, OKX DEX |
| **Ethereum, BNB Smart Chain, Base, Robinhood Chain** | Best (default), 0x, Uniswap API         |

**Best** quotes every provider on the chain and executes through the one returning the most output, skipping any provider that fails to quote. Custom Swap is not available on Tron or Stable Mainnet.

## Logs and Confirmations

After you submit a custom swap:

1. Sumo submits the source transaction through the chain-specific execution path
2. Treasury logs record the action as **Custom swap**
3. Balances refresh after confirmation
4. Failed swaps show the parsed failure reason in logs when available

- [Treasury Swap](/treasury/stable-swap): Rotate between native assets, stablecoins, and the quote token for a 0.5% fee.

- [Token Cleanup](/treasury/token-cleanup): Redistribute or clear the project token across wallets.


---

# Cross-Chain Swap

> Move value between supported chains from project wallets or between Wallet Farm wallets.

- URL: https://docs.sumo.trade/treasury/cross-chain-swap
- Markdown: https://docs.sumo.trade/treasury/cross-chain-swap.md
- Docs index: https://docs.sumo.trade/llms.txt

Cross-Chain Swap moves value between wallets on different chains. Supported chains are Solana, Ethereum, BNB Smart Chain, Base, Stable, Robinhood Chain, and Tron. It is available in two places:

* **Project Wallets** — intended as a cross-chain cashout or withdrawal from a project wallet to an address on a different chain.
* **Wallet Farm** — intended for swapping between two Wallet Farm wallets on different chains inside the same organization.

## Project Wallets

Use the project-scoped flow when funds are in a profile wallet and the destination is an external address on another chain. The destination chain must be different from the profile's chain.

![Project Cross-Chain Swap modal](/images/cross-chain-swap-modal.png)

1. Open the profile's **Wallets** tab
2. Open the wallet actions menu
3. Click **Cross-chain swap**
4. Choose the provider, or leave it as **Best**
5. Select the source wallet
6. Enter the destination address
7. Enter the source amount and source asset
8. Select the destination chain and destination asset
9. Review the quote, minimum received, and total fee
10. Click **Swap**

For EVM source chains, the modal can use private relay execution. For Solana source chains, Sumo builds the transaction with the normal Solana execution path used by the app.

## Wallet Farm

Use the Wallet Farm flow when both sides are Wallet Farm wallets and you want to move value between chains without first importing either wallet into a project.

![Wallet Farm Cross-Chain Swap modal](/images/wallet-farm-cross-chain-swap-modal.png)

1. Open **Wallet Farm**
2. Click **Cross-Chain Swap**
3. Choose the provider, or leave it as **Best**
4. Select the source Wallet Farm wallet
5. Enter the source amount and asset
6. Select the destination Wallet Farm wallet on a different chain
7. Select the destination asset
8. Review the quote, minimum received, and total fee
9. Click **Swap**

Wallet Farm also includes a switch-direction button once both wallets are selected. The destination options are filtered to wallets on a different chain from the selected source wallet.

## Providers and Quotes

Cross-chain quotes can be requested from a specific provider — **0x**, **Relay**, **Mayan**, or **deBridge** — or through **Best**. When **Best** is selected, Sumo compares supported providers and returns the best quote, with runner-up quotes available when multiple providers return valid routes.

Provider availability depends on the route: routes touching Stable use Relay; routes touching Robinhood Chain use 0x or Relay; routes touching Tron use 0x, deBridge, or Relay; other routes can use any provider.

The quote shows:

* **Quote** — selected provider and route summary
* **Minimum received** — the amount protected by the selected slippage setting
* **Sumo / Provider Fee** — total fee percentage shown as one combined fee

Provider availability depends on the source chain, destination chain, and selected assets.

## Fees

Cross-chain swaps show the provider fees and Sumo fee together in the quote summary. Cashout fees configured for a project or organization are not applied to cross-chain swaps; when such fees exist, the modal shows a warning.

## Logs and Notifications

After submission:

1. Sumo records a Treasury audit log for the cross-chain swap
2. The source transaction is submitted and confirmed
3. A background job polls the provider until the destination side is complete or failed
4. Logs and notifications are updated with the destination transaction link when available

For project-scoped swaps, the activity appears in the project's Treasury logs. For Wallet Farm swaps, the activity appears in Wallet Farm activity logs.

- [Treasury Swap](/treasury/stable-swap): Rotate treasury balances between native assets and stablecoins.

- [Privacy Cashout](/treasury/privacy-cashout): Move funds privately through a provider.


---

# Privacy Cashout

> Move native assets and supported stablecoins privately between wallets using third-party privacy providers.

- URL: https://docs.sumo.trade/treasury/privacy-cashout
- Markdown: https://docs.sumo.trade/treasury/privacy-cashout.md
- Docs index: https://docs.sumo.trade/llms.txt

Privacy Cashout lets you move funds to destination wallets without creating a direct on-chain link between the source and destination wallets. It is useful for distributing funds across trading wallets, rotating funds between wallets, or separating trading wallets from the original funding source.

> **Video: How to Use Privacy Cashout**
>
> A walkthrough of single-source and multi-source privacy cashouts, provider choices, destination splits, and delivery settings.
>
> https://www.youtube.com/watch?v=fxp5KAwjqjQ

## How It Works

Instead of sending funds directly wallet-to-wallet, Sumo routes funds through a third-party privacy provider that breaks the visible on-chain connection between the source side and destination side.

## Supported Chains and Assets

Privacy Cashout is available on Solana, Ethereum, BNB Smart Chain, Base, Robinhood Chain, and Tron mainnet. It is not available on Stable Mainnet.

| Chain               | Native | Stablecoins                      |
| ------------------- | ------ | -------------------------------- |
| **Solana**          | SOL    | USDC, USDT, USD1                 |
| **Ethereum**        | ETH    | USDC, USDT; USD1 via Husher only |
| **BNB Smart Chain** | BNB    | USDC, USDT (Husher only)         |
| **Base**            | ETH    | USDC (Husher only)               |
| **Robinhood Chain** | ETH    | Native ETH only                  |
| **Tron**            | TRX    | USDT                             |

Stablecoin swaps are same-stablecoin only, such as USDC to USDC or USDT to USDT. The asset selector only shows assets available for the selected profile chain, provider, and source wallets.

## Supported Providers

| Provider     | Features                                     |
| ------------ | -------------------------------------------- |
| **Husher**   | Time-staggered delivery for enhanced privacy |
| **SplitNOW** | Instant distribution                         |

Robinhood Chain privacy cashouts route through Husher only.

## Source Modes

### Single Source

![Single Source Privacy Cashout dialog](/images/privacy-cashout.png)

Use **Single Source** when one wallet holds the funds you want to distribute.

1. Open the profile’s **Wallets** tab and click **Privacy cashout** from the wallet actions menu
2. Select **Single Source**
3. Select a **provider** (Husher or SplitNOW)
4. Select the **source wallet**
5. Enter the amount and choose the asset
6. Choose **amount mode** — Gross before fees or Net after fees
7. Optionally set a staggered time delay in minutes and choose the allowed exchanges (Husher only)
8. Configure destination wallets and percentage splits
9. Click **Preview** to review fees and amounts, then confirm to execute

### Multiple Source

![Multiple Source Privacy Cashout dialog](/images/privacy-cashout-multi-source.png)

Use **Multiple Source** when you want several source wallets or wallet groups to contribute to one privacy swap.

1. Select **Multiple Source**
2. Select one or more source wallets or wallet groups
3. Choose the allocation mode
4. Enter the gross total amount and choose the asset
5. Choose **amount mode** — Gross before fees or Net after fees
6. Configure destination wallets and percentage splits
7. Click **Preview** to review source allocations, fees, and destination amounts, then confirm to execute

Multiple Source supports two allocation modes:

| Mode          | Description                                                                       |
| ------------- | --------------------------------------------------------------------------------- |
| **Pro-rata**  | Each source wallet contributes proportionally from its available balance          |
| **Rebalance** | Sumo plans contributions to draw more from wallets with higher available balances |

## Destination Configuration

Single-source and multiple-source privacy cashouts use the same destination split editor.

### Interactive Mode

Add destination wallets one by one:

* Enter or select a wallet address
* Set the percentage each wallet receives
* Use **Split Evenly** to distribute equally across all destinations
* Add more destinations as needed

### CSV Mode

Paste destinations in CSV format:

```
walletAddress,60.00
walletAddress2,30.00
walletAddress3,10.00
```

Values are percentages. The total across all destinations must equal 100%. Privacy cashouts support up to 200 destination wallets.

## Exchange Controls (Husher)

Husher swaps route through centralized-exchange accounts. The **Allowed Exchanges** multi-select restricts which exchanges can be used, and **Rotate Exchanges** varies the exchange used across destinations for additional separation.

**All Exchanges** covers the default tier. The **Opt-in** group below it (ChangeNOW, SideShift) is never used unless you tick it, on any chain including Robinhood. Opt-in exchanges carry their own minimum per leg; ChangeNOW in particular charges a flat fee of about 0.01 ETH, so it is only worth selecting for legs of roughly 0.05 ETH or more. Legs below an opt-in minimum rotate to another allowed exchange, and the quote fails with a clear message if none remains.

## Fees

The preview step shows:

* **Provider fee** — Charged by the privacy provider
* **Sumo fee** — Platform fee
* **Net total** — What destinations actually receive

> **Common Use Case**
>
> Fund one wallet from an exchange, then use Privacy Cashout to distribute to your trading wallets. This way, your trading wallets have no direct on-chain link to each other or to your exchange account.

- [Withdraw](/treasury/withdraw): Standard withdrawals to external addresses.

- [Swap Wallets](/treasury/swap-wallets): Move funds to fresh wallets.


---

# Swap Wallets

> Sweep balances from source wallets into fresh wallets, existing wallets, or a list of addresses.

- URL: https://docs.sumo.trade/treasury/swap-wallets
- Markdown: https://docs.sumo.trade/treasury/swap-wallets.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Swap Wallet Example**
>
> A walkthrough of replacing existing wallets with fresh wallets while preserving assignments and moving supported balances.
>
> https://www.youtube.com/watch?v=Z98n1hsekPw

![Swap Wallets modal with source wallets, destination mode, and assets to sweep](/images/swap-wallets.png)

Swap Wallets sweeps balances out of selected wallets — into freshly derived replacement wallets, into existing project wallets you pick, or into a pasted list of addresses that may mix profile wallets and external addresses. On a full sweep, Sumo also rotates the wallet identity: group and strategy assignments move to the destination wallets and the old wallets are archived. It is supported on Solana, EVM, and Tron profiles.

## When to Use

* **Fresh addresses** — Continue operations from new wallet addresses
* **Wallet hygiene** — Rotate wallets after a launch, trading campaign, or funding cycle
* **Retiring wallets** — Move balances out of wallets you no longer want to use
* **Consolidating** — Sweep specific assets from some wallets into other wallets you already hold
* **Draining to external wallets** — Sweep everything a wallet holds to addresses outside Sumo in one step

## How to Use

1. Open the profile's **Wallets** tab
2. Select one or more wallets
3. Open the wallet actions menu and click **Swap wallets**
4. Review the **Source Wallets** — pre-filled from your selection; adjust by wallet or group
5. Choose the **Destination** mode
6. Choose the **Assets to Sweep**
7. Click **Swap Wallets**

Use this when you want the selected wallets replaced or drained, one destination per source. To send chosen amounts from many wallets to one or more destinations, use [Withdraw](/treasury/withdraw) instead.

## Destination

| Mode                 | Description                                                                                                                                                                                    |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New Wallets**      | Sumo derives one fresh replacement wallet per source wallet. Available for full sweeps only.                                                                                                   |
| **Existing Wallets** | You pick destination wallets from the profile, one per source wallet.                                                                                                                          |
| **Addresses**        | You paste one address per source wallet, one per line or comma-separated. Addresses that belong to profile wallets are treated as those wallets; any other address is an external destination. |

A partial sweep into freshly derived wallets would strand the unswept assets in an archived wallet, so partial sweeps always target existing wallets or addresses.

External addresses receive the sweep only. On a full sweep the source wallets are still archived and leave their groups, but no group or strategy assignment moves to an external address. If that empties a group, any active strategy assigned only to that group is deactivated. Pasting external addresses requires the admin role, the same rule as Withdraw; traders can paste addresses of wallets the organization manages. Addresses that cannot be a wallet are rejected before anything moves: on Solana, program-derived addresses and existing token or program accounts; on EVM, contract addresses. Tron addresses are not checked.

## Assets to Sweep

Toggle which balances move: the native asset, the project token, the quote asset, and the profile's stablecoin where enabled. On profiles that trade with native, the quote is the wrapped native asset, so there is no separate quote toggle.

The selection decides what kind of operation runs:

* **Full sweep** (every asset selected) — balances move, group and strategy assignments transfer to the destination wallets, and the source wallets are archived. This is the classic wallet rotation.
* **Partial sweep** (some assets deselected) — only the selected assets are transferred. Source wallets keep their groups and stay active.

The summary line above the confirm button states which of the two will happen before you commit.

## What Happens

1. Sumo derives fresh wallets (New Wallets mode) or uses your chosen destinations (Existing Wallets or Addresses mode)
2. The selected asset balances are moved from the source wallets to the destinations
3. On a full sweep, wallet groups and strategy assignments are updated to point at the destination wallets (external addresses are skipped)
4. On a full sweep, the source wallets are archived — they stay available for history but are not reused for new operations

- [Token Cleanup](/treasury/token-cleanup): Migrate tokens between wallet groups via swaps.

- [Withdraw](/treasury/withdraw): Send funds to external addresses instead.


---

# Token Cleanup

> Rebalance token holdings between wallet groups using direct transfers or buy/sell redistribution.

- URL: https://docs.sumo.trade/treasury/token-cleanup
- Markdown: https://docs.sumo.trade/treasury/token-cleanup.md
- Docs index: https://docs.sumo.trade/llms.txt

![Token Cleanup modal](/images/token-cleanup.png)

Token Cleanup lets you rebalance project-token holdings from one wallet group to another. You can either transfer tokens directly to the destination group or use buy/sell redistribution where source wallets sell on the DEX and destination wallets buy back through the same market.

Token Cleanup is available on Solana and EVM profiles. Both support direct transfer and buy/sell redistribution. EVM transfer mode uses batched Gaslite transfers; EVM buy/sell mode uses direct Uniswap V2, V3, or V4 execution against a wrapped-native quote pool. Tron profiles do not have token cleanup.

## When to Use

* **Rebalancing** — Redistribute token holdings across a different set of wallets
* **Group rotation** — Move positions to a fresh wallet group after generating new wallets
* **Portfolio restructuring** — Consolidate or spread holdings as your profile changes

## How to Use

1. Open the profile's **Wallets** tab
2. Click **Token Cleanup** from the wallet actions menu
3. Select the **Redistribution Mode**
4. Select the **source wallet group**
5. Select the **destination wallet group**
6. Configure the cleanup parameters
7. Click **Continue** to review the plan
8. Click **Start Token Cleanup** to execute

## Redistribution Mode

| Mode               | Description                                                                                                                                                                                                             |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Token Transfer** | Sends project tokens directly from source wallets to destination wallets. This avoids swap slippage and DEX fees, and is best when you only need to move balances between wallet groups.                                |
| **Buy/Sell**       | Source wallets sell project tokens on the DEX and destination wallets buy them back. This creates market activity, but proceeds are affected by slippage, DEX fees, token taxes, gas, and the configured safety buffer. |

Buy/Sell is the default mode (on Solana it also enables the Sender Max bundle by default, so each source sell and destination buy lands atomically). Switch to Token Transfer when you only need to move balances between wallet groups without market activity.

## Configuration

The available fields depend on the redistribution mode.

### Token Transfer

| Setting                      | Description                                                                                    |
| ---------------------------- | ---------------------------------------------------------------------------------------------- |
| **Source Wallet Group**      | Wallets that will send project tokens.                                                         |
| **Destination Wallet Group** | Wallets that will receive project tokens.                                                      |
| **Spread (%)**               | Adds randomness around each destination wallet's token transfer split.                         |
| **Delay (seconds)**          | Pause after each completed transfer.                                                           |
| **SOL Per Wallet**           | Extra SOL sent to each destination wallet after its token transfer.                            |
| **SOL Jitter (%)**           | Adds randomness around the SOL top-up amount.                                                  |
| **Quote Per Wallet**         | Extra quote token sent to each destination wallet, when the project has a non-SOL quote asset. |
| **Quote Jitter (%)**         | Adds randomness around the quote-token top-up amount.                                          |

### Buy/Sell

| Setting                      | Description                                                                                    |
| ---------------------------- | ---------------------------------------------------------------------------------------------- |
| **Source Wallet Group**      | Wallets that will sell project tokens first.                                                   |
| **Destination Wallet Group** | Wallets that will buy project tokens back.                                                     |
| **Source Balance Used (%)**  | Percentage of tokens to sell from each source wallet.                                          |
| **Spread (%)**               | Adds randomness around each wallet's allocation for varied trade sizes.                        |
| **Safety Buffer (%)**        | Keeps a portion of sell proceeds aside to account for slippage, taxes, and fees.               |
| **Delay (seconds)**          | Pause after each completed destination leg.                                                    |
| **SOL Per Wallet**           | Extra SOL sent to each destination wallet after its buy completes.                             |
| **SOL Jitter (%)**           | Adds randomness around the SOL top-up amount.                                                  |
| **Quote Per Wallet**         | Extra quote token sent to each destination wallet, when the project has a non-SOL quote asset. |
| **Quote Jitter (%)**         | Adds randomness around the quote-token top-up amount.                                          |

### EVM

EVM cleanups share the wallet, spread, delay, and native-funding settings:

| Setting                      | Description                                                                                                                                                                                               |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Source Wallet Group**      | Wallets that will send project tokens.                                                                                                                                                                    |
| **Destination Wallet Group** | Wallets that will receive project tokens.                                                                                                                                                                 |
| **Spread (%)**               | Adds randomness around each destination wallet's token transfer split.                                                                                                                                    |
| **Delay (seconds)**          | Pause after each completed transfer batch or sell-buy pair.                                                                                                                                               |
| **Native Funding**           | **Sweep Balance** forwards each source wallet's spare native balance; **Fixed Amount** sends a set native amount per destination wallet. Buy/Sell defaults to a fixed 0.01 native amount with 20% jitter. |
| **Native Per Wallet**        | Native amount per destination wallet in Fixed Amount mode.                                                                                                                                                |
| **Native Jitter (%)**        | Adds randomness around the native funding amount.                                                                                                                                                         |

Solana Buy/Sell defaults its **Safety Buffer** to 0%.

EVM Buy/Sell also exposes **Source Balance Used** (default 100%) and **Buy Margin** (default 0%). It requires a direct Uniswap V2, V3, or V4 project with a wrapped-native quote pool. Sell and buy swaps use the chain's private-relay execution path when supported and fall back to the standard executor path on chains without private-relay support.

EVM cleanups support up to 500 source wallets and 1,000 destination wallets, with up to 100 destinations per source transfer batch. Results appear in Treasury Logs under the **Token Cleanup** filter, including partial confirmations.

## Preview

The preview shows the cleanup plan before execution:

* Source and destination wallet counts
* Total planned token amount
* Redistribution mode
* Largest sell and buy legs, for Buy/Sell mode
* Spread, safety buffer where applicable, top-ups, and delay
* Number of source wallets skipped because they cannot be included in the plan

## How It Works

In Token Transfer mode:

1. Source wallets send project tokens directly to destination wallets
2. Sumo applies the spread setting when planning destination splits
3. Optional SOL or quote-token top-ups are sent to destination wallets
4. The net result is your token exposure rebalanced across a new wallet group without DEX trades

In Buy/Sell mode:

1. Source wallets sell a portion of their tokens on the DEX
2. On EVM, Universal Router sends native sell proceeds and the configured top-up directly to the destination in the sell transaction
3. The confirmed sell receipt is parsed and a fresh destination buy is quoted
4. Destination wallets sign and submit the token buy through the same pool
5. On Solana, optional SOL or quote-token top-ups are included in the atomic migration transaction
6. The net result is your token exposure rebalanced across a new wallet group through market trades

The spread and delay settings help distribute the trades over time and vary the sizes.

- [Swap Wallets](/treasury/swap-wallets): Rotate to entirely new wallet addresses.

- [Withdraw](/treasury/withdraw): Withdraw funds to external addresses.


---

# Burn

> Permanently remove project tokens or LP tokens from a treasury wallet.

- URL: https://docs.sumo.trade/treasury/burn
- Markdown: https://docs.sumo.trade/treasury/burn.md
- Docs index: https://docs.sumo.trade/llms.txt

Burning permanently removes tokens from circulation. Sumo exposes two burn actions from the profile's **Wallets** tab, in the wallet actions menu.

> **Burns are irreversible**
>
> Burned tokens cannot be recovered. Preview amounts carefully before confirming.

## Burn Tokens

Removes the project token from one treasury wallet.

![Burn Tokens dialog](/images/burn-tokens.png)

1. Open the profile's **Wallets** tab and click **Burn Tokens** from the wallet actions menu
2. Select the **source wallet**
3. Enter the **tokens to burn** — the dialog shows the wallet's available balance and the supply percentage
4. On EVM profiles, choose the **burn method**
5. Confirm

| Method (EVM)                 | Description                                                                                                                                                                       |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Contract burn**            | Burns through the token's built-in burn function, reducing supply directly. If the contract does not support burning, Sumo falls back to the dead-address transfer automatically. |
| **Transfer to dead address** | Always sends the tokens to the dead address, removing them from circulation without a contract-level burn.                                                                        |

The method choice only exists on EVM because not every ERC-20 implements a burn function. Solana tokens always support burning, so no choice is needed there.

## Burn Liquidity

Sends LP tokens from one treasury wallet to the dead address, permanently locking the underlying liquidity in the pool. Available on EVM profiles whose pool uses V2-style LP tokens.

![Burn Liquidity dialog](/images/burn-liquidity.png)

1. Open the profile's **Wallets** tab and click **Burn Liquidity** from the wallet actions menu
2. Select the wallet holding the LP tokens — active or archived
3. Enter the LP token amount to burn
4. Confirm

Burning LP tokens is a common post-launch commitment signal: the pool's liquidity can no longer be withdrawn by the team.

## Logs

Both burn types are recorded in [Treasury Logs](/reporting/treasury-logs) with the transaction details.

- [Treasury Logs](/reporting/treasury-logs): Review burn transactions and outcomes.

- [Token Cleanup](/treasury/token-cleanup): Redistribute tokens instead of destroying them.


---

# Wrap / Unwrap

> Convert between native and wrapped assets in your wallets.

- URL: https://docs.sumo.trade/treasury/wrap-unwrap
- Markdown: https://docs.sumo.trade/treasury/wrap-unwrap.md
- Docs index: https://docs.sumo.trade/llms.txt

![Wrap / Unwrap modal](/images/wrap-unwrap.png)

Wrap / Unwrap lets you convert between a chain's native asset and its wrapped version across wallet batches. For example, SOL to WSOL on Solana, or ETH to WETH on Ethereum.

Use it when a profile needs wrapped native liquidity for swaps, or when wrapped balances need to be returned to the native asset before another treasury action. The action appears when the profile trades with the wrapped asset instead of the native asset.

## Supported Assets

| Chain               | Native | Wrapped |
| ------------------- | ------ | ------- |
| **Solana**          | SOL    | WSOL    |
| **Ethereum**        | ETH    | WETH    |
| **BNB Smart Chain** | BNB    | WBNB    |
| **Base**            | ETH    | WETH    |
| **Robinhood Chain** | ETH    | WETH    |
| **Stable**          | USDT0  | WgUSDT  |
| **Tron**            | TRX    | WTRX    |

On Stable, wrap/unwrap converts between the chain's USDT0 gas asset and **WgUSDT** (wrapped gUSDT), the wrapped-gas token used by DYORSwap V2 pools. It is available for profiles trading a WgUSDT-quoted DYORSwap pool.

## Wrap

Convert the native asset into its wrapped version in your wallets.

### Wrap Modes

| Mode                      | Description                                                                                                                                     |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Balance minus reserve** | Wraps each wallet's spare native balance after keeping the reserve amount for gas. Wallets without enough extra balance are skipped in preview. |
| **Variable per wallet**   | Specify exact native amounts for individual wallets.                                                                                            |

### How to Wrap

1. Open the profile's **Wallets** tab
2. Click **Wrap / Unwrap** from the wallet actions menu
3. Select the **Wrap** tab
4. Choose the **source** — all wallets, a wallet group, selected wallets, or one wallet
5. Select a wrap mode:
   * **Balance minus reserve** — Enter the amount to keep in each wallet for gas
   * **Variable per wallet** — Enter exact amounts per wallet
6. Click **Continue** to review the plan
7. Click **Wrap** to execute

## Unwrap

Convert the wrapped asset back to native.

### Unwrap Modes

| Mode                    | Description                                                  |
| ----------------------- | ------------------------------------------------------------ |
| **Unwrap all**          | Unwraps each selected wallet's full wrapped-native balance.  |
| **Variable per wallet** | Specify exact wrapped-native amounts for individual wallets. |

### How to Unwrap

1. Open the profile's **Wallets** tab
2. Click **Wrap / Unwrap** from the wallet actions menu
3. Select the **Unwrap** tab
4. Choose the source
5. Select **Unwrap all** or **Variable per wallet**
6. Click **Continue** to review the plan
7. Click **Unwrap** to execute

## Variable Amount Input

For variable mode, you can enter amounts in two ways:

* **Interactive** — Select wallets from a dropdown and enter amounts one by one
* **CSV** — Paste in format: `walletAddress,amount`

The wallet address must belong to the selected source. Sumo also accepts the internal wallet ID, but wallet address is the normal format to use.

## Preview

The preview shows how many wallets will be included, the total amount planned, skipped wallets, and per-wallet before/after balances. Review skipped wallets before confirming, especially when using Balance minus reserve.

- [Treasury Dashboard](/treasury/treasury-dashboard): View your overall treasury balances.

- [Withdraw](/treasury/withdraw): Withdraw funds from your wallets.


---

# Live Trading

> Monitor trades in real-time as they happen on-chain.

- URL: https://docs.sumo.trade/reporting/live-trading
- Markdown: https://docs.sumo.trade/reporting/live-trading.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Sumo Live Trading Workspace**
>
> A tour of the real-time chart, trade feed, strategy controls, manual trades, wallet surveillance, and operating metrics.
>
> https://www.youtube.com/watch?v=kLcZ_Dpu9c8

![Live Trading workspace with chart, trade feed, filters, and instant trade controls](/images/live-trading.png)

The Live Trading page is the main operating workspace for an active profile. It combines the live chart, streamed pool trades, strategy and wallet tabs, Insights views, and manual trade controls in one screen.

## Chart

The chart shows live price or market-cap movement for the profile's pool. Use the interval controls to switch candle size, toggle volume and Sumo trade markers, and switch between market-cap and price display. The drawing toolbar supports annotations such as trend lines, rays, paths, circles, and freehand marks.

The header above the chart shows current market and treasury metrics, including market cap, token supply held by profile wallets, native treasury balance, and quote treasury balance.

### Drawing Tools

Use the drawing toolbar to mark up the chart while monitoring live flow:

|                             Icon                            | Action              | Use                                                                   |
| :---------------------------------------------------------: | ------------------- | --------------------------------------------------------------------- |
|      ![Select drawings](/images/chart-tools/select.svg)     | **Select**          | Select, move, style, or delete existing drawings                      |
|      ![Trend line](/images/chart-tools/trend-line.svg)      | **Trend Line**      | Mark support, resistance, or trend between two points                 |
|             ![Ray](/images/chart-tools/ray.svg)             | **Ray**             | Project a line forward from an anchored point                         |
|   ![Extended line](/images/chart-tools/extended-line.svg)   | **Extended Line**   | Extend a trend line in both directions                                |
|  ![Horizontal ray](/images/chart-tools/horizontal-ray.svg)  | **Horizontal Ray**  | Mark a price or market-cap level from a point forward                 |
| ![Horizontal line](/images/chart-tools/horizontal-line.svg) | **Horizontal Line** | Mark a persistent price or market-cap level                           |
| ![Fib retracement](/images/chart-tools/fib-retracement.svg) | **Fib Retracement** | Draw Fibonacci retracement levels between a swing start and end point |
|   ![Vertical line](/images/chart-tools/vertical-line.svg)   | **Vertical Line**   | Mark a point in time across the full chart height                     |
|      ![Cross line](/images/chart-tools/cross-line.svg)      | **Cross Line**      | Mark a time and level crosshair at a single point                     |
|            ![Path](/images/chart-tools/path.svg)            | **Path**            | Sketch multi-point moves or scenarios                                 |
|           ![Brush](/images/chart-tools/brush.svg)           | **Brush**           | Add freehand annotations                                              |
|     ![Highlighter](/images/chart-tools/highlighter.svg)     | **Highlighter**     | Add broader freehand emphasis                                         |
|          ![Circle](/images/chart-tools/circle.svg)          | **Circle**          | Highlight a specific chart area                                       |

Drawings are saved in your browser for the current profile, chart interval, and price/market-cap mode. Refreshing the page or returning to the same chart restores them. Changing the chart context, such as switching interval or price/market-cap mode, uses a separate drawing set so annotations do not carry onto a different chart view.

The toolbar also supports:

* **Undo / Redo** — Use the toolbar buttons, `Cmd/Ctrl+Z`, `Cmd/Ctrl+Shift+Z`, or `Cmd/Ctrl+Y`
* **Escape** — Finish or deselect the active drawing tool
* **Delete / Backspace** — Delete the selected drawing
* **Right click or click outside the chart** — Finish or deselect the active drawing tool
* **Clear drawings** — Remove all drawings from the current chart view

### Chart Footer Integrations

The footer strip under the chart links out to holder-analysis views without leaving the workspace:

* **Bubblemaps** — Opens the token's holder map. See [Bubblemaps Analysis](/reporting/bubblemaps-analysis).
* **InsightX** — Opens the token in InsightX Atlas Live, an embedded holder and cluster analysis view. Available on Solana, Ethereum, BNB Chain, Base, Robinhood Chain, and Tron.
* **Holders** — Opens Sumo's holder analysis for the token.
* **TA** — Opens the technical analysis view.

### Project Notes

Use **Project notes** to pin operating notes to the chart while you monitor price action. Notes can be tied to the current chart context, such as interval and price/market-cap mode, so a team can record why a level, event, or market condition mattered at the time.

Project notes are useful for:

* Marking support, resistance, or intervention levels
* Recording launch, migration, or liquidity events
* Leaving handoff notes for another trader or market maker
* Keeping founder-facing commentary beside the trading view

Team notes appear with the profile's other live-trading context, so operators can review market decisions without searching through chat history.

## Workspace Tabs

The tabs below the chart keep the profile workflow in one place:

* **Trading** — Live trade feed and manual trade controls
* **Strategies** — Counter Trade, DCA, Limit Order, Grid, and other profile strategies
* **Insights** — Trading pulse, strategy breakdown, and execution health
* **Wallets** — Profile wallet balances and treasury actions
* **Surveillance** — Wallet tracking and activity monitoring

## Trade Feed

The trade feed streams recent and live swaps on your token's pool. New rows continue arriving while filters are active, so chart updates and side-panel metrics keep moving even when the table is focused on a smaller subset.

| Column     | Description                                                                    |
| ---------- | ------------------------------------------------------------------------------ |
| **Date**   | Relative timestamp (e.g. "11s ago", "3m ago")                                  |
| **Type**   | Buy (green) or Sell (red) badge                                                |
| **USD**    | Dollar value of the trade                                                      |
| **Quote**  | Amount of quote asset traded                                                   |
| **Token**  | Amount of your token traded                                                    |
| **Maker**  | Trader wallet. Click the filter icon beside it to load trades from that maker. |
| **TXN**    | Link to the transaction on the block explorer                                  |
| **Tags**   | Signals and attribution icons for the trade                                    |
| **Source** | Whether the trade is Organic or Sumo                                           |

## Trade Filters

Use the filter menu to narrow the table:

* **All** — Every trade on the pool
* **Organic** — Trades from external market participants
* **Sumo** — Trades executed by your strategies
* **Signals** — MEV, arbitrage, new holders, full exits, strategy types, holder size, and known trading platforms

The signal filter supports **OR** and **AND** matching, so you can either broaden the view or require multiple conditions at once.

## Tags

Tags give each trade extra context at a glance.

|                          Icon                          | Tag                  | Meaning                                                                                                                                   |
| :----------------------------------------------------: | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
|     ![Arbitrage](/images/trade-tags/arbitrage.svg)     | **Arbitrage**        | The trade appears to be part of an arbitrage path. If the contract is unknown, the icon links to the contract address.                    |
|     ![MEV actor](/images/trade-tags/mev-actor.svg)     | **MEV Actor**        | The trade is classified as the acting side of a sandwich-style MEV pattern.                                                               |
|    ![MEV victim](/images/trade-tags/mev-victim.svg)    | **MEV Victim**       | The trade is classified as the affected trade inside a sandwich-style MEV pattern.                                                        |
|    ![New holder](/images/trade-tags/new-holder.svg)    | **New Holder**       | The maker had no token balance before the buy and holds tokens after it.                                                                  |
|     ![Full exit](/images/trade-tags/full-exit.svg)     | **Full Exit**        | The maker sold down to a zero or negligible token balance.                                                                                |
| ![Counter Trade](/images/trade-tags/counter-trade.svg) | **Counter Trade**    | Trade executed by a Counter Trade strategy.                                                                                               |
|           ![DCA](/images/trade-tags/dca.svg)           | **DCA**              | Trade executed by a DCA strategy.                                                                                                         |
|   ![Limit Order](/images/trade-tags/limit-order.svg)   | **Limit Order**      | Trade executed by a Limit Order strategy.                                                                                                 |
| ![Instant Trade](/images/trade-tags/instant-trade.svg) | **Instant Trade**    | Manual buy or sell executed from Sumo.                                                                                                    |
|      ![Whale holder](/images/trade-tags/whale.svg)     | **Whale**            | Maker balance is at least 1% of supply.                                                                                                   |
|    ![Dolphin holder](/images/trade-tags/dolphin.svg)   | **Dolphin**          | Maker balance is at least 0.1% of supply.                                                                                                 |
|       ![Fish holder](/images/trade-tags/fish.svg)      | **Fish**             | Maker balance is at least 0.01% of supply.                                                                                                |
|     ![Shrimp holder](/images/trade-tags/shrimp.svg)    | **Shrimp**           | Maker holds a smaller tracked balance.                                                                                                    |
|   ![Trading platform](/images/trade-tags/jupiter.svg)  | **Trading platform** | Known router, aggregator, DEX, or bot source. Examples include Jupiter, Raydium, Pump.fun, GMGN, Photon, OKX, 1inch, Uniswap, and others. |

The **Source** column is separate from Tags:

|                       Icon                       | Source      | Meaning                                             |
| :----------------------------------------------: | ----------- | --------------------------------------------------- |
| ![Organic trade](/images/trade-tags/organic.svg) | **Organic** | External market trade not attributed to Sumo.       |
|    ![Sumo trade](/images/trade-tags/sumo.svg)    | **Sumo**    | Trade attributed to a Sumo wallet or Sumo strategy. |

## Side Panel

The right panel keeps the live operating numbers visible while you watch the chart and feed.

### Volume

The **Volume** card can be switched between **5m**, **1h**, **6h**, and **24h** windows. It shows:

| Metric      | Description                                                             |
| ----------- | ----------------------------------------------------------------------- |
| **Txns**    | Total buys and sells, with a green/red split bar for buy vs. sell count |
| **Volume**  | Total traded USD volume, with buy volume and sell volume split out      |
| **Traders** | Unique trader activity, with maker and taker counts shown side by side  |

### Trading Stats

The **Trading Stats** card summarizes Sumo-attributed trading performance:

| Metric           | Description                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------ |
| **Total Bought** | Total quote value bought by Sumo trades, with USD value when pricing is available                |
| **Total Sold**   | Total quote value sold by Sumo trades, with USD value when pricing is available                  |
| **PnL**          | Net Sumo trading PnL in quote terms and USD terms. Click the row to open the shareable PnL card. |

### Manual Trading

Below the metrics, the panel contains manual execution controls:

* **Quick Buy / Quick Sell** presets for fast manual intervention
* **Custom Trade** for exact one-off buy or sell orders
* **Swap** button for the full trade modal, including Treasury Swap

When a profile trades against a stablecoin or custom quote token and its active wallets hold the native asset but none of the quote, a notice appears above Quick Buy: buys spend the quote, so nothing can execute yet. Its **Convert** button switches the Custom Trade panel to **Convert** mode with the native-to-quote pair already selected. The notice clears on its own once any quote balance arrives, and the × hides it until the page is next loaded. [AutoFix](/getting-started/profile-settings#autofix) offers the same conversion as a per-wallet fix for buy wallets assigned to active strategies.

## Instant Trade

See [Instant Trade](/strategies/instant-trade) for details on quick presets, custom trades, and treasury swaps.

- [Insights](/reporting): View trade volume summaries and performance analytics.

- [Trade Logs](/reporting/trade-logs): Browse the full history of executed trades.


---

# Surveillance

> Monitor tracked wallets, token movements, and surveillance event logs.

- URL: https://docs.sumo.trade/reporting/surveillance
- Markdown: https://docs.sumo.trade/reporting/surveillance.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Surveillance Deep Dive**
>
> A walkthrough of tracked wallets, linked-wallet discovery, event logs, filters, and surveillance workflows.
>
> https://www.youtube.com/watch?v=5cna696-Wdk

![Surveillance table with tracked wallet groups, balances, linked wallets, and deltas](/images/wallet-tracking.png)

Surveillance monitors external project-related wallets such as founder, partner, or community wallets. It tracks token balances, follows token outflows into newly discovered wallets, and records the movements that matter for your profile.

## Surveillance Tab

The **Surveillance** tab shows the live tracking state for every configured wallet group:

| Column                   | Description                                                                          |
| ------------------------ | ------------------------------------------------------------------------------------ |
| **Group**                | The wallet group being monitored, such as founders, partners, or market participants |
| **Label**                | Optional label for the specific tracked wallet                                       |
| **Wallet**               | Truncated wallet address with copy button                                            |
| **Snapshot**             | Baseline snapshot time for the tracked wallet                                        |
| **Original**             | Token balance when tracking began (baseline)                                         |
| **Current**              | Live token balance                                                                   |
| **Counter Asset Amount** | Current value in the profile's counter asset when available                          |
| **Linked Wallets**       | Number of child wallets discovered via outflow follows                               |
| **Delta**                | Change from original balance (negative = tokens left the wallet)                     |

The total row summarizes the original balance, current balance, and net delta across all tracked wallets.

### Tracking Toggle

The **Tracking On/Off** toggle enables or disables surveillance for the profile. When enabled, Sumo refreshes balances and activity automatically.

### Reconcile

Click **Reconcile** to manually trigger a balance refresh and replay recent wallet activity. Use this when you want an immediate update without waiting for the next automatic refresh.

### Edit

Click **Edit** to add, remove, or rename tracked wallet groups and root wallet addresses. Changes take effect on the next poll or reconcile.

### CSV Export

The Wallet Tracking tab has its own **CSV** button that downloads the tracking table - group, label, wallet, snapshot, original and current balances, counter-asset gained, linked wallet count, and delta - using your browser's timezone for timestamps. This is separate from the Event Logs CSV export below.

## Event Logs Tab

![Surveillance Event Logs table with event types, wallet groups, token amounts, and transaction links](/images/surveillance-event-logs.png)

The **Event Logs** tab shows a chronological history of detected surveillance events:

| Column                   | Description                                                                                |
| ------------------------ | ------------------------------------------------------------------------------------------ |
| **Date**                 | When the event was detected                                                                |
| **Event**                | Type of movement, such as Inflow, Outflow, Buy, Sell, Internal, Sold Out, or Outflowed Out |
| **Group**                | Wallet group associated with the event                                                     |
| **Label**                | Optional wallet label                                                                      |
| **Wallet**               | Wallet address involved in the event                                                       |
| **Tokens**               | Number of tokens moved                                                                     |
| **Counter Asset Amount** | Counter asset value when available                                                         |
| **Tx**                   | Link to the transaction on the block explorer                                              |

### Event Types

| Event             | Meaning                                                               |
| ----------------- | --------------------------------------------------------------------- |
| **Inflow**        | Tokens received from an external wallet                               |
| **Outflow**       | Tokens sent to another wallet (which is then auto-followed)           |
| **Internal**      | Movement between wallets that are already part of the tracked tree    |
| **Buy**           | Tokens purchased via a DEX (detected by contract/program interaction) |
| **Sell**          | Tokens sold via a DEX                                                 |
| **Outflowed Out** | Wallet fully emptied via outflow — tracking stops for that wallet     |
| **Sold Out**      | Wallet fully emptied via sell — tracking stops for that wallet        |

### Filtering & Sorting

* **Event type filter** — Filter by specific event types (All, Inflow, Outflow, Buy, Sell, etc.)
* **Search** — Search by transaction signature
* **Sort** — Toggle between Recent (newest first) and Oldest (oldest first)

### CSV Export

Click the **CSV** button to download your event logs as a CSV file for external analysis or record keeping.

## How Tracking Works

1. **Add root wallets** — Configure wallet groups with one or more root addresses to watch
2. **Automatic follow** — When a tracked wallet sends tokens to a new address, that address is automatically added to the tracking tree
3. **Custodial detection** — Known exchange and custodial addresses are detected and excluded from follow chains to avoid noise
4. **Terminal states** — Wallets that fully sell or outflow their tokens are marked as Sold Out or Outflowed Out and stop being actively tracked

## Supported Chains

| Chain               | Network |
| ------------------- | ------- |
| **Solana**          | Mainnet |
| **Ethereum**        | Mainnet |
| **Base**            | Mainnet |
| **BNB Chain**       | Mainnet |
| **Stable**          | Mainnet |
| **Robinhood Chain** | Mainnet |

Wallet tracking is not available for Tron profiles.

## Notifications

Surveillance events, except internal movements, generate in-app notifications and best-effort Telegram alerts to linked project groups. See [Profile Notifications](/reporting/profile-notifications) for notification settings.

## Telegram Commands

In a linked Telegram group, `/surveillance` sends a rendered overview image with total wallets tracked, total counter-asset gained, net supply sold, and the top tracked wallets ranked by supply sold. Use `/surveillance details` for the full per-wallet table. See [Telegram Bot](/integrations/telegram-bot) for setup.

- [Live Trading](/reporting/live-trading): Monitor trades in real-time as they happen on-chain.

- [Trade Logs](/reporting/trade-logs): Browse the full history of executed trades.


---

# Insights

> Trading pulse, strategy breakdowns, and execution health analytics.

- URL: https://docs.sumo.trade/reporting
- Markdown: https://docs.sumo.trade/reporting.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Insights Deep Dive**
>
> A walkthrough of Trading Pulse, Strategy Breakdown, Execution Health, and profile performance analytics.
>
> https://www.youtube.com/watch?v=nVVYcvVYv9M

![Insights tab with Trading Pulse, Strategy Breakdown, and time range controls](/images/reporting.png)

The **Insights** tab gives you a performance view for the active profile. Use it to understand buy/sell flow, net position change, strategy contribution, withdrawals, Sumo trading fees, and execution quality without leaving the live trading workspace.

Access it from the profile workspace by opening **Live Trading** and selecting **Insights** below the chart.

## Time Range

Filter all metrics by time range using the buttons in the top right:

* **24H** — Last 24 hours
* **7D** — Last 7 days
* **30D** — Last 30 days
* **ALL** — All time

Use the section selector beside the range controls to switch between **Trading Pulse**, **Strategy Breakdown**, and **Execution Health**.

## Trading Pulse

**Trading Pulse** summarizes profile-level trading activity for the selected period:

| Metric                 | Description                                                 |
| ---------------------- | ----------------------------------------------------------- |
| **Buy Volume**         | Total buy volume in quote asset, USD, and tokens            |
| **Sell Volume**        | Total sell volume in quote asset, USD, and tokens           |
| **Net Change**         | Net position change (buys minus sells)                      |
| **Withdraw**           | Total withdrawn in native asset and token mints             |
| **Avg Buy MCap**       | Average market cap at which buys were executed              |
| **Avg Sell MCap**      | Average market cap at which sells were executed             |
| **Avg Trading Spread** | Percentage spread between average buy and sell prices       |
| **Sumo Trade Fees**    | 1% platform fees attributed to Sumo-executed trading volume |

The chart visualizes buy volume, sell volume, and net change over time with interactive hover tooltips.

## Strategy Breakdown

**Strategy Breakdown** groups performance by strategy type, such as Counter Trade, DCA, Limit Order, and Instant Trade. Each card shows buy volume, sell volume, net change, average buy/sell market cap, spread, trade counts, and the buy/sell split.

## Execution Health

**Execution Health** monitors order reliability and latency:

| Metric                    | Description                                                               |
| ------------------------- | ------------------------------------------------------------------------- |
| **Total Orders**          | Number of orders submitted                                                |
| **Confirmed**             | Successfully landed on-chain                                              |
| **Failed**                | Orders that failed                                                        |
| **Success Rate**          | Percentage of confirmed orders                                            |
| **Submit-Landed P50/P95** | Latency from submit to on-chain confirmation (median and 95th percentile) |
| **Create-Landed P50/P95** | Latency from order creation to confirmation                               |
| **Retry Rate**            | Percentage of orders that required retries                                |
| **Avg Attempts**          | Average retry count per order                                             |

A failure breakdown shows the most common failure reasons so you can quickly separate market conditions from configuration or execution issues.

- [Trade Logs](/reporting/trade-logs): Browse the detailed history of every trade.

- [Live Trading](/reporting/live-trading): Watch trades happen in real time.


---

# Bubblemaps Analysis

> Inspect token-holder clusters, Magic Nodes, Time Nodes, and matching Sumo wallet groups.

- URL: https://docs.sumo.trade/reporting/bubblemaps-analysis
- Markdown: https://docs.sumo.trade/reporting/bubblemaps-analysis.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo includes two Bubblemaps workflows for token-holder review: a quick map view from the live chart and a saved wallet analysis from the Wallets tab. Bubblemaps is available for profiles on Solana, Ethereum, BNB Chain, Base, Robinhood Chain, and Tron.

> **Video: Bubblemaps Analysis on Sumo**
>
> A walkthrough of opening Bubblemaps from the trading workspace and running saved wallet analyses from Sumo.
>
> https://www.youtube.com/watch?v=R5kVEgM9AG0

## Bubblemaps From the Chart

Click **Bubblemaps** in the bottom-left of the live trading chart to open the token's Bubblemaps view without leaving the profile workspace.

![Bubblemaps token holder map opened from the live trading chart](/images/bubblemaps-live-map.png)

Use this view when you want to quickly inspect holder distribution while watching flow. Bubblemaps represents token holders as bubbles: larger bubbles hold more supply, and links between bubbles show on-chain transfers between holders. Connected bubbles form clusters, which can reveal groups of related wallets, coordinated holders, or concentration patterns that deserve a closer look.

Bubblemaps can also surface indirect relationships. **Magic Nodes** add non-holder intermediary addresses when they connect top holders that would otherwise look unrelated. **Time Nodes** highlight wallets that interacted through common venues, such as exchanges or bridges, within similar time windows. For launch monitoring, these views can help you spot related snipers, coordinated wallets, or hidden distribution patterns faster than scanning addresses one by one.

## Wallets Tab Analysis

The Wallets tab has a **Bubblemaps analysis** action in the overflow menu. This runs Sumo's saved analysis for the current project token.

![Bubblemaps Analysis modal with node count, wallet group options, and refresh toggle](/images/bubblemaps-analysis-modal.png)

The analysis can:

* Fetch the latest token-holder map summary for the project token
* Choose how many top nodes to inspect: **80**, **250**, or **500**
* Optionally refresh Bubblemaps data instead of using the current cached map
* Save the latest summary for the project, replacing the prior saved analysis
* Create cluster wallet groups named with your prefix, such as **BM Cluster #1**, **BM Cluster #2**, and so on
* Create fixed **BM Magic Nodes** and **BM Time Nodes** wallet groups

Wallet groups are only created or updated when at least one address in the Bubblemaps result matches a Sumo wallet in the current profile. External holders still appear in the Bubblemaps result, but Sumo does not create wallet-group memberships for addresses you do not manage.

## Saved Results

The saved results panel shows the latest analysis metrics:

| Metric                    | Meaning                                                                 |
| ------------------------- | ----------------------------------------------------------------------- |
| **Total Cluster**         | Combined supply share held by all detected clusters                     |
| **Biggest Cluster**       | Supply share held by the largest detected cluster                       |
| **Magic Nodes**           | Count of matching Sumo wallets found in Bubblemaps Magic Nodes          |
| **Time Nodes**            | Count of matching Sumo wallets found in Bubblemaps Time Nodes           |
| **Top 10**                | Adjusted top-holder concentration                                       |
| **Fresh Wallets**         | Supply share held by newly active wallets                               |
| **Contracts / DEX / CEX** | Supply share associated with contracts, DEXs, and centralized exchanges |
| **Bubblemaps Score**      | Bubblemaps' decentralization score for the token                        |

For Bubblemaps terminology, see the Bubblemaps docs on [how bubble maps work](https://wiki.bubblemaps.io/bubblemaps-v2/how-does-it-work), [Magic Nodes](https://wiki.bubblemaps.io/bubblemaps-v2/magic-nodes), and [Time Nodes](https://wiki.bubblemaps.io/bubblemaps-v2/time-nodes).

- [Insights](/reporting): Review trading pulse, strategy breakdown, and execution health.

- [Live Trading](/reporting/live-trading): Open the workspace where the Bubblemaps chart button appears.


---

# Profile Notifications

> Real-time alerts for important profile events.

- URL: https://docs.sumo.trade/reporting/profile-notifications
- Markdown: https://docs.sumo.trade/reporting/profile-notifications.md
- Docs index: https://docs.sumo.trade/llms.txt

![Notifications panel showing withdrawal completions and wallet events](/images/notifications.png)

Profile Notifications keep you informed about important events like completed withdrawals, failed transactions, and wallet status changes. Access them by clicking the **bell icon** in the profile header.

## Notification Types

Notifications cover key events across your profile:

* **Withdraw completed** — A withdrawal operation finished with confirmation count
* **Privacy Swap completed** — Privacy swap completed with amount and destination count
* **Wallet archived** — A wallet was automatically archived (e.g. after consecutive failures)
* **Strategy events** — Strategy-related alerts like failures or completions
* **Launch events** — Token launch confirmations and failures

## Notification Levels

Each notification has a severity level with a visual indicator:

| Level       | Description                                    |
| ----------- | ---------------------------------------------- |
| **Success** | Operation completed successfully (green badge) |
| **Info**    | Informational event (blue badge)               |
| **Warning** | Something needs attention (yellow badge)       |
| **Error**   | An operation failed (red badge)                |

## Managing Notifications

* **Unread count** — The bell icon shows a badge with the number of unread notifications
* **Mark all as read** — Click **Read all** to dismiss all unread notifications
* **Real-time updates** — New notifications stream in automatically, with a sound alert
* **Scroll to load more** — Older notifications load as you scroll down

- [Live Trading](/reporting/live-trading): Monitor trades in real time.

- [Audit Logs](/reporting/audit-logs): Full audit trail of all operations.


---

# Trade Logs

> Detailed log of strategy and manual trades executed by Sumo.

- URL: https://docs.sumo.trade/reporting/trade-logs
- Markdown: https://docs.sumo.trade/reporting/trade-logs.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Managing Trade, Treasury, and Audit Logs**
>
> A walkthrough of the Logs workspace, including trade history, treasury operations, audit events, filtering, and exports.
>
> https://www.youtube.com/watch?v=vrDyM1Xa_8o

![Trade Logs page with log tabs, strategy filter, wallet column, statuses, and transaction links](/images/trade-logs.png)

Trade Logs provide a complete history of Sumo-executed trades for a profile, including strategy trades and manual Instant Trade activity. Access them from the profile **Logs** view and select the **Trade Logs** tab.

The same Logs workspace also includes **Treasury Logs**, **Launch Logs** when available, and **Audit Logs**.

## Columns

| Column         | Description                                                                                                    |
| -------------- | -------------------------------------------------------------------------------------------------------------- |
| **Date**       | When the trade was executed                                                                                    |
| **Side**       | Buy or Sell                                                                                                    |
| **Strategy**   | Which strategy or manual action triggered the trade, such as Counter Trade, DCA, Limit Order, or Instant Trade |
| **Wallet**     | Wallet that executed the trade, with a copy button                                                             |
| **Amount In**  | What was spent (with token symbol)                                                                             |
| **Amount Out** | What was received (with token symbol)                                                                          |
| **Status**     | Success, Failed, Submitted, or the current execution state                                                     |
| **Trigger**    | Link to the external trade that triggered a counter trade (if applicable)                                      |
| **Tx**         | Link to the transaction on the block explorer                                                                  |

## Filtering

* **Strategy filter** — Show all strategies or filter to specific strategy/action types
* **Search** — Search by transaction signature
* **Sort** — Click sortable column headers such as Date, Strategy, Amount In, Amount Out, or Status
* **Order** — Toggle between Recent (newest first) and Oldest (oldest first)
* **Refresh** — Reload the current log view

## CSV Export

Click the **CSV** button to download your trade logs as a CSV file for external analysis or record keeping.

## Pagination

Use the page controls at the bottom to move through older or newer log pages.

- [Treasury Logs](/reporting/treasury-logs): View withdrawal and wallet swap history.

- [Insights](/reporting): See aggregated trade analytics.


---

# Treasury Logs

> Log of all treasury operations including withdrawals and wallet swaps.

- URL: https://docs.sumo.trade/reporting/treasury-logs
- Markdown: https://docs.sumo.trade/reporting/treasury-logs.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Managing Trade, Treasury, and Audit Logs**
>
> A walkthrough of the Logs workspace, including trade history, treasury operations, audit events, filtering, and exports.
>
> https://www.youtube.com/watch?v=vrDyM1Xa_8o

![Treasury Logs page with log tabs, type filter, wallet column, statuses, and transaction links](/images/treasury-logs.png)

Treasury Logs record every treasury operation performed on your profile. Access them from the profile **Logs** view and select the **Treasury Logs** tab.

The same Logs workspace also includes **Trade Logs**, **Launch Logs** when available, and **Audit Logs**.

## Columns

| Column     | Description                                                           |
| ---------- | --------------------------------------------------------------------- |
| **Date**   | When the operation was executed                                       |
| **Wallet** | Wallet involved in the operation, destination count, or summary label |
| **Type**   | The operation type                                                    |
| **Amount** | Amount transferred                                                    |
| **Status** | Success, Failed, Submitted, or the current execution state            |
| **Tx**     | Link to the transaction on the block explorer                         |

## Operation Types

* **Withdraw** — Standard withdrawals to external addresses
* **Privacy Swap** — Private native asset or stablecoin distributions
* **Privacy Cashout** — Multi-source privacy cashout operations with destination-side settlement
* **Treasury Swap** — Native-to-stable or stable-to-native treasury swaps
* **Cross-Chain Swap** — Project wallet swaps to a destination on another chain
* **Swap Wallets** — Wallet replacement transfers
* **Token Cleanup** — Token transfers or buy/sell redistribution between wallet groups
* **Token Burn** — Project-token burns
* **Liquidity Burn** — Liquidity-token burns
* **Wrap/Unwrap Native** — Native asset wrap/unwrap operations
* **Creator Fee Claim** — PumpFun/PumpSwap and Pons V2 creator-fee claims when available
* **Change Creator** — A finalized PumpFun/PumpSwap creator-fee recipient change, including the recipient count and transaction

For cross-chain swaps, the transaction link points to the destination receipt when the provider returns one. The tooltip can include the source deposit transaction so you can reconcile both sides of the bridge route.

## Filtering & Sorting

* **Type filter** — Show only specific operation types
* **Search** — Search by transaction signature
* **Sort** — Click sortable column headers such as Date, Wallet, Type, Amount, or Status
* **Order** — Toggle between Recent (newest first) and Oldest (oldest first)
* **Refresh** — Reload the current log view

## CSV Export

Click the **CSV** button to download treasury logs for external review or reconciliation.

## Pagination

Use the page controls at the bottom to move through older or newer log pages.

- [Trade Logs](/reporting/trade-logs): View your trade execution history.

- [Audit Logs](/reporting/audit-logs): Full audit trail of all actions.


---

# Audit Logs

> Full audit trail of all sensitive operations in your organization.

- URL: https://docs.sumo.trade/reporting/audit-logs
- Markdown: https://docs.sumo.trade/reporting/audit-logs.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Managing Trade, Treasury, and Audit Logs**
>
> A walkthrough of the Logs workspace, including trade history, treasury operations, audit events, filtering, and exports.
>
> https://www.youtube.com/watch?v=vrDyM1Xa_8o

![Audit Logs page with log tabs, action filter, actor column, details column, and sort controls](/images/audit-logs.png)

Audit Logs provide a complete trail of important profile and organization actions. Access them from the profile **Logs** view and select the **Audit Logs** tab.

The same Logs workspace also includes **Trade Logs**, **Treasury Logs**, and **Launch Logs** when available.

## Columns

| Column       | Description                                                             |
| ------------ | ----------------------------------------------------------------------- |
| **Date**     | When the action occurred                                                |
| **Action**   | What was done (e.g. created, updated, deleted)                          |
| **Resource** | What was affected, such as a wallet, strategy, wallet group, or profile |
| **Actor**    | Who performed the action                                                |
| **Details**  | Additional context about the change                                     |

## Filtering & Sorting

* **Action filter** — Show all actions or filter to specific action types
* **Search** — Search by transaction or log text when available
* **Sort** — Click sortable column headers such as Date, Action, Resource, Actor, or Details
* **Order** — Toggle between Recent (newest first) and Oldest (oldest first)
* **Refresh** — Reload the current log view

## CSV Export

Click the **CSV** button to download audit logs for external review.

## Pagination

Use the page controls at the bottom to move through older or newer log pages.

## Use Cases

* **Security review** — Track who made changes and when
* **Troubleshooting** — Understand what changed before an issue occurred
* **Team oversight** — Monitor team member activity across the organization

- [Trade Logs](/reporting/trade-logs): View trade execution history.

- [Profile Notifications](/reporting/profile-notifications): Real-time alerts for profile events.


---

# Supported Chains

> Blockchain networks supported by Sumo.

- URL: https://docs.sumo.trade/integrations/supported-chains
- Markdown: https://docs.sumo.trade/integrations/supported-chains.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo supports Solana and EVM trading profiles. Chain support affects which wallets you can create, which DEXes and aggregators are available, which stablecoins appear in swap flows, and which privacy providers can be used.

## Production Networks

| Network              | Native Asset | Registered Stablecoins | Notes                                                                                                                                                                                                                                 |
| -------------------- | ------------ | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Solana Mainnet**   | SOL          | USDC, USDT, USD1       | Full Solana trading support, Pump.fun launches, Wallet Farm, Surveillance, and privacy workflows                                                                                                                                      |
| **Ethereum Mainnet** | ETH          | USDC, USDT, USD1       | EVM trading profiles, Wallet Farm, treasury actions, and native/stable privacy swaps                                                                                                                                                  |
| **BNB Smart Chain**  | BNB          | USDC, USDT             | EVM trading profiles, Flap, SushiSwap and other direct DEX execution, Wallet Farm, treasury actions, and native/stable privacy swaps                                                                                                  |
| **Base Mainnet**     | ETH          | USDC                   | EVM trading profiles, Wallet Farm, treasury actions, and native/stable privacy swaps                                                                                                                                                  |
| **Robinhood Chain**  | ETH          | USDG                   | EVM trading profiles, Wallet Farm, treasury actions, native ETH privacy workflows through Husher, Flap, Pons V2, PancakeSwap, SushiSwap and Uniswap direct execution, and EVM aggregator execution                                    |
| **Stable Mainnet**   | USDT0        | USDT0, WgUSDT          | Stablecoin-native chain with USDT0 gas. Uniswap and DYORSwap trading, Uniswap V3 launches, airdrops, wallet tracking, treasury actions, and reporting. Direct DEX execution only; privacy funding and private relay are not available |
| **Tron Mainnet**     | TRX          | USDT                   | SunSwap and SunPump trading, Wallet Farm, privacy swaps, wallet rotation, cross-chain swaps, Bubblemaps, and reporting. Direct DEX execution only                                                                                     |

Stablecoins are chain-specific. When a flow supports stable assets, Sumo only shows stablecoins that are registered for the selected profile chain and supported by the selected provider.

## Solana Coverage

Solana has the broadest product coverage in Sumo:

* Pump.fun token launches with automated vanity mining and launch-wallet funding
* Direct DEX trading across PumpSwap, Orca, Raydium, and Meteora pool families
* Aggregator execution through Jupiter, DFlow, and OKX DEX
* Wallet Farm preparation, activity generation, and privacy funding
* Surveillance, trade feed, strategy execution, treasury actions, and reporting

## EVM Coverage

EVM profiles support direct DEX execution, aggregator execution, Wallet Farm workflows, treasury actions, and treasury-swap flows. Available DEXes depend on the selected chain:

* **Ethereum Mainnet** — Uniswap and SushiSwap pool families and EVM aggregators
* **BNB Smart Chain** — Flap, Four.meme, OpenFour, PancakeSwap, SushiSwap, Uniswap, and EVM aggregators
* **Base Mainnet** — Aerodrome, PancakeSwap, SushiSwap, Uniswap, and EVM aggregators
* **Robinhood Chain** — Flap, Pons V2, PancakeSwap, SushiSwap, Uniswap pool families, and EVM aggregators
* **Stable Mainnet** — DYORSwap and Uniswap pool families, direct DEX execution only

## Tron Coverage

Tron profiles trade directly on SunSwap V2 pools and SunPump launch markets with TRX as the native asset and USDT as the settlement stablecoin. Supported workflows include instant trades, strategies, treasury cashouts, privacy swaps, wallet rotation, wrap/unwrap (WTRX), cross-chain swaps, Wallet Farm activity generation, Wallet Marketplace, and Bubblemaps analysis. Wallet tracking, airdrops, and token launches are not available on Tron.

## Test Networks

| Network              | Native Asset | Use            |
| -------------------- | ------------ | -------------- |
| **Solana Devnet**    | SOL          | Solana testing |
| **Ethereum Sepolia** | ETH          | EVM testing    |

Test networks are available in the product for setup and integration testing. Production liquidity, privacy providers, and wallet-funding behavior can differ from test networks.

- [Supported DEXes](/integrations/supported-dexes): See which DEXes are available on each chain.

- [Supported Aggregators](/integrations/supported-aggregators): DEX aggregators for best-price routing.


---

# Supported DEXes

> Decentralized exchanges integrated with Sumo.

- URL: https://docs.sumo.trade/integrations/supported-dexes
- Markdown: https://docs.sumo.trade/integrations/supported-dexes.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo integrates with the following decentralized exchanges for direct pool trading. If you paste a pool address while creating or importing a profile, Sumo attempts to detect the matching DEX and pool family automatically.

## Solana

| DEX                    | Pool Types                       |
| ---------------------- | -------------------------------- |
| **PumpFun / PumpSwap** | Bonding curve, migrated pools    |
| **Orca**               | Whirlpool concentrated liquidity |
| **Raydium**            | AMM v4, CLMM, CPMM, LaunchLab    |
| **Meteora**            | DAMM v1, DAMM v2, DLMM, DBC      |

## Ethereum

| DEX           | Pool Types |
| ------------- | ---------- |
| **Uniswap**   | V2, V3, V4 |
| **SushiSwap** | V2, V3     |

## BNB Smart Chain

| DEX             | Pool Types            |
| --------------- | --------------------- |
| **Uniswap**     | V2, V3, V4            |
| **PancakeSwap** | V2, V3                |
| **SushiSwap**   | V2, V3                |
| **Four.meme**   | Legacy launch markets |
| **OpenFour**    | BSC launch markets    |
| **Flap**        | Bonding-curve markets |

## Base

| DEX             | Pool Types                             |
| --------------- | -------------------------------------- |
| **Uniswap**     | V2, V3, V4                             |
| **PancakeSwap** | V2, V3, Infinity CL                    |
| **Aerodrome**   | Classic, Slipstream, legacy Slipstream |
| **SushiSwap**   | V2, V3                                 |

## Robinhood Chain

| DEX             | Pool Types                                |
| --------------- | ----------------------------------------- |
| **Uniswap**     | V2, V3, V4, Universal Router              |
| **PancakeSwap** | V2, V3                                    |
| **SushiSwap**   | V2, V3                                    |
| **Flap**        | Bonding-curve markets                     |
| **Pons V2**     | Bonding curve, graduated Uniswap V4 pools |

## Stable

| DEX          | Pool Types                   |
| ------------ | ---------------------------- |
| **DYORSwap** | V2, with fee-capable routing |
| **Uniswap**  | V2, Universal Router         |

## Tron

| DEX         | Pool Types                   |
| ----------- | ---------------------------- |
| **SunSwap** | V2                           |
| **SunPump** | Bonding curve launch markets |

## Test Networks

| Network              | DEX                   | Pool Types                          |
| -------------------- | --------------------- | ----------------------------------- |
| **Solana Devnet**    | Solana DEX connectors | Used for Solana integration testing |
| **Ethereum Sepolia** | Uniswap               | V2                                  |

## Choosing a DEX

When creating a profile, select the DEX where your token's primary liquidity pool is hosted. Direct DEX execution is the most predictable setup when you know the exact pool Sumo should watch and trade against.

For tokens with liquidity across multiple DEXes, consider using an [Aggregator](/integrations/supported-aggregators) instead of direct DEX execution for better pricing.

- [Supported Aggregators](/integrations/supported-aggregators): Route trades across multiple pools for best price.

- [Import an Existing Token](/getting-started/import-existing-token): Set up your profile with a DEX and pool.


---

# Supported Aggregators

> DEX aggregators integrated with Sumo for best-price routing.

- URL: https://docs.sumo.trade/integrations/supported-aggregators
- Markdown: https://docs.sumo.trade/integrations/supported-aggregators.md
- Docs index: https://docs.sumo.trade/llms.txt

DEX aggregators route trades across multiple pools and DEXes to find the best available route. In Sumo, aggregators can be selected as the execution provider for trading profiles and activity-generation flows when they are supported on the selected chain.

## Solana Aggregators

| Aggregator  | Notes                                             |
| ----------- | ------------------------------------------------- |
| **Jupiter** | Broad Solana route coverage through Jupiter Metis |
| **DFlow**   | Solana aggregation route option                   |
| **OKX DEX** | Solana aggregation route option                   |

## EVM Aggregators

| Aggregator      | Chains                                                             |
| --------------- | ------------------------------------------------------------------ |
| **0x**          | Ethereum, BNB Smart Chain, Base, Robinhood Chain                   |
| **Uniswap API** | Ethereum, BNB Smart Chain, Base, Robinhood Chain, Ethereum Sepolia |

**Stable Mainnet** and **Tron Mainnet** have no aggregator integrations — profiles on those chains use direct DEX execution.

## Fees

> **Aggregator Fees**
>
> Aggregator routing, price impact, gas, and provider fees are separate from Sumo's platform fee. Sumo's platform fee is charged on Sumo-executed trading volume.

## When to Use an Aggregator

* **Multiple pools** — Your token has liquidity spread across several DEXes or pool types
* **Better pricing** — The aggregator can split your trade across pools for less slippage
* **Price discovery** — Let the aggregator find the best route automatically
* **Activity generation** — Wallet Farm can use supported aggregators when generating swap history

If your token trades on a single known pool, direct [DEX execution](/integrations/supported-dexes) is simpler and keeps routing tied to that pool.

- [Supported DEXes](/integrations/supported-dexes): Direct DEX execution without aggregator fees.

- [Import an Existing Token](/getting-started/import-existing-token): Choose between DEX and Aggregator execution.


---

# Telegram Bot

> Monitor balances, receive alerts, and use Telegram for login verification.

- URL: https://docs.sumo.trade/integrations/telegram-bot
- Markdown: https://docs.sumo.trade/integrations/telegram-bot.md
- Docs index: https://docs.sumo.trade/llms.txt

> **Video: Linking Telegram to Sumo**
>
> A walkthrough of linking the Telegram bot, monitoring profiles, receiving alerts, and enabling Telegram login verification.
>
> https://www.youtube.com/watch?v=0nIaCqMpeGA

![Sumo Telegram bot showing balance update with chart, market cap, liquidity, and holdings](/images/telegram-bot.png)

Sumo's Telegram bot lets you monitor profiles, check balances, receive real-time alerts, and use Telegram as a login verification channel.

## Linking Your Account

1. Go to [Settings](https://app.sumo.trade/settings)
2. In the Telegram section, click **Generate Link**
3. You'll receive a code and deep link — enter the code in the Sumo Telegram bot, or open the deep link directly
4. Once linked, your Telegram username appears in Settings

## Features

### Balance Updates

Get balance summaries with a live price chart showing:

* Current market cap and liquidity
* Supply percentage and USD value of your holdings
* Native asset balance and value
* 1-minute candlestick chart

### Trade Alerts

Receive real-time notifications for:

* Strategy trade executions (buys and sells)
* Instant Trade and Treasury Swap activity
* Withdraw and Privacy Swap completions
* Failed transactions or provider sessions
* Wallet events
* Profile and strategy events

### Group Commands

Telegram groups can be linked to a Sumo profile so the team can check operating data without opening the app. A linked personal Telegram account with trader access or higher must run the setup commands.

| Command                                          | Use                                                                                                  |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| `/link <project-uuid>`                           | Link the current group to a profile.                                                                 |
| `/move_link <project-uuid>`                      | Move an existing project link from another group to the current group.                               |
| `/unlink`                                        | Remove the current group's project link.                                                             |
| `/balance`                                       | Print the linked profile's balances and chart summary.                                               |
| `/volume [all\|organic\|sumo] [24h\|6h\|1h\|5m]` | Show volume for the selected source and window, including total volume, buy volume, and sell volume. |
| `/preferences`                                   | Choose the stablecoin shown in `/balance` and the LP wallet used for eligible claim flows.           |
| `/fees`                                          | Show claimable creator-fee or LP-fee amounts when supported.                                         |
| `/claim`                                         | Submit a creator-fee or LP-fee claim for the linked profile.                                         |
| `/timers`                                        | Schedule recurring group updates for supported commands.                                             |
| `/alerts`                                        | Configure linked-group market alert delivery.                                                        |
| `/subscribe <project-uuid>`                      | Subscribe the current group to trade notifications for a profile.                                    |
| `/unsubscribe`                                   | Remove the current group's trade-notification subscription.                                          |
| `/threshold <usd>`                               | Set the minimum USD trade size for notification messages.                                            |

Channels can also receive trade notifications when the bot has permission to post there. Use `/subscribe_channel @channel <project-uuid>` and `/settings @channel` from a direct message with the bot.

## Two-Factor Authentication

Once your Telegram is linked, you can use it as your 2FA method:

1. Go to [Settings](https://app.sumo.trade/settings)
2. Change the **Two Factor Authentication** dropdown from Email to Telegram
3. Future login challenges will be sent via Telegram instead of email

## Unlinking

To disconnect Telegram, go to [Settings](https://app.sumo.trade/settings) and click **Unlink Telegram**. Your two-factor method will revert to email.

- [Profile Notifications](/reporting/profile-notifications): In-app notification alerts.

- [Other Integrations](/integrations/other-integrations): Additional third-party integrations.


---

# Other Integrations

> Additional third-party integrations for privacy and wallet funding.

- URL: https://docs.sumo.trade/integrations/other-integrations
- Markdown: https://docs.sumo.trade/integrations/other-integrations.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo integrates with third-party privacy providers for privacy-preserving fund movement and Wallet Farm funding.

Privacy providers are used by [Privacy Cashout](/treasury/privacy-cashout) and [Wallet Farm Privacy Funding](/wallet-farm/privacy-funding). They receive a source-side deposit and distribute funds to one or more destination wallets, reducing the direct on-chain link between source and destination.

## Husher

[Husher](https://www.husher.io/) is a non-custodial crypto exchange platform offering instant, private, and secure cryptocurrency swaps. Your keys, your crypto.

**Used in:** [Privacy Cashout](/treasury/privacy-cashout), [Wallet Farm Privacy Funding](/wallet-farm/privacy-funding), and Pump.fun launch wallet funding when CEX funding is enabled.

* Time-staggered delivery for enhanced privacy
* Configurable delay between destination payouts
* Supports splitting a source wallet across multiple destinations
* Supports native assets and selected registered stablecoins depending on chain

## SplitNOW

[SplitNOW](https://splitnow.io/) lets you split your crypto across hundreds of wallets instantly and privately. One deposit, multiple wallets, 100% private.

**Used in:** [Privacy Cashout](/treasury/privacy-cashout) and [Wallet Farm Privacy Funding](/wallet-farm/privacy-funding).

* Instant delivery to destination wallets
* No time delay between payouts
* No account required
* Supports native assets and selected registered stablecoins depending on chain

## How to Use

Privacy providers are selected inside Privacy Cashout and Privacy Funding. Choose the provider, source mode, asset, destination wallets, and delivery settings, then review the provider quote before confirming.

- [Privacy Cashout](/treasury/privacy-cashout): Distribute funds privately using these providers.

- [Wallet Farm](/wallet-farm/overview): Prepare wallets before importing them into profiles.


---

# Manage Users

> Manage team members, roles, and permissions in your organization.

- URL: https://docs.sumo.trade/account/user-management
- Markdown: https://docs.sumo.trade/account/user-management.md
- Docs index: https://docs.sumo.trade/llms.txt

![Manage Users page with invite form and user table](/images/manage-users.png)

Manage your organization's team members from the [Manage Users](https://app.sumo.trade/users/manage) page. Invite new users, assign roles, and disable access when someone should no longer use the workspace.

## Inviting Users

1. Enter the user's **email address**
2. Select a **role** from the dropdown
3. Click **Invite**

The invited user receives an email with instructions to set up their account. Their status shows as **Invite Sent** until they complete signup.

## Roles

| Role                | Description                                                                                                |
| ------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Admin**           | Full organization access, including users, settings, wallets, treasury operations, strategies, and trading |
| **Trading Manager** | Can manage trading users below them and operate trading workflows                                          |
| **Trader**          | Can manage strategies, execute trades, and work with profile wallets                                       |
| **Analyst**         | Read-only access for dashboards, reports, logs, and wallet balances                                        |

The role options you can assign depend on your own role. Higher-privilege users can assign and manage more roles; lower-privilege users only see the roles they are allowed to manage.

## User Table

The table shows all users in your organization:

| Column      | Description                               |
| ----------- | ----------------------------------------- |
| **User**    | User's email address                      |
| **Role**    | Current role (editable via dropdown)      |
| **Status**  | Active, Inactive, or Invite Sent          |
| **Actions** | Save a role change or disable user access |

## Manage Users

* **Change role** — Select a new role from the dropdown and click the save icon
* **Disable user** — Click the disable icon to revoke a user's access; this requires admin access

You cannot modify your own role or disable your own account.

- [User Settings](/account/user-settings): Change your password, email, and 2FA preferences.

- [Rewards](/account/rewards): Manage launch tickets, cashback, and referrals.


---

# Rewards

> Buy launch tickets, claim referral revenue, claim rebates, and manage Sumo Balance activity.

- URL: https://docs.sumo.trade/account/rewards
- Markdown: https://docs.sumo.trade/account/rewards.md
- Docs index: https://docs.sumo.trade/llms.txt

![Rewards page showing Sumo Balance wallets, launch tickets, referral stats, and claim actions](/images/rewards-page.png)

The Rewards page is where organization rewards, launch-ticket inventory, and Sumo Balance activity live. It combines:

* Launch tickets for token launches
* Cashback / fee rebate claims
* Referral links, referral revenue, and referral claims
* Sumo Balance deposits, withdrawals, and ledger activity

Open it from **Rewards** in the app sidebar.

## Launch Tickets

Launch tickets let you prepay for token launches at a fixed price.

| Item              | Description                                                                       |
| ----------------- | --------------------------------------------------------------------------------- |
| **Price**         | $250 per ticket, paid in canonical USDC from your Sumo Balance                    |
| **Coverage**      | One ticket covers one token launch                                                |
| **Inventory**     | Tickets belong to the organization and remain available until applied to a launch |
| **Bulk Purchase** | You can buy multiple tickets at once from Rewards                                 |

![Buy Launch Ticket dialog](/images/rewards-buy-launch-ticket.png)

During a launch, choose **Launch Ticket** as the launch-fee payment method to consume an available ticket. If you do not want to use a ticket, choose the dev-allocation method instead; that method charges **0.25% of token supply** as the launch fee.

## Sumo Balance

Sumo Balance is the organization-level balance used for rewards and platform settlement activity.

You can use it to:

* Deposit supported assets on Solana, Ethereum, Base, or BNB Chain
* Buy launch tickets with canonical USDC
* Receive referral revenue claims
* Receive fee rebate claims
* Pay wallet marketplace fees
* Withdraw supported balances
* Swap between the native asset and the settlement stablecoin on a chain (admin only; the standard treasury swap fee applies and the result is reported in Rewards notifications)
* Review ledger entries and export history

The ledger tracks credits and debits such as referral revenue, fee rebate claims, wallet marketplace fees, and withdrawals.

## Cashback / Rebates

Cashback, shown in-app as fee rebates, returns eligible fee amounts to your Sumo Balance. When rebates are available, Rewards shows the claim action and chain-specific claimable amounts.

1. Open **Rewards**
2. Click the rebate claim action
3. Select the chain with claimable rebate amount
4. Confirm the claim
5. Review the transaction link and ledger entry after submission

Rebate availability depends on your organization's fee settings and confirmed activity.

## Referrals

The referrals section lets organization admins share an invite-code link and earn referral revenue from referred organizations. Referral revenue can be claimed from Rewards into Sumo Balance.

Referral tools include:

* **Referral Code** — your organization's referral code
* **Referral Link** — shareable signup link that applies the code
* **Vanity Code** — optional one-time custom referral code when available
* **Referral Terms** — your commission and the referred-org discount
* **Referral Stats** — earnings, balance, trade volume, and referred organizations
* **Claim Referrals** — pays claimable referral revenue into your Sumo Balance

Referral revenue claims are chain-specific. The claim dialog shows native and USDC amounts due for the selected chain.

## Referred Organizations

The referred organizations section lists every organization that signed up through your referral link. For each referred organization, Sumo can show:

* Organization name and signup date
* Number of trading profiles
* Trade volume
* Earnings and remaining balance

If you do not have any referred organizations yet, the page shows an empty state.

## Launch Fee Choices

For each launch, choose the payment method that fits that launch:

| Method             | Use When                                                                            |
| ------------------ | ----------------------------------------------------------------------------------- |
| **Launch Ticket**  | You want a fixed $250 launch cost and already have or want to buy ticket inventory. |
| **Dev Allocation** | You prefer to pay **0.25% of token supply** instead of prepaying in USDC.           |

- [Platform Fees](/platform-fees): See the full fee schedule.

- [User Settings](/account/user-settings): Manage account preferences and linked Telegram login.


---

# User Settings

> Change your password, email, and 2FA preferences.

- URL: https://docs.sumo.trade/account/user-settings
- Markdown: https://docs.sumo.trade/account/user-settings.md
- Docs index: https://docs.sumo.trade/llms.txt

![Settings page with UI preferences, email, password, two-factor, Telegram, and log out controls](/images/user-settings.png)

Manage your personal account settings from the [Settings](https://app.sumo.trade/settings) page.

## UI and Sounds

Use the **UI and Sounds** section to control your local interface preferences:

* **Interface** — Switch between supported interface modes
* **Notification Sound** — Choose Calm, Alerting, or Off
* **Sound Effects** — Enable or disable interaction sounds

## Change Password

1. Enter your **current password**
2. Enter a **new password** (minimum 8 characters)
3. **Confirm** the new password
4. Click **Update Password**

## Change Email

1. Enter your **new email address**
2. Enter your **current password** for verification
3. Click **Request Email Change**
4. Enter the **verification code** sent to your new email
5. Click **Verify Email Change**

## Two-Factor Authentication

Sumo requires a second factor on every login. Choose your preferred method:

* **Email** — A verification code is sent to your email on each login
* **Telegram** — A verification code is sent via the Sumo Telegram bot

Change your preference using the **Two Factor Authentication** dropdown.

To use Telegram 2FA, you must first [link your Telegram account](/integrations/telegram-bot).

## Telegram Linking

* **Link** — Click **Generate Link** to get a code, then enter it in the Sumo Telegram bot
* **Unlink** — Click **Unlink Telegram** to disconnect (reverts 2FA to email)

See [Telegram Bot](/integrations/telegram-bot) for the full setup guide.

## Log Out

Use **Log Out** at the bottom of Settings to end the current browser session.

- [Manage Users](/account/user-management): Manage team members and roles.

- [Rewards](/account/rewards): Manage launch tickets, cashback, and referrals.


---

# Key Export

> The owner-controlled policy that decides who may export wallet private keys, and how ownership is transferred.

- URL: https://docs.sumo.trade/account/key-export
- Markdown: https://docs.sumo.trade/account/key-export.md
- Docs index: https://docs.sumo.trade/llms.txt

Every organization has exactly one **owner**, and only the owner decides who may use [Export Keys](/wallets/export-keys) — the bulk export of wallet private keys from a profile's **Wallets** tab and from **Wallet Farm**. The controls live under **Settings → Key Export**, a section that is visible to the owner alone.

This policy covers those two surfaces only. The launch **deployer** export and the **Snipe Deck** wallet export are separate flows, available to admins regardless of these toggles.

## Who May Export

| Toggle                                  | Effect                           | Default |
| --------------------------------------- | -------------------------------- | ------- |
| **Allow me to export private keys**     | The owner may export             | On      |
| **Allow admins to export private keys** | Every admin and above may export | Off     |

When admins are allowed, pick how long the grant lasts: **1 hour**, **24 hours**, or **until turned off**. A timed grant expires on its own — the section shows the exact expiry — and the toggle returns to off with no further action.

Members below the admin role can never export, whatever the toggles say, and Export Keys on those two surfaces is always blocked while an account is being impersonated.

## One-Time Code

Turning either toggle on **or** off sends a 6-digit code to your email or Telegram, following your two-factor preference. The change is applied only after the code is entered, so a hijacked session cannot quietly widen key access.

Exports themselves never ask for a code — the policy above is the gate.

> The switch reflects the saved server state, not your click: it moves only once the code is accepted.

## What Exporting Does

Exporting reveals private keys for up to **250 wallets** at a time and flips each exported wallet's custody from **Sumo** to **Shared** — the key now also exists outside Sumo. Custody never flips back, and every export is recorded in [Audit Logs](/reporting/audit-logs).

Export lives in two places, both governed by this policy:

* [Profile wallets](/wallets/export-keys) — the **Wallets** tab's **More** menu
* [Wallet Farm](/wallets/export-keys&#x29; — the toolbar's &#x2A;*⋯** menu

The deployer key export (**Export Deployer PK**, same **More** menu) and the Snipe Deck wallet export are not governed by these toggles; see [Security & Encryption](/wallets/security-encryption).

## Ownership

The **Ownership** sub-section names the current owner and can hand ownership to another member. Pick any active member with the admin, ops manager, or superadmin role, then confirm with a one-time code.

Ownership transfer takes effect immediately: the new owner gains the Key Export section and you lose it, so transfer only to someone who should hold that control. A Sumo superadmin can also reassign an organization's owner with a recorded reason — for example when the current owner has left.

- [User Management](/account/user-management): Roles and who can be made owner.

- [Security & Encryption](/wallets/security-encryption): How Sumo stores wallet keys.


---

# Platform Fees

> Sumo's transparent fee structure for trading volume and token launches.

- URL: https://docs.sumo.trade/platform-fees
- Markdown: https://docs.sumo.trade/platform-fees.md
- Docs index: https://docs.sumo.trade/llms.txt

Sumo charges a **1% platform fee on Sumo-executed trading volume**. Token launches also require a launch fee, paid as **either** a $250 launch ticket **or** 0.25% of token supply as dev allocation.

Deposits, withdrawals, wallet generation, and internal wallet management do not have a Sumo platform fee.

## How It Works

When Sumo executes a buy or sell through a strategy or manual trading action, the platform fee is calculated from the executed trade volume. The fee is tracked and shown in the **Sumo Trade Fees** metric in Insights.

Network gas, DEX fees, aggregator fees, and third-party privacy provider fees are separate from Sumo's platform fee.

| Action                           | Fee                                                                         |
| -------------------------------- | --------------------------------------------------------------------------- |
| **Sumo-executed trading volume** | 1% of executed volume                                                       |
| **Token launch**                 | Choose one: **$250 launch ticket** or **0.25% token supply dev allocation** |
| **Deposits**                     | Free                                                                        |
| **Withdrawals**                  | Free                                                                        |
| **Internal transfers**           | Free                                                                        |
| **Wallet generation**            | Free                                                                        |

## Launch Fees

For each launch, you choose one launch-fee payment method. Sumo does not charge both the launch ticket and dev allocation for the same launch.

| Method             | How it Works                                                                                             |
| ------------------ | -------------------------------------------------------------------------------------------------------- |
| **Launch Ticket**  | Buy a launch ticket for **$250** in canonical USDC from your Sumo Balance. One ticket covers one launch. |
| **Dev Allocation** | Pay **0.25% of the launched token supply** as a dev-allocation fee.                                      |

Launch tickets are organization-level inventory. You can buy multiple tickets at once from the [Rewards](/account/rewards) page, then apply one ticket to a later launch.

The dev-allocation method is useful when you do not want to prepay in USDC. The ticket method is useful when you want a fixed launch cost before launch execution.

## Example

If Sumo executes **$10,000** of trading volume:

* Platform fee: **$100** (1%)
* Trading, strategy, and fee totals are reflected in Insights and logs

If you launch a token:

* Launch ticket method: **$250** ticket consumed for that launch
* Dev-allocation method: &#x2A;*0.25%** of token supply collected as the launch fee

Only the method selected for that launch is charged.

## What's Included

The platform fee covers:

* Automated strategy execution
* Enterprise-grade wallet encryption and key management
* Real-time trade monitoring and analytics
* MEV-aware transaction and bundle execution where supported
* Multi-chain DEX routing
* Token launch infrastructure
* Telegram bot notifications
* Unlimited wallet generation
* Priority support

> **No hidden fees.** There are no monthly subscriptions, deposit fees, or withdrawal platform fees.

- [Rewards](/account/rewards): Buy launch tickets, claim referral revenue, and track Sumo Balance activity.

- [Launch Tokens](/launch-tokens/pumpfun-launch): Review supported launch methods.

## Further Reading

* [How to Choose a Market Making Bot](https://blog.sumo.trade/how-to-choose-a-market-making-bot/) — how hidden execution costs dwarf any provider's sticker price


---

# FAQ & Troubleshooting

> Frequently asked questions and common troubleshooting tips.

- URL: https://docs.sumo.trade/faq
- Markdown: https://docs.sumo.trade/faq.md
- Docs index: https://docs.sumo.trade/llms.txt

Common questions and solutions for Sumo users.

## General

### What is Sumo?

Sumo is a market making platform for token founders and professional market makers. It provides automated trading strategies, secure wallet management, and real-time analytics across Solana and EVM chains.

### Who is Sumo for?

Sumo is built for three primary audiences:

* **Token founders** who want to maintain healthy liquidity and price stability for their token
* **Market makers** who manage trading operations across multiple tokens and DEXes
* **Launch teams** who need to prepare wallets, launch tokens, and coordinate trading operations from one workspace

### Which chains does Sumo support?

Sumo supports **Solana**, **Ethereum**, **BNB Smart Chain**, **Base**, **Robinhood Chain**, **Stable Mainnet**, and **Tron**. See [Supported Chains](/integrations/supported-chains) for the full list.

### How much does Sumo cost?

Sumo charges a **1% platform fee on Sumo-executed trading volume**. There are no monthly subscriptions, setup costs, deposit platform fees, or withdrawal platform fees. Network gas, DEX fees, aggregator fees, and privacy provider fees are separate. See [Platform Fees](/platform-fees) for details.

### How do I create an account?

Sumo signup is invite-only. If you need access, contact us on [Telegram](https://t.me/sumo_support) for an invite code. After signup, you can invite teammates from [Manage Users](/account/user-management).

## Strategies

### What strategies does Sumo offer?

Sumo offers automated strategies and manual trading tools:

* **Counter Trade** — Automatically counter external buys/sells to stabilize price
* **DCA** — Scheduled buys or sells at regular intervals
* **Limit Orders** — Conditional trades based on market cap ranges
* **Instant Trade** — Manual buys and sells using preset or custom amounts
* **Treasury Swap** — Manual swaps between supported stablecoin/profile asset pairs

See [Strategies Overview](/strategies/overview) for details on each.

### What happens if my strategy fails?

Failed trades are logged with a failure reason in [Trade Logs](/reporting/trade-logs). Your funds remain safe in your wallets — a failed trade never results in lost funds. Common failure reasons include slippage exceeded and insufficient balance.

### Can I run multiple strategies at once?

Yes. You can run multiple strategies simultaneously on the same profile, even across different wallet groups.

## Wallets & Security

### Are my private keys safe?

Yes. Sumo uses **AES-256-GCM envelope encryption** with master keys stored in a hardware security module (HSM). Private keys are decrypted only in an isolated signing service's memory for the brief moment needed to sign a transaction. See [Security & Encryption](/wallets/security-encryption) for details.

### How many wallets can I create?

There is no fixed organization-wide wallet limit. You can generate wallets from a seed, import existing wallets, or move prepared wallets from Wallet Farm into a profile. Some bulk workflows cap the number of wallets per operation to keep execution reliable.

### What is a wallet group?

Wallet groups let you organize wallets into named, color-coded sets. You can assign strategies to specific groups, run treasury operations on a group, and use groups for token launch bundles. See [Wallet Groups](/wallets/wallet-groups).

### What is Wallet Farm?

Wallet Farm is a workspace for preparing wallets before they belong to a specific trading profile. You can generate or import wallets, organize them into folders, fund them privately, generate activity, and then import prepared wallets into a profile. See [Wallet Farm](/wallet-farm/overview).

## Treasury

### Do withdrawals have a Sumo platform fee?

No. Withdrawals do not have a Sumo platform fee. Source wallets still pay normal network gas or transaction fees required by the chain.

### How long do withdrawals take?

Withdrawals are processed on-chain and typically confirm within seconds on Solana. EVM chain withdrawals depend on the network's block time and congestion.

### What is Privacy Cashout?

Privacy Cashout distributes native assets or supported stablecoins from one or more source wallets to destination wallets through a third-party privacy provider, breaking the direct on-chain link between source and destinations. See [Privacy Cashout](/treasury/privacy-cashout).

### Does Privacy Cashout support stablecoins?

Yes. Privacy Cashout supports native assets and registered stablecoin-to-same-stablecoin swaps when that asset is available for the selected chain and provider, such as USDC to USDC, USDT to USDT, or USD1 to USD1.

## Account

### How do I invite teammates?

Open [Manage Users](/account/user-management), enter the teammate's email address, choose a role, and send the invite. Their status shows as **Invite Sent** until they complete signup.

### Can I use Telegram for login verification?

Yes. Link Telegram from [Settings](/account/user-settings), then choose Telegram as your two-factor authentication method. See [Telegram Bot](/integrations/telegram-bot).

### How do referrals work?

Each organization can generate a referral code and shareable signup link. Referred organizations receive the configured discount, and your organization earns commission on eligible platform fees. See [Rewards](/account/rewards).

## Need Help?

If you can't find an answer here, reach out to our support team through the Sumo dashboard or [Telegram](https://t.me/sumo_support).