What PAIR does differently
PAIR, at pair.fund, calls itself the first multipool launchpad, and the description is literal. Where other platforms create one market for a new token, PAIR can create up to five at once, each pairing the token against a different Robinhood Stock Token, all built on Uniswap v4 hooks. It was announced on 31 August 2026 alongside an AWS infrastructure partnership.
There is no bonding curve, no price ceiling and no migration. The pool a token trades in during its first second is the pool it trades in a year later. For a copier that removes a whole class of timing problems: there is no graduation event to be caught on the wrong side of.
The launch transaction, as published
A PAIR launch is one atomic transaction. The PairLaunchpadV5Upgradeable contract deploys a new ERC-20 with a fixed supply of one billion tokens and creates one to five Uniswap v4 pools, one for each stock the creator selected. The protocol launch fee is 0.0005 ETH and deployment takes under a minute.
The stock list is the widest on the chain: AAPL, AMC, AMD, AMZN, BABA, BE, CRCL, CRWV, GOOGL, INTC, META, MSFT, MU, NVDA, ORCL, PLTR, QQQ, SGOV, SLV, SNDK, SPCX, SPY, TSLA and USAR. A creator can therefore launch a token quoted simultaneously against a chipmaker, an index proxy and a treasury-like asset.
How a multipool trade executes
PAIR's interface defaults to AUTO routing through a contract called PairV5MultiPoolAggregator. It balances a single buy or sell across up to five pools, using USDG as the common input or output leg, quotes every leg before executing, and rejects routes whose live price impact exceeds 15 percent.
| Single-pool launch | PAIR multipool launch |
|---|---|
| One swap event per trade | Several legs for one user action |
| Pool address identifies the market | Five pool addresses can all be the same token |
| Price impact is one number | Impact is assessed per leg, with a 15 percent ceiling |
| Quote asset is fixed | USDG is used as the common leg between stock pairs |
| Slippage tuning is per pool | Slippage tuning has to assume a route, not a pool |
This is where venue-specific copy bots break. A bot that watches swap events and expects one event per trade will either miss legs or double count them, and a bot keyed to a single pool address will not recognise the same token arriving through a different leg.
Why transfer-log detection still works here
A wallet either ends up with more of the token or less of it. Filtering ERC-20 Transfer logs by the followed address as an indexed topic gives exactly that answer, regardless of how many legs the aggregator used, because the net effect on the wallet is what the logs record.
That is the same reason this approach survives Uniswap v4 generally on Robinhood Chain: the v4 swap event names the router rather than the trader, and with ERC-4337 smart accounts in common use the transaction sender is often a bundler. Reading the wallet instead of the venue sidesteps both problems and a five-leg route at the same time.
Sizing a copy across five pools
The headline risk on PAIR is not the token, it is depth per leg. Three habits handle it.
- Use fixed sizing rather than percent-of-theirs for multipool tokens until you know how deep the legs are. A leader with a larger book can absorb a route that your smaller copy cannot improve on.
- Keep a per-trade cap that is small relative to the thinnest leg you are willing to trade, not the total.
- Set a minimum pool size filter. On a five-way split, a token can look liquid in aggregate while the leg your route needs is nearly empty.
Exiting a position that lives in several markets
Because there is no migration, the exit is the same shape as the entry: a route across legs, priced against stock tokens with USDG in the middle. Two consequences matter.
- Mirroring the leader's exit is usually the better policy, because they are exiting the same route structure you are.
- A hard percentage stop can trigger on a leg-specific price move rather than a real change in the token's value, so if you use your own rules give them more room than you would on a single-pool token.
Recommended settings for PAIR wallets
| Setting | Starting point | Reason |
|---|---|---|
| Size rule | Fixed amount | Route depth, not leader conviction, is the binding constraint |
| Per-trade cap | Tight | Protects against a thin leg on a wide route |
| Minimum pool size | On | Aggregate liquidity can hide an empty leg |
| Buy slippage | Moderate, not maximal | A route rejected at 15 percent impact is a signal, not an obstacle |
| Exit mode | Mirror, partial mirroring on | The leader exits the same structure you do |
| Contract filters | All on | No curve means no graduation checkpoint to lean on |
Following a PAIR wallet step by step
- 01Confirm the token is a PAIR launchLook for a fixed one billion supply and several Uniswap v4 pools for the same token, each quoted against a different Stock Token.
- 02Check which legs have depthA five-way split can be uneven. The leg your route uses decides your slippage, not the token's total liquidity.
- 03Follow the wallet with a small budgetGive multipool leaders a tighter per-leader budget while you learn how their routes behave.
- 04Use fixed sizing and a minimum pool filterFixed amounts plus a depth floor is the combination that survives thin legs.
- 05Mirror exits with partial mirroringCopy trims as trims, since a partial exit on a route is common.
- 06Arm the engine and watch rejectionsIf the depth filter is rejecting everything, the venue is telling you the legs are too thin for your size.
Questions people actually ask
What is a multipool launch?
It is a launch where the same token is deployed into several liquidity pools at once, each against a different quote asset. On PAIR a single atomic transaction creates one to five Uniswap v4 pools, one per selected Robinhood Stock Token, with a fixed supply of one billion tokens.
How does a trade get split across the pools?
PAIR's interface routes through a contract it calls PairV5MultiPoolAggregator. It balances one buy or sell across up to five pools using USDG as the common leg, quotes each leg first, and refuses routes whose live price impact would exceed 15 percent.
Does multipool routing break copy detection?
It breaks detection that watches swap events, because one user action produces several legs and the v4 event names the router. It does not break detection that filters ERC-20 Transfer logs by the followed wallet, because those logs record the net movement of tokens into or out of the address whatever route was used.
Is there a bonding curve or a graduation on PAIR?
No. PAIR publishes no curve, no price ceiling and no migration: the launch pool is the permanent pool. That removes graduation timing risk but also removes the checkpoint some traders use as a quality filter, so contract and depth filters matter more.
What does the 0.0005 ETH fee cover?
It is the protocol launch fee charged when the token and its pools are deployed, which PAIR describes alongside a deployment time of under a minute. It is a creator cost rather than a trading cost, so it does not change your entry price as a copier.
Should I copy every leg the leader trades?
You are not copying legs, you are copying a position. Your engine sends its own transaction, so what matters is whether your own route can fill at an acceptable price. If the depth filter rejects a candidate, that is the venue telling you your size does not fit the route the leader had access to.
Figures that move are quoted with the date they were measured. Pons Copy Trading does not publish numbers it cannot point at a source for.