KPI-Gated Unlock
A release conditioned on a published, measurable performance threshold rather than a calendar date. MegaETH put 53.3% of total supply behind KPIs and gated its own TGE the same way, holding it until seven days after a named milestone was hit. Backpack applied the model to the 75% of supply not distributed at launch.
TradFi parallel: An earnout in an acquisition, or a performance-vesting equity grant. The shares are allocated and the recipient is named, but nothing is delivered until a stated metric clears a bar, so the delivery schedule follows the business rather than the calendar.
Key Takeaways
- 01A KPI-gated unlock conditions a release on a published, measurable threshold instead of a date, and can gate the TGE itself rather than just post-launch tranches
- 02MegaETH held its TGE until seven days after one of three named milestones was met, and placed 53.3% of total supply behind KPIs across ecosystem growth, L2 decentralization, performance and Ethereum decentralization
- 03Backpack distributed 25% of supply at TGE entirely to points holders and Mad Lads NFT holders, leaving the remaining 75% on a growth-triggered unlock model tied to predefined milestones
- 04The stated purpose is to address the low float and high FDV pattern by tying issuance to demonstrated adoption rather than a fundraising timeline
- 05Size is known, timing is not, which puts a KPI-gated tranche closer to TBD locked supply than to a dated vesting schedule for projection purposes
- 06The trigger is observable but usually self-scored: published designs name the thresholds without naming an independent verifier
How It Works
A KPI-gated unlock replaces the date in a vesting schedule with a condition. The tokens are allocated, the size of the tranche is known, and the criteria are published, but the release happens only when the protocol demonstrably hits the threshold. MegaETH, a real-time Ethereum Layer 2, applied it to the launch itself: $MEGA would only hold its TGE seven days after at least one of three milestones was achieved, namely USDM circulating supply reaching a 30-day time-weighted average of $500M, at least ten live Mega Mafia applications each carrying more than 100,000 transactions over 30 days, or three applications generating over $50K in daily fees for 30 consecutive days. The Mega Mafia milestone cleared on 23 April 2026, which started the seven-day clock and set the TGE for April 30, 2026.
The scope can be much larger than the launch date. 53.3% of MegaETH's total supply is KPI-gated, entering circulation only as the protocol achieves milestones across four dimensions: ecosystem growth, L2 decentralization, performance improvements, and contributions to broader Ethereum decentralization. Backpack, an exchange and wallet, used the same logic with different wording: 1 billion total supply, 250 million (25%) circulating at TGE, split 24% to points holders and 1% to Mad Lads NFT holders, which makes the entire initial float community-facing with no insider tranche at launch, and the remaining 75% following what it called a growth-triggered unlock model tied to predefined performance milestones. The stated motivation is not subtle. MegaETH's design is explicitly aimed at the chronic low float and high FDV dynamic that has defined recent launches, and its own ICO round, which targeted $50M and attracted over $1.39B in capital commitments, is a fair illustration of the demand pressure that produces those launches.
For forward supply modelling, a KPI gate removes the single input unlock analysis depends on. Linear and cliff schedules can be extrapolated because the dates are written down; a KPI-gated tranche has a known size and unknown timing, which places it closer to TBD locked supply than to a vesting schedule, even though the disclosure quality is much better. The upside is that the trigger is observable: a reader tracking USDM's 30-day time-weighted supply, or a daily fee run rate against a stated threshold, has a live read on how close a tranche is to releasing, which no calendar can offer. The risk sits with whoever scores the metric. Published announcements of these designs state the thresholds but not an independent verification process, so treat the issuer as the scorekeeper unless it says otherwise, and note that a threshold can be set close to where the project already stands.
Read the gate alongside everything else in the structure, because it is a timing mechanism and nothing more. It does not shrink an allocation, it does not change who holds it, and it does not commit the project to any particular pace: MegaETH's gating KPI cleared before launch rather than delaying it. What it does change is the shape of the risk. Instead of a dated overhang the market can position against, a KPI-gated tranche is a conditional overhang, and the design's argument is that it arrives when the protocol is performing, which is also when demand is most likely to absorb it. That is the claim rather than a measured result, and a gate that cleared a week before the token existed is the first evidence that the coupling can be loose. It is also worth testing against the size of the gated block: on MegaETH's structure, more than half of total supply sits behind it.
Real World Examples
MegaETH (MEGA): a TGE with a KPI clock instead of a launch date
View →Rather than launching on a set date, MegaETH announced $MEGA would TGE seven days after at least one milestone was achieved: USDM circulating supply at a 30-day time-weighted average of $500M, at least ten live Mega Mafia applications each with more than 100,000 transactions over 30 days, or three applications generating over $50K in daily fees for 30 consecutive days. The Mega Mafia milestone cleared on 23 April 2026, setting the TGE for April 30, 2026.
MegaETH (MEGA): 53.3% of total supply behind milestones
View →More than half of total supply enters circulation only as the protocol achieves milestones across four dimensions: ecosystem growth, L2 decentralization, performance improvements, and contributions to broader Ethereum decentralization. Tokenomist described it as one of the more structurally distinct release designs in recent memory, and explicitly aimed at the low float and high FDV problem.
Backpack: 25% community float at TGE, 75% growth-triggered
View →Backpack's framework put 250 million of 1 billion total supply into circulation at TGE, 24% to points holders and 1% to Mad Lads NFT holders, so the entire initial float is community-facing with no insider tranche at launch. The remaining 75% follows a growth-triggered unlock model tied to predefined performance milestones, mirroring MegaETH's approach.
Frequently Asked Questions
How is a KPI-gated unlock different from TBD locked supply?
Both are undated, which is why they behave alike in a forward projection. The difference is disclosure. TBD locked tokens sit in a treasury or reserve awaiting a governance vote or an operational decision, often with no stated criteria at all. A KPI-gated tranche publishes the thresholds up front, in quantitative terms a reader can track independently, such as a 30-day time-weighted stablecoin supply or a daily fee level sustained for 30 days. The timing is still unknown, but the condition is legible.
Does a KPI gate reduce supply pressure?
It reschedules it rather than reducing it. The allocation size is unchanged; what changes is that release coincides with demonstrated traction rather than a date set during fundraising. The argument is that a market absorbing supply while adoption metrics are clearing thresholds is in better shape than one absorbing supply on a calendar it cannot influence. The counterweight is size: with 53.3% of MegaETH's total supply gated this way, the conditional overhang is larger than most dated schedules.
Who verifies that a KPI has been met?
Usually the project. The published designs specify measurable thresholds but do not name an independent verifier or an on-chain oracle for the determination, so the issuer is effectively the scorekeeper. That is worth weighing against how the threshold is set: MegaETH's gating KPI was confirmed on 23 April 2026, a week before the 30 April TGE, so the gate cleared rather than deferred. Thresholds set near a project's current position gate very little.
How do I track a KPI-gated tranche?
Track the metric, not the calendar. Note the size of the gated allocation from the Allocation Screener, record the published thresholds, and monitor the underlying figure directly, whether that is stablecoin supply, application count, or daily fee revenue. A KPI-gated tranche will not appear on the unlock calendar with a date until the condition is met and the release becomes scheduled, so it must be carried as a separate, conditional line in any forward supply model.
Related Terms
tbd locked supplytreasury vestingtoken generation eventvesting schedulelow float high fdvwhitepaper schedule
Track on Tokenomist
Supply-side analysis for educational purposes. Not financial advice. Verify assumption and precision labels on the relevant token page.
Tokenomist.ai provides a complete solution for supply-side tokenomics data. Analyze future token emissions, track vesting schedules, and compare standardized tokenomics and allocation across projects to gain actionable insights