Before placing a large limit order, simulate the full executable route at your order size and set a maximum price impact the treasury can tolerate. A pool’s headline TVL does not tell you how much can trade near the current price: in a concentrated-liquidity market maker, much of that capital may sit outside the active range.
Measure active depth across your order’s price limit
For a concentrated-liquidity pool, the useful quantity is active liquidity at each price along the trade, not the sum of tokens held in the pool’s vaults. Positions outside the current tick contribute no immediate swap depth; as a swap moves through ticks, the active liquidity can rise or fall abruptly.
For a single range with liquidity L and token1 priced in token0, ignoring fees, moving from price P₀ to P₁ consumes approximately L(√P₁ − √P₀) units of token1 when price rises. The corresponding token0 output is approximately L(1/√P₀ − 1/√P₁). A real quote must account for tick crossings, fee tier, token decimals and every pool in the route.
Read a size ladder at several trade sizes, such as 25%, 50%, 75% and 100% of the planned transfer. Record average execution price, price impact versus the starting mid-price, output after fees, and the price reached by the last unit. A quote only at the full size can hide a sharp deterioration near the end.
Separate pool depth from route quality
A routed swap can combine pools, so its result depends on the route’s aggregate depth and the cost of each hop. Compare the best route with direct quotes from relevant pools, including Orca and Raydium when they hold the pair. A route split may improve the average price, but extra hops add fees, account complexity and another source of state change before execution.
For example, suppose a treasury must convert 200,000 USDC for a scheduled payout. An illustrative quote might show 100,000 USDC at 4 basis points of impact, 150,000 at 11 basis points, and 200,000 at 38 basis points because the route crosses a thin tick range. That step-up matters more than a pool’s displayed dollar value: the order can be divided into clips or assigned a stricter limit, subject to payout timing.
Byreal is a Solana DEX for token swaps and concentrated liquidity. Teams researching how to use its venue can consult what to check on Byreal for the broader swap and liquidity explanation; this article focuses on evaluating executable depth for a large trade.
Model the limit as an execution constraint
A limit price caps the worst acceptable rate; it does not guarantee that the entire size will fill. Depending on the execution system, an order may wait for a trigger, submit a swap when its condition is met, or be routed through an RFQ process. Confirm which mechanism applies before treating a quote as firm liquidity.
Set the limit from the business requirement, not from a convenient round number. If the payout requires at least 199,400 USDC-equivalent value for the proposed conversion, derive the minimum acceptable output after pool fees and any route costs, then translate that into the maximum input-per-output price. For an RFQ route, compare the quoted size, expiry and settlement conditions against the pool simulation; a firm quote can be useful even when public pool depth is thin.
Recheck state and execution risk before release
Pool state can change between simulation and transaction execution. A competing swap can move the price, an LP can remove liquidity, or the market can cross into a range with less active liquidity. Use a fresh quote close to signing, specify a slippage bound consistent with the treasury policy, and reject execution if the realized route or output no longer meets the approved limit.
When comparing a Byreal pool with other routes, use the same input amount, token direction and quote time. Verify token mints rather than relying on symbols, account for token decimals, and distinguish active liquidity from vault balances. Stale indexed data, shallow newly created pools and a route that depends heavily on one tick boundary can each make apparent depth misleading.
For recurring transfers, keep a record of quoted and realized output, impact, fees and fill time by size bucket. That history reveals when to split a payment, request a fresh RFQ, or move the execution window; my practical tip is to size the largest clip against the weakest depth observed in the recent payout window.