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.
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:
- Token metadata ready: name, ticker, image, description, and social links
- ETH on Robinhood Chain for the ordered V4 buys, the creator gas reserve, and per-wallet cleanup buffers
- A launch plan: supply control target, optional dev buy, creator-fee preference, bundle wallet count, and holder cleanup preference
- A wallet plan: use ready wallets from private keys, Wallet Farm, or another profile, or create new Robinhood Chain wallets / buy aged EVM wallets through 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 |
|---|---|
| Launch plan | Sets the dev buy, the bundle and the snipe on one bar, with the cost strip under it; see Launch Plan. Dev buy plus bundle: 1% to 99% (Max 99%). Once dev-only launches are available, a 0% bundle makes a dev-only launch, and a 0% dev buy with it a create-only launch. |
| Dev buy | Launch plan row, with its range beside the label: optional dev-wallet buy before the bundle. Set to 0 for no dev buy. |
| Bundle · at launch | Launch plan row: the share bought by the bundle wallets, without the dev buy. |
| Bundle cost | Launch plan cost strip: ordered Uniswap V4 buys plus the creator gas reserve and configured per-wallet cleanup buffers. |
| Market cap | Launch plan cost strip (MCap after with a snipe): 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. |
| 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. Dev-only launches become available once Pools.trade's updated launch delegate is live. Then, when the Launch plan's bundle is 0%, there is no bundle buy (the row reads Dev buy only): the launch is dev-only (create-only when the dev buy is 0% too), so Bundle Wallets and Holder Wallets are hidden, no bundle or holder wallets are created, only the dev wallet is funded, and no token cleanup runs unless snipe wallets join holder cleanup (see Snipe After Launch in Launch a New Token). With Token Supply launch-fee payment the fee then comes from the dev wallet, so the dev buy must be at least the fee share of supply; otherwise use a Launch Ticket. |
| 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. With Token Cleanup Method Off the wallets are still created, but nothing funds or fills them, and the per-bundle-wallet limits do not apply. |
| 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. |
| Trading slippage | Default 1%, at most 10%. Becomes the new profile's default slippage for strategies and instant trades, changeable later in profile settings. On a taxed token the tax is added on top and saved (for example 1% + 5% tax = 6%). |
| Cleanup slippage | Sell / Buy holder cleanup only. Default 2%, at most 10%, not counting tax: the token's buy or sell tax is added automatically for each leg. Each cleanup sell and buy gets up to three attempts, each with 1% more tolerance, up to 10%. |
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. With Token Cleanup Method Off they are still created and stay empty. |
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, or reusing wallets from another profile. Additional paths include creating new wallets or buying aged inventory from 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, DCA, and Limit Order 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 bundle supply control, dev buy, bundle buy, launch cost, estimated market cap, and whether creator fees are enabled.
There is no separate deploy or pool-creation step. Two actions are available:
- Simulate Launch - Plans the ordered V4 buys and reports any blockers before funds move.
- 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.
Snipe After Launch
Optional Snipe after launch wallets buy right after the launch lands, with their own sizing, delay, max premium, pacing and gas priority. Set Snipe Wallets to 0 (the default) and the launch is unchanged. See Snipe After Launch.
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.
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.
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.