Running a volume campaign on Orca

Liquidity lives in a range, not across the curve

A constant-product pool spreads its liquidity across every possible price, which is inefficient but predictable. Orca's Whirlpools do the opposite: each liquidity provider chooses a price range and concentrates capital inside it. The result is far deeper trading near the current price when the ranges are set well, and almost nothing when they are not.

For a volume campaign this changes the question you have to answer. It is no longer "how much liquidity does this pool hold" but "how much liquidity sits at the price I will be trading at". Those are different numbers, and only the second one affects your execution.

The practical consequence: two Orca pools with identical headline figures can behave completely differently. One absorbs your swaps without moving; the other turns every trade into a visible step on the chart.

What an out-of-range pool does to your budget

When price drifts past the edge of where liquidity was placed, the pool does not fail loudly. It just gets very expensive to trade against.

• Impact rises sharply. The same swap that moved nothing yesterday moves several percent today.
• Slippage failures follow. Transactions revert, and each one still pays its base and priority fee while producing no volume.
• The chart looks broken. Sharp steps in both directions, which is exactly the shape that makes a visitor close the tab.
• Costs double up. You are paying fees to move price against yourself, then paying again on the way back.

None of this is fixable with settings. Widening slippage tolerance converts failures into bad fills; tightening it converts bad fills into failures. The only real answers are liquidity repositioning or routing elsewhere.

Fee tiers are a choice made when the pool was created

Orca pools carry a fee tier selected at creation, and the range across tiers is wide: very low on pairs that barely move, up to a full percent on volatile ones. Two pools for the same token can sit on different tiers.

This matters more than people expect, because the venue fee scales with volume rather than with transaction count. Network fees stay small in absolute terms no matter how many swaps you send; a percentage of every SOL routed does not. On a campaign of any size, the tier is a larger line item than everything the network charges combined, which the fee breakdown works through with real numbers.

A worked example makes the tier concrete. Take 200 SOL of target volume. On a pool sitting at a quarter of a percent, the venue takes half a SOL across the campaign. On a pool sitting at a full percent, it takes two. The difference between those two pools is four times the entire network fee bill for a campaign of that size, and it is a property of the pool rather than anything you configure. Two pools for the same token, one on each tier, are not interchangeable venues.

There is a second-order effect worth knowing. Higher-tier pools attract liquidity providers precisely because volatile pairs need compensating, so the deeper pool for a young token is sometimes the more expensive one. Cheaper is not automatically better; a thin pool on a low tier can cost more in price impact than a deep pool on a high one charges in fees. Read both numbers before deciding.

Checking an Orca pool in about a minute

1. Simulate a realistic buy. Not your best case, the ordinary one. Any aggregator interface quotes it and shows the impact without executing.
2. Read the impact, not the pool size. Under a percent for a normal order means the range covers your price. Several percent means it does not.
3. Repeat for the sell. Ranges are frequently asymmetric, and a pool that fills buys cleanly can choke on sells.
4. Check the fee tier. It multiplies against every SOL you route.
5. Count the other pools. If the token trades elsewhere too, the campaign should not be an Orca-only decision.

Shaping a campaign that suits the venue

Assuming the range covers your price, Orca is a good venue precisely because concentration means depth. The design implications are straightforward.

Keep swaps small relative to the concentrated depth. The advantage of a well-positioned Whirlpool is that small swaps are nearly free of impact. Larger ones give that advantage back quickly once they start eating through a tick range.

Use more wallets rather than bigger trades. The same target volume delivered as many small swaps produces better trade-count and unique-address figures while moving the pool less, which is the trade-off covered in the fleet sizing guide.

Watch for range drift during long campaigns. A campaign that runs for hours can push price toward the edge of the liquidity band, at which point everything above starts applying. Shorter, denser windows are safer here than long thin ones.

Expect asymmetry and plan for it. Because providers choose their own ranges, the depth available above the current price and below it are frequently different. A campaign with balanced buy and sell flow will therefore see the two directions execute differently, and the side with less depth is where your failures and your visible price steps will cluster. Simulating both legs before you start is the only way to see this, and it changes how you set the buy-pressure weighting.

Why an Orca-only campaign is usually the wrong plan

Even when the pool is ideal, concentrating a whole campaign into one venue is a bad trade on three counts at once. It maximises impact per swap, because every trade hits the same reserves. It maximises failure rate, for the same reason. And it produces a pattern that reads as one participant hammering one pool, because real demand arrives through whichever pool each trader's router picked.

Spreading across every venue the token has liquidity on fixes all three with one decision, and it is why routing here is automatic rather than a checkbox. Our weekly measured failure rates show how far apart venues sit on execution, which is the argument for spreading stated in numbers rather than in principle.