A trader's guide to liquidity pool crypto and real float

Quick answer: When you inspect liquidity pool crypto balances, separate pool inventory from tokens held by ordinary wallets. Then classify staking, burns and treasury holdings to estimate real float, and check active pool depth to judge how much selling the market can absorb.
A headline market cap does not tell you what your exit will cost. It applies a marginal trading price to a supply figure, without proving that the market could absorb that supply.
You need separate views of ownership, liquidity and control.

Why liquidity pool crypto inventory needs its own label
A pool's token balance is market inventory, not an ordinary holder's position. In a constant-product pool, traders deposit one asset and withdraw the other, changing reserves and the quoted price.
That inventory belongs in your liquidity analysis. It should not also be treated as an independent wallet waiting to sell into the same pool.
Concentrated liquidity adds another distinction: total inventory is not necessarily active depth. Liquidity positioned outside the current trading range may contribute little to the trade you want to execute now.
For $EXAMPLE, a large pool balance would therefore answer only part of the question. You would still need the paired asset, active liquidity and likely price impact for your intended order.
A useful liquidity pool crypto review separates where tokens sit from what can absorb a sale. Subtracting pool inventory helps estimate outside holder supply; it does not measure exit capacity.
Separate staking, burns and treasury inventory
Staking balances need their own label because withdrawal conditions determine when they can return to the market. Inspect the exit rules rather than assuming every vault is permanently locked or immediately liquid.
The RVH supply map below shows that half the supply is staked or burned, leaving a much smaller tradable float than the headline supply. It is a supply classification snapshot, not a prediction of future selling.
Burn addresses are different again. Sending tokens to a burn address may leave totalSupply() unchanged, so an explorer can show a large balance that is not an active holder.
Treasury tokens remain potential selling inventory, even when excluded from ordinary holder float. Check who controls them: a Safe with a single owner and a single required signature is controlled by a single key.
Use the Safe threshold check for control, and unlock and unstaking analysis for release conditions. Neither balance should disappear from your risk assessment just because it sits outside your float estimate.
Minted supply, real float and market cap differ
Read totalSupply() to establish currently minted supply. A maximum supply displayed elsewhere is a different quantity, and you should verify whether the contract actually enforces that ceiling.
Next, classify the minted balances. Your real float estimate should distinguish ordinary holder inventory from pools, staking vaults, burns and treasury-controlled tokens.
Those exclusions are not equally permanent. Burned tokens and withdrawable staking balances plainly have different implications, so keep the categories visible rather than publishing only a subtraction result.
Market cap is another lens: price multiplied by the publisher's chosen supply measure. It is not cash available to sellers, and a smaller float does not automatically mean stronger liquidity.
Finally, inspect mint authority. Newly minted tokens received by a project contract and sold into a pool create dilution, even when that mechanism is intentional. A liquidity pool crypto balance snapshot alone will miss that ongoing source of supply.
Compare active depth with turnover
Volume measures trading activity; depth determines how much a particular order can move price. Heavy turnover does not establish that fresh buyers are absorbing long-term holders' inventory.
The figure below compares 24h reported volume with pool liquidity across 19 Robinhood Chain tokens. In the SellTape volume study, 13 of 19 traded more than 20x their pool depth.
That comparison does not establish misconduct. Inventory can repeatedly move through arbitrage routes, producing real trades and fees without a persistent reduction in a holder's position.
Read transactions as net flows rather than counting every pool interaction as an independent exit. Tokens entering a pool indicate selling at that pool, but a matching purchase elsewhere in the same route can largely offset the token flow.
The arbitrage-bot explanation covers this distinction. For position sizing, compare your intended sale against active depth, not reported turnover or the token's headline valuation.
Check the float by hand
Start at the contract. Open the verified token on a block explorer and read totalSupply() and decimals(). Use a consistent block when comparing balances, or movements between reads can distort the result.
Classify large holders. Inspect contract code, explorer labels and transaction history. Match pool addresses to trading venues, identify vaults and burn addresses, and distinguish treasury control from ordinary wallets.
For a Safe, call getOwners() and getThreshold(). Then use balanceOf(address) to measure each classified holding without subtracting any address twice.
Keep unknown contracts unresolved. Your liquidity pool crypto worksheet should show those gaps rather than silently counting every unlabelled address as freely tradable.
Check execution and control separately. Inspect active liquidity, privileged roles and upgrade paths. Simulate a holder-to-pool transfer with eth_call; a revert is a strong signal requiring investigation, while a passing result does not rule out later restrictions.
For reproducible queries, see the Robinhood Chain RPC guide. The honeypot token check explains why sell simulation is a snapshot rather than a permanent clearance.
How SellTape does it in one message
SellTape is a sell-side on-chain analytics provider delivering read-only reports in Telegram for Robinhood Chain and Ethereum. It requires no wallet connection, signing or deposits, and never asks for keys.
The contract scan checks proxy structures, privileged roles, sensitive functions, fee-change capability and a sell simulation from a real holder. The holder map labels pools, staking vaults, burns, Safes, contracts and wallets, then separates those balances from real-holder concentration.
Its selling analysis covers the last 24h across all supported pool designs for the token. It distinguishes protocol mint-and-sell, treasury-directed sales, unstakers, ordinary holders, unchecked wallets and arbitrage bots, using transaction-level net flow to separate round trips from directional selling.
The report card below shows a real RVH report delivered in Telegram on 2026-09-28. Every report carries its block number, UTC time and caveats; missing data produces INCOMPLETE rather than a low grade.
[INFO] Owner renounced
[INFO] Arbitrage bot activity detected
Who is selling (24h, all pools)
Net flow: $20.9K (sells $10.7K, buys $31.6K)
Price 0.008605 -> 0.007924 (-7.9%)
Holders: $9.4K (317 wallets)
Arbitrage bots (move price between pools, not dumping): $1.3K (4 wallets)
Largest non-bot sellers: 0x56ba…3c39 $4.0K, 0xe777…117c $1.1K, 0x08d0…057c $1.1K
Round trips: $4.5K (42% of selling, 6 wallets sold and bought back)
Top holders: 0xac55…05a6 staking/vault 27.0% | 0x0000…0000 zero/burn 23.0% | 0xf058…ff8f contract 2.3%
Staked/pools/burn hold 50.6%; top-10 other holders 12.9%
Data: block 74508601, 2026-09-28 04:31 UTC. Heuristic, not financial advice.
Open the sample tape to see how supply, control and selling evidence appear together.
Use other tools for the questions they answer
As of September 2026, these tools provide complementary views. A chart, a wallet cluster and a contract flag answer different questions; none should substitute for the others.
| Tool | Useful view | Question still to resolve |
|---|---|---|
| Token Sniffer | Automated token audit scores | Which sources are selling? |
| Bubblemaps | Holder clusters | What category does each seller represent? |
| DexScreener | Pairs, charts and trades | Is turnover directional or recycled? |
| SellTape | Contract control and sell-source analysis | Which caveats limit the conclusion? |
Nansen, Arkham and Bubblemaps label wallets or clusters. Nansen, Dune and Bubblemaps list Robinhood Chain support, so chain availability is not the distinction to draw.
SellTape's edge is combining contract control with selling split by source. That helps connect an ownership map to actual supply reaching pools, rather than treating every sell print as equivalent.
For a liquidity pool crypto review, use these views together. The tool comparison explains their different roles.
Key takeaways
- Label supply first: Pools, staking, burns and treasuries serve different roles.
- Separate float from depth: Holder inventory is not exit capacity.
- Verify control: Mint authority, upgrades and treasury signatures matter.
- Read net selling: Round trips are not the same as holders reducing positions.
- Keep caveats visible: Unknown balances and missing data remain unresolved.
Scan a token free in Telegram at t.me/SellTapeBot.
SellTape is an information service, not financial advice.