Quick Answer: Public calendars identify a LayerZero ZRO vesting event around 20 November 2026, but their estimates differ because they may use different token-allocation versions and definitions of “unlocked” or “circulating.” LayerZero’s original 2024 plan assigned 322 million ZRO to strategic partners and 255 million to contributors; its later supply update describes repurchases and relocking that changed the earlier picture. An unlock makes tokens eligible under a schedule. It does not prove that the same number immediately reached an exchange or was sold.
As of 20 November 2026 UTC. This article reports the schedule and methodology available at the time checked. It does not claim a completed on-chain transfer unless a transaction and address are identified.
What was the original ZRO vesting plan?
LayerZero Foundation’s original ZRO announcement says total supply was fixed at one billion tokens. It allocated 38.3% to the community, 32.2% to strategic partners, 25.5% to core contributors, and 4% to tokens repurchased and pledged to the community. The partner and contributor allocations were subject to a three-year schedule with a one-year initial lock and monthly releases over the following two years.
That original plan is an essential primary source, but it is a starting version. A calendar that simply divides 322 million and 255 million by 24 months may produce a clean monthly figure. It can still be wrong for a later date if tokens were repurchased, reallocated or relocked. Readers should use the latest official disclosure as well as the original document.
The June 2026 LayerZero update says 514 million ZRO were unlocked at the time of that publication and 486 million still vested. It also describes 50 million tokens repurchased from strategic partners in September 2025 and relocked until the planned Zero mainnet launch. The post states that the strategic-partner allocation had become 312 million after the settlement of an earlier repurchased-token category. Those details mean the original category names and amounts cannot always be carried forward unchanged.
What does a 20 November unlock estimate actually count?
Different trackers publish different estimates for the same date. For example, CoinGecko’s ZRO page displayed a scheduled release near 23.28 million ZRO when checked, while Blockworks’ unlock calendar displayed a larger figure of roughly 25.71 million. These are third-party schedules, subject to their data definitions and update times. The difference should prompt a denominator and category audit, not a claim that one tracker caught a hidden sale.
Ask which categories the tracker includes. Does it count strategic partners, contributors and repurchased tokens separately? Does it treat relocked tokens as unavailable until a separate mainnet event? Does it count foundation inventory that is technically unlocked but not circulating in public markets? Does its percentage use the one-billion total supply, a circulating-supply estimate, or a free-float estimate? A single token count can correspond to quite different percentages depending on the denominator.
The percentage calculation itself is simple: a 23.28-million-token schedule is 2.328% of one billion total supply. It is not necessarily 2.328% of public float. If a tracker says the same event is about 5.8% of circulation, it is implicitly using a smaller circulating denominator. Both statements can be arithmetically consistent while answering different questions.
Why is an unlock not the same as selling pressure?
Vesting restrictions and actual market behavior are different stages. A scheduled unlock may remove a contractual restriction, but the holder may keep the tokens, delegate them, transfer to custody, provide liquidity, or sell some or all. Some tokens may be released from a contract but already included in a tracker’s “unlocked” supply. Others may move between addresses without entering public exchange books.
To test whether supply became market sell pressure, an analyst needs transaction-level evidence and an attribution method. Identify the vesting contract, beneficiary addresses, release transactions and subsequent transfers. Then distinguish a transfer to another self-controlled wallet from an exchange deposit. Even an exchange deposit is only a potential precursor to a sale, not proof that an order executed. Address labels can be incomplete, and an over-the-counter transfer might not be visible as a public exchange order.
Price can also react before an unlock. Traders can position in anticipation of a scheduled event, and macro news, market-wide risk or unrelated project developments can move ZRO at the same time. If price declines after the date, timing alone does not establish the unlock as the cause. A causal claim would need evidence about realized flows, market depth and competing explanations.
How can readers compare two calendars responsibly?
Start with the fixed supply and category definitions in the original Foundation post. Then read the later LayerZero update for revisions. For each third-party calendar, save the check time, listed token count, beneficiary categories, dollar conversion price and percentage denominator. Do not compare two dollar values from different days without first comparing the token counts.
| Field | Why it changes the headline |
|---|---|
| Tokens scheduled | The estimate can include or exclude relocked allocations. |
| Date and time zone | A local calendar date can straddle two UTC dates. |
| Beneficiary category | Partner, contributor, treasury and community releases have different holding incentives. |
| Percentage denominator | Total supply, unlocked supply and circulating supply are distinct. |
| Dollar value | It changes as the token price changes, even if the token count does not. |
| On-chain confirmation | A schedule is a forecast; a transaction confirms a transfer or contract release. |
Verify the available market: Open Phemex Markets and search the exact ZRO pair before making a product-specific claim. The older Phemex ZRO analysis discusses prior spot and futures status, but current availability and order-book depth must come from the live interface.
What would a careful event analysis monitor next?
Monitor the release transaction, whether beneficiary addresses receive tokens, and whether those addresses transfer to venues or other wallets. Record exchange order-book depth on both sides, not merely 24-hour volume. Compare ZRO’s move with broad crypto-market indices and similarly sized tokens over the same interval. Check whether LayerZero publishes an updated allocation statement or clarifies how the repurchased tokens are treated. Those steps can narrow uncertainty; they do not reveal every holder’s intent.
If reporting a percentage price move, specify the source, timestamp and quote currency. A thin market can show a dramatic last trade without enough depth for a larger holder to sell at that number. Conversely, an unlock can pass with little immediate observable price effect. Neither outcome validates a simple rule that unlocks always cause losses.
FAQ
How many ZRO unlock on 20 November?
Public third-party calendars checked for this draft differed, including estimates near 23.28 million and 25.71 million ZRO. The primary LayerZero posts explain allocations and revisions but do not establish one verified on-chain amount for the moment of this article. Confirm the vesting transaction and the tracker’s methodology before publishing a single definitive count.
Does “unlocked” mean “circulating”?
No. Tokens can be unrestricted yet held in a treasury, by a long-term holder or in a wallet without a liquid market sale.
Does an unlock guarantee a ZRO price decline?
No. The price response depends on expected supply, actual transfers, holder decisions, market depth and other news. The schedule alone does not prove causation.
Can a dollar unlock amount change without token movements?
Yes. A calendar often multiplies scheduled tokens by a current token price. That dollar estimate changes when the price changes.






