A token unlock is a scheduled release of tokens that were previously restricted, typically to teams, investors, foundations, or ecosystem programs. It is a supply event with a date, a recipient class, and a size. It is not automatically a dump. It is not automatically “priced in.” Your job is to read who gets coins, how they vest, and whether the venues can absorb that size without turning you into exit liquidity.
Show me the unlock table, not the roadmap. Roadmaps are stories about future usefulness. Unlocks are mechanics that hit circulating supply on a calendar. I get more excited by a boring linear vest that the market already learned to live with than by a cinematic cliff the night before a conference.
This guide is a read, not a trading system. You will still see “unlock tomorrow, short it” posts. You will have a way to check the event before you inherit someone else’s urgency.
Who this is for
People who trade or hold tokens with investor and team allocations. Ethereum users who already understand issuance on the base chain and want the same seriousness for alt unlock calendars. Anyone who has been trapped in a “bullish unlock” thread that never pasted the recipient list.
If you only hold Bitcoin, you can still use the skepticism. Bitcoin’s issuance is public and programmatic. Most alt unlocks are contractual. Contractual supply needs documents, not vibes. Pair that contrast with Ethereum history when someone pretends every token has the same issuance honesty as ETH.
Beginners often think the skill is finding the calendar first. More often the skill is refusing to treat a calendar screenshot as a thesis. Intermediate readers know the calendar and still skip liquidity. This is for both.
Prerequisites
- The public unlock dashboard at DefiLlama Unlocks. Use the live page. Do not trust a week-old crop from a group chat.
- EDGAR at sec.gov/edgar/search when the issuer is a public company and the “unlock” is actually a disclosed share or warrant event. Dashboards and 8-Ks are different animals. Do not mash them.
- The project’s own token docs or allocation page when DefiLlama is not enough. Dashboards summarize. They can lag. They can mis-label a category. Primary docs win arguments.
- Literacy on token unlock, liquidity, and market structure.
- A note with date, token, amount, percent of circulating, recipient class, vest type, and venues you would actually trade.
- Willingness to do nothing. Most unlocks are not your trade.
You do not need a paid emissions API. DefiLlama’s HTML page is enough to start. Paid tools can wait until the free table is a habit.
Steps
Use the full sequence when an unlock is being sold as destiny. Tiny ecosystem drips can be compressed. Cliffs that are large versus circulating supply cannot.
1. Find the event on a live table, then confirm the token
Open DefiLlama Unlocks. Search the token. Confirm you have the right project, not a ticker collision. Write the next event date in your note from the live page, not from memory. Calendars move. “Tomorrow” in a screenshot may already be last week.
If the dashboard and the project’s docs disagree, stop and resolve the conflict. Conflict is information. Averaging two calendars into false confidence is how people size a ghost event.
Ignore countdown bots that never link a source. A bot can be right. A bot is still not a source. Your standard is a URL you can reopen.
2. Split cliff from linear, and locked from circulating
A cliff is a chunk that becomes transferable on a date. Linear vesting drips over time. Those are different mechanical hits. A cliff into a thin book is a different animal than a daily drip the book has seen for months. Name the type in your note. If you cannot name it, you are reading a vibe calendar.
Then separate “unlocked” from “sold.” Unlocking means the restriction lifted. Selling is a choice, a mandate, or a market-maker program. Some recipients sell. Some stake. Some OTC. Some sit. The calendar does not tell you which. Anyone who tells you they know, without a wallet they can show, is guessing with confidence.
Circulating supply definitions are sloppy across sites. Fully diluted numbers are sloppier. Write which supply number you used and from where. If the unlock is 2% of circulating on one site and 0.2% on another, you do not have a size. You have a homework assignment.
3. Read who receives the coins
Team, early investors, foundation, ecosystem, advisors, and “community” are not the same seller set. Investor coins often have a financial return job. Team coins can be payroll and incentive. Foundation coins can be grants or a hidden market-maker budget. Community labels can be honest or decorative. Read the allocation names in the project docs, not the marketing synonyms in a thread.
Ask whether the recipient is a single wallet you can watch or a class of wallets. A class is harder to track and easier to mythologize. If the project publishes addresses, save them. If it does not, write “unverified recipients” in the note. That line should raise the evidence bar, not your certainty.
Governance tokens add a twist. An unlock can change voting power as well as float. If you care about a vote, the unlock is a political event too. If you only care about the book, keep the political essay out of the trade note. Mixing them is how people justify a bad scalp with a manifesto.
4. Compare unlock size to venue depth
This is the step people skip because math is less fun than lore. Estimate the dollar size of the unlock using a dated price from your snapshot, not a round number from memory. Then look at the books you would actually use: which venues, which pairs, what size takes the price 2% or 5% if someone sells into them. If you cannot get a depth read, you do not have an unlock thesis. You have a calendar invite.
A large unlock into deep BTC or ETH pairs is not the same as a large unlock into a token/USDT book that trades in fits. Stablecoin quote quality matters. If the exit is a thin alt book, the “dollar size” is a fantasy until someone eats the slippage.
Fees belong here. Show me the fee to move and sell, not the roadmap slide that promised utility the same week. If claiming, bridging, or dumping the unlocked pile costs more than the edge you imagined, the event is not your event. Mechanics first.
Market-maker and CEX inventory programs can sit next to unlocks and confuse the tape. A venue listing the token the same week as a cliff is not a coincidence you should ignore. Listing is a venue event. Unlock is a supply event. Ask which one the thread is actually selling. If it will not say, assume they want you to mix them until you click buy.
5. Look at the days around the date, not only the candle on it
Markets often trade the story early. Sometimes they trade it late. The unlock date is a timestamp, not a promise of a volume spike. Write what already happened in the prior sessions: did the book thin, did basis move, did a market maker tweet, did the project announce a lock extension. Extensions are events too. They change the calendar you thought you had.
After the date, check whether expected wallets moved. If they did not, the “sell the unlock” crowd just taught you something about this recipient class. If they did, compare size moved to size unlocked. Partial sells are common. Treating a 10% sell as a 100% thesis is how you invent a villain.
Do not upgrade a red candle on unlock day into proof of dumping if you never checked the wallets or the venues. Correlation with a date is a clue. It is not a court case.
6. Write a falsifiable line, then refuse the slogan
Template: Token. Date. Amount. Percent of circulating (source). Recipient class. Cliff or linear. Venue depth note. What would change my mind. What I will not do for lack of depth.
If the line will not fill, you are early or the data is junk. Both are reasons to stand down. Standing down is a position. It does not trend.
Pair this with how to follow crypto news without getting played when the unlock is being laundered through “partnership” threads the same week. Stacked stories are a classic way to hide a supply event under a narrative. Split them. Calendar in one bucket. Partnership claim in another. Liquidity in a third. Then see what is left.
Common mistakes
- Trading a screenshot calendar with no live URL.
- Equating unlocked with sold.
- Skipping recipient class because the dollar headline was large.
- Using fully diluted supply to make a cliff look small, or circulating supply from a random site to make it look huge.
- Ignoring venue depth and fees.
- Assuming the move must happen on the calendar day.
- Treating an unlock extension announcement as a free lunch without reading who still unlocks, and when.
Price can dump on an unlock day because the book was already garbage. Price can rise on an unlock day because the recipients did not sell, or because something else hit the tape. Do not let the candle grade your process. Grade the note.
Related reading
Keep the token-unlock definition open while you use DefiLlama so the word stays tighter than a countdown bot. For how thin books turn a supply event into a trap, stay with liquidity and market structure. Reopen those pages when a thread starts treating depth as optional.
When the token lives in an Ethereum-heavy world of fees and venue choice, Ethereum history is the longer backdrop. Issuance honesty on ETH does not transfer to every ERC-20 with a sleek unlock graphic. Shipped mechanics transfer. Graphics do not.
If you cannot name the recipient and the vest type, you are not reading an unlock. You are reading a marketing calendar. Close the thread. Open the table. Then decide whether this event is even yours.
A monthly calendar pass is enough for most books. Once a month, list the next four weeks of unlocks that are large versus circulating supply on names you actually hold or would trade. Ignore the rest on purpose. Attention is part of custody of your decision quality. A feed that shows every micro-unlock on earth is how people trade noise and call it process.