Copying pools.trade launches, Uniswap's own launchpad

What pools.trade is

pools.trade is the first token launch platform built by Uniswap Labs, and it launched on Robinhood Chain on 5 August 2026. Every launch ends as a Uniswap v4 pool. Tokens are minted with a fixed supply of one billion, the pool charges a 0.25 percent LP fee, and those fees autocompound into a liquidity position the creator cannot remove.

There is no launchpad fee. Uniswap describes the 0.25 percent as a fraction of the roughly 1 percent charged on other launchpads, and a creator can optionally take 0.05 percent of that 25 basis points as their own fee.

Instant Launch versus Crowd Launch

Those two rows at the bottom are the whole story for a copier. An Instant Launch is a burst: the flow that matters happens in the first minutes and a late copy is a different trade from the one the leader made. A Crowd Launch is a scheduled event with a four hour window, so the wallets you follow may be bidding rather than buying, and the price they get depends on when they bid rather than on the pool state at that moment.

The fee model, and what it means for high copy rates

A 0.25 percent LP fee is low for a launch venue. That is genuinely useful when you are copying: fees are the one cost that scales linearly with how many copies you make, and a copy engine at a hundred copies a day pays that fee a hundred times.

• Round trip fee cost at 0.25 percent per side is about half a percent before slippage, compared with roughly two percent on a 1 percent venue.
• There is no launch tax to screen for, unlike the configurable taxes on some other Robinhood Chain venues.
• Because fees autocompound into the locked position rather than being extracted, pool depth tends to grow with volume rather than shrink.

Locked liquidity, and the risk it does not remove

Uniswap describes the launch liquidity as protocol held and impossible for the creator to remove, with fees compounding into that position. This removes one specific, common failure: the creator pulling the pool.

Copying an Instant Launch

The creator buys in the same block as the launch, by design, so outside bots cannot be first. As a copier you are not competing with that: you are following a wallet that decided to buy, which happens after the launch block anyway.

1. Keep the maximum trade age short. On a curve, price moves as supply sells, so a copy sent thirty seconds late is buying a different price.
2. Use fixed sizing. Percent-of-theirs sizing on a fast curve amplifies a leader's aggressive entry into your account.
3. Set a slippage ceiling and let it reject rather than chase. A rejected copy on a launch burst is usually a saved trade.

Copying a Crowd Launch

Crowd Launch is unusual because it has a deadline and a refund condition: bids are collected over four hours with earlier bids priced better, and if the launch does not reach a 10,000 dollar FDV everybody is refunded.

A copy engine watching transfer logs sees the result of that process rather than the bidding itself, which is the right place to be. The practical approach is to treat the post-graduation pool as the market you copy into, and to let the wallets you follow take the bidding risk with their own capital.

Settings that fit pools.trade

Following a pools.trade wallet step by step

1. 01Identify the launch formatAn Instant Launch trades immediately on a curve. A Crowd Launch collects bids for four hours and can be refunded below a 10,000 dollar FDV.
2. 02Pick wallets by behaviour, not by hit rateA wallet that buys the first minute of every Instant Launch is a different leader from one that waits for a pool to settle. Follow the one whose timing you can actually copy.
3. 03Set the age limit and slippage firstThese two settings decide whether your copies land at a price close to the leader's or well behind it.
4. 04Follow with a budget and fixed sizingFixed amounts keep a fast curve from turning a leader's conviction into your concentration.
5. 05Mirror exits by defaultThe 0.25 percent fee makes round trips cheap enough that following their exit is rarely the expensive choice.
6. 06Arm the engine and read the logAge and slippage rejections are the useful ones here. They tell you the burst was over before your copy could land.

Questions people actually ask