What we counted on the chain
In a 400 block sample on Robinhood Chain taken on 14 September 2026, we saw 97 distinct Uniswap v3 pools emitting swap logs under topic 0xc42079f9..., alongside a single v4 PoolManager and 21 v2 style pairs. The v3 router at 0xcaf681a66d020601342297493863e78c959e5cb2 appeared with the exactInputSingle selector 0x04e45aaf, which is the plain single-pool swap path.
One of our verification traces makes the practical picture concrete: a single leader wallet over 4,000 blocks, roughly seven minutes, produced six buys in one token between 0.00003 and 0.00199 ETH, all routed through the v3 router. Detecting all of it cost two RPC calls.
Concentrated liquidity, in the terms that matter
In a v2 pair, liquidity is spread along the entire price curve, so depth degrades smoothly and predictably. In v3, liquidity providers choose a price range, and all their capital sits inside it. Inside the range the pool can be very deep; a few percent outside it, almost empty.
| Situation | What a copy experiences |
|---|---|
| Price mid-band, deep liquidity | Small slippage, a fill close to the leader's price |
| Price near the band edge | Slippage jumps sharply for the same trade size |
| Price outside every band | The trade crosses to the next tick range, or reverts |
| Single-sided launch liquidity | Depth on one side only, so buys and sells are asymmetric |
Reading a v3 trade from outside
v3 is friendlier than v4 to an observer: each pool is its own contract, so the log address identifies the market. But the swap event still reports the sender as whatever contract called the pool, which for almost all retail flow is a router.
On Robinhood Chain that is usually the v3 SwapRouter or the Universal Router at 0x8876789976decbfcbbbe364623c63652db8c0904, whose execute selector 0x3593564c can bundle several actions into one call. Add ERC-4337 smart accounts, common on this chain through the EntryPoint at 0x4337084d9e255ff0702461cf8895ce9e3b5ff108, and neither the event sender nor the transaction sender reliably identifies the trader.
Detection that survives routers and bundlers
Filter ERC-20 Transfer logs by the followed wallet as an indexed topic. Tokens arriving means a buy, tokens leaving means a sell, and the pool, the router and the bundler are all irrelevant to that reading. A topic OR list carries every followed address in a single filter, so the call cost does not grow with the size of your wallet list.
Why a late fill hurts more on v3
On a constant-product pair, arriving two seconds late means paying a slightly worse price along a smooth curve. On v3, arriving late can mean the price has left the deep part of the band, so the same trade size now costs several times the slippage it would have cost moments earlier.
- Keep maximum trade age short, because band position changes with price rather than with time, and price moves at ten blocks per second here.
- Set the slippage ceiling to a number you would accept as a price, not as a formality. On v3 the ceiling is what stops a band-edge fill.
- Prefer fixed sizing on thin pools. Percent-of-theirs sizing sends a larger copy exactly when the leader was confident, which is often when the band is already stretched.
Settings for v3 heavy wallet lists
| Setting | Starting point | Reason |
|---|---|---|
| Buy slippage | Firm ceiling | The only defence against a band-edge fill |
| Sell slippage | Slightly wider than buys | Exits matter more than entries, but not at any price |
| Per-trade cap | Small relative to visible depth | v3 punishes size more sharply than v2 |
| Maximum trade age | Short | Band position is a function of price, and price moves fast |
| Minimum pool size | On | A first-pass filter, not a guarantee |
| Exit mode | Mirror, partial mirroring on | Leaders often exit in pieces on thin bands |
Curve launches that land in a v3 pool
Several Robinhood Chain venues end up in v3 rather than v4. Flap deploys straight into a v3 pool with single-sided liquidity and a locked LP, and hood.fun's described model migrates a completed curve into a locked v3 position. If you copy wallets that trade those venues, you are copying into v3 mechanics whether or not the branding mentions it.
Single-sided launch liquidity is the case to watch. Depth exists on one side of the price, so buying and selling the same size are not symmetric operations, and the sell side is the one you need when you are trying to leave.
Copying a wallet that trades v3 pools
- 01Follow the wallet with transfer-log detectionRouter calls and smart accounts hide the trader in the swap event, so read the wallet instead.
- 02Check the active range, not the totalLook at where price sits relative to the liquidity band before deciding your size.
- 03Set the slippage ceiling as a real price limitThis is the setting that prevents a band-edge fill from becoming a permanent loss.
- 04Keep the per-trade cap smallOn concentrated liquidity, size costs more than it does on a constant-product pair.
- 05Mirror exits with partial mirroringThin bands encourage partial exits, and a trim copied as a full close is its own mistake.
- 06Watch slippage rejections in the logA run of them on one token means the band moved and the pool is no longer the market you sized for.
Questions people actually ask
How many Uniswap v3 pools are active on Robinhood Chain?
We counted 97 distinct v3 pools emitting swap logs in a 400 block sample on 14 September 2026, alongside one v4 PoolManager and 21 v2 style pairs. That is a sample rather than a census, but it shows v3 is a significant part of the chain's flow rather than a legacy corner.
Why does concentrated liquidity matter for copy trading?
Because depth sits inside a price range instead of along the whole curve. Inside the band a pool can absorb size cheaply; near the edge the same trade slips several times as much. A copy that arrives a few seconds late can therefore pay a very different price from the leader, which is why trade age and slippage ceilings matter more on v3.
Can I identify the trader from a v3 swap event?
Not reliably. The pool is its own contract so the market is identifiable, but the event's sender is the router that called it, typically the v3 SwapRouter or the Universal Router. With ERC-4337 smart accounts also in use, the transaction sender can be a bundler, so wallet-level transfer-log detection is the dependable route.
What is single-sided launch liquidity?
Liquidity deposited on one side of the price rather than both, which several Robinhood Chain launch venues use. It means buying and selling the same size are asymmetric operations, and the side you need when exiting may be much thinner than the side you entered through.
Should sell slippage be wider than buy slippage?
Usually a little, because the cost of not exiting is higher than the cost of not entering. Wider does not mean unlimited: on a thin band an unbounded sell can hand you a much worse price than waiting a few blocks, so set it as a number you would accept rather than as a formality.
Is v3 easier or harder to copy than v4?
Slightly easier to observe, because each pool has its own address, and slightly harder to size, because depth is concentrated in a band. Detection is identical for both when you read wallets rather than venues, so the difference shows up in your slippage and size settings, not in the engine.
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.