Read token unlocks before supply reaches a pool
Quick answer: Token unlocks make previously restricted supply available to recipients, but they do not automatically create selling. Track the release schedule, follow beneficiary wallets, and separate actual pool sales from unstaking transfers, treasury movements and arbitrage activity.
Your job is to distinguish available supply from executed selling. A vesting release changes what a recipient can sell; a swap shows what they actually sold.
The same distinction applies to staking. Tokens sitting in a vault have not disappeared, and their return to a wallet is not yet evidence of an exit through a pool.
A useful supply read therefore needs both a calendar and transaction tracing. The calendar identifies possible release windows, while the trace establishes where tokens went and whether someone reduced their holdings.
Why token unlocks belong on your calendar
Vesting contracts release tokens according to rules you can inspect. A cliff makes a block of supply claimable at a particular point, while linear vesting makes supply available progressively.
Claimable does not always mean transferred. Some contracts require the beneficiary to claim, so distinguish the scheduled release from the actual movement on-chain.
These are different states, not interchangeable labels.
| Supply event | What changes | What confirms selling |
|---|---|---|
| Vesting release | Recipient can access tokens | A traced swap into a pool |
| Unstaking | Tokens leave a staking position | Withdrawn tokens are sold |
| Mint-and-sell | New supply is created | Newly minted tokens reach a swap |
For token unlocks, record the contract, beneficiary and release rules rather than relying only on an announcement. Then watch what the recipient does: holding, restaking and selling produce very different outcomes.
Unstaking returns supply to the market
Staking is a delay in availability, not a burn. A vault can hold a large share of supply while the freely trading portion remains comparatively small.
When tokens leave that vault, potential selling capacity expands. Actual unstaking sell pressure requires the next link: withdrawn tokens being sold into a pool.
That sale can happen in the withdrawal flow or later. A later sale requires more tracing, especially when the recipient already held tokens or moves funds through another address.
The supply lifecycle figure shows how supply reaches the market. Unlocks and unstakes show up as transfers you can watch before they hit a pool, although withdrawal and sale can also execute together.
For $EXAMPLE, a vault withdrawal followed by a swap is stronger evidence than a falling vault balance alone. Read the destination and transaction context before assigning a selling label.
Our guide to real float and liquidity pools explains why staking, pool, burn and treasury balances need separate treatment when assessing available supply.
Mint-and-sell adds a different supply source
An unlock typically releases existing tokens. Protocol mint-and-sell creates tokens and then converts them into the pool’s quote asset.
The trace starts with a mint, commonly represented by a transfer from the zero address. A project contract receives those tokens and sells them, with proceeds often going to the treasury.
That is dilution even when the mechanism is disclosed and operating as designed. It is not an ordinary holder reducing an existing position, and it may operate without a vesting date.
Read totalSupply() for current minted supply. A maximum supply displayed elsewhere is a different concept, and a difference between the figures does not by itself prove that discretionary minting is possible.
Check who can mint, whether permissions can change, and whether the contract is upgradeable. Also distinguish treasury selling of existing inventory from selling newly created tokens: the destination may match while the supply effect differs.
Check the supply trail by hand
Start with the token’s block explorer page and verified contract code where available. Keep the block reference attached to your notes so reads and transfers describe a consistent state.
- Read supply and schedules. Query
totalSupply(), account for token decimals, and inspect vesting release rules, beneficiaries and staking withdrawal conditions. - Label major addresses. Separate pools, staking vaults, burn addresses, treasury contracts and wallets. Follow releases to recipients, then inspect their swaps rather than treating every pool transfer as selling.
- Read control. Check
owner()where present and other privileged roles. For a Safe, usegetOwners()andgetThreshold(); a single-owner, single-signature setup still depends on a single key, as our Safe control guide explains. - Test sellability. An
eth_callsimulating a real holder’s transfer to the pool can reveal restrictions. A revert is a strong warning requiring interpretation; a pass does not rule out later fee changes or upgrades.
The honeypot check guide covers simulation limits. For repeated queries, use suitable infrastructure: the public endpoint discussed in our Robinhood Chain RPC notes is rate-limited and not intended for production.
Read net selling, not isolated transfer arrows
A transfer into a pool needs transaction context. Liquidity additions are not ordinary sells, and routed trades can move the same token through several pools.
SellTape measures net token flow across pools within each transaction. A route that buys the token in a pool and sells it in another can largely cancel out rather than represent a holder exiting.
Arbitrage bots exploit price differences between pools and typically retain little inventory. Their activity should not be read as existing holders dumping; our arbitrage bot analysis explains the distinction.
The composition figure shows where the selling came from across the 19 most active Robinhood Chain tokens, 24 hours to 2026-09-27. 11,999 liquidity add/remove transactions excluded.
That source breakdown is the useful companion to token unlocks. A busy tape can reflect arbitrage rather than released supply being sold, while quieter trading can still contain persistent protocol or unstaker selling.
How SellTape does it in one message
Send a token address to SellTape in Telegram. It provides read-only on-chain analysis on Robinhood Chain and Ethereum, with no wallet connection, signing or deposits, and it never asks for keys.
The contract scan reads proxies, privileged roles and control structures. It checks relevant bytecode functions, tests whether the owner can change fees, and simulates a sell from a real holder.
The holder map separates pools, staking vaults, burns, Safes, contracts and wallets. It shows staking and pool balances against real float and examines concentration among leading real holders.
The sell-side analysis then traces daily selling across all supported pool types for the token. It separates protocol mint-and-sell, treasury-directed selling, unstakers, ordinary holders, wallets not checked for bot behaviour and arbitrage bots, using transaction-level netting to avoid mistaking round trips for holder exits.
Inspect the sample tape for the report format. Every report includes its block reference, UTC time and caveats; missing data produces INCOMPLETE, not a low-risk result.
Turn the evidence into a working calendar
For token unlocks, keep the next release window alongside its contract and beneficiary. For linear vesting, track the release rate and claim behaviour rather than looking only for a dramatic cliff.
For staking, record withdrawal conditions and watch outgoing transfers. For mintable supply, record the privileged role and look for mint-to-contract-to-pool sequences.
Then compare scheduled availability with observed sales. An approaching release and current arbitrage-heavy activity describe different risks; neither cancels the other.
Update labels when contract control changes or a treasury begins using a new address. Old labels can make a clean-looking trace misleading even when the underlying transfers are accurate.
Most importantly, preserve uncertainty. A transfer establishes movement, a schedule establishes eligibility, and a traced swap establishes selling; none alone tells you the recipient’s next decision.
Key takeaways
- Availability is not selling: token unlocks need beneficiary follow-through.
- Unstaking is reversible supply lockup: trace withdrawals to actual swaps.
- Mint-and-sell is dilution: separate it from treasury inventory sales.
- Net transaction flow matters: liquidity movements and arbitrage can distort raw transfer counts.
- Keep evidence current: track contract control, block references and missing data.
Scan a token free in Telegram at t.me/SellTapeBot.
SellTape is an information service, not financial advice.