Early-Claim Penalty
An early-claim penalty lets a beneficiary take tokens ahead of the schedule at the cost of forfeiting part of the claim, usually on a forfeiture rate that declines as the wait lengthens. 0G's AI Alignment Node allocation charged 60% at TGE, stepping down to 50% at day 90, 35% at day 180, 20% at day 270 and nothing from day 365. Because each holder chooses, released supply becomes a range rather than a figure.
TradFi parallel: Like breaking a fixed-term deposit before maturity and paying a surrender charge that shrinks the closer you get to the maturity date.
Key Takeaways
- 01An early-claim penalty prices impatience instead of forbidding it: the beneficiary may claim ahead of schedule and forfeits a declining share of the claim for doing so
- 020G's AI Alignment Node tiers ran 60% at TGE, 50% from day 90, 35% from day 180, 20% from day 270, and 0% from day 365
- 03Released supply becomes a band, not a number. Assuming maximum penalties and immediate claiming, Tokenomist put 0G's real float at 16.3% to 19.3% of total supply at launch
- 04Penalties usually cover only part of an allocation. Of 0G's node allocation, 10% was penalty-free at TGE, 23% was penalty-subject, and the remaining 67% vested daily over 36 months with none
- 05Steepness signals intent: Lybra Finance charged 95% for vesting esLBR four days after receipt, a deterrent rather than a genuine option, stated as a way to reduce selling pressure
- 06Tier boundaries are behavioural focal points, so claim activity concentrates just after a rate steps down rather than spreading evenly across the window
How It Works
A penalty schedule replaces a hard lock with a price. Rather than forbidding a claim before a date, the contract permits it and keeps a share of the tokens. 0G applied this to the 150 million tokens in its AI Alignment Node allocation, which is 15% of supply, under a release schedule chosen by community vote in the project's Discord. Of that allocation, 33% was claimable at TGE, split between a penalty-free 10% available immediately and a penalty-subject 23%, with the remaining 67% vesting daily over 36 months with no penalty applied. The penalty tiers governed only the middle piece: 60% forfeited for a claim at TGE, 50% from day 90, 35% from day 180, 20% from day 270, and 0% from day 365.
The consequence for supply analysis is that there is no single released-supply number to report. Tokenomist's read of 0G at launch was that assuming maximum penalties, meaning every eligible holder claims immediately, real float ranges between 16.3% and 19.3% of total supply. That band is the honest output. The upper end assumes maximum patience, the lower end maximum impatience, and the actual figure is a behavioural result that only resolves as claims land on-chain. Any model that collapses that band to a point estimate is inventing precision the schedule does not contain.
How steep the curve is tells you what behaviour the designer expected. 0G's tiers step down four times across the first year, so the charge is steep at TGE and falls in stages, and the cost of not waiting becomes survivable well before the schedule runs out. Lybra Finance's V2 esLBR design sits at the other extreme: a user who chooses to vest tokens 4 days after receiving them incurs a 95% penalty, receiving only 5% of the LBR they were otherwise due. Lybra stated the purpose plainly, as a mechanism to reduce selling pressure on LBR. A charge that severe is not really an option being offered, it is a deterrent priced so that only forced sellers take it.
Reading a penalty schedule in practice comes down to three things. Locate the tier boundaries, because claiming behaviour tends to cluster just after them: 0G's day 90, day 180, day 270 and day 365 are the dates where the marginal cost of claiming drops. Check what happens to forfeited tokens, which is a per-protocol design choice rather than a convention, and do not assume they are burned unless the protocol says so. And separate the schedule from the outcome by watching claim transactions as they execute, since the whole point of a penalty mechanism is that the released figure is decided by claimants, not by the calendar.
Real World Examples
0G: A Five-Step Penalty Ladder
View →0G's node rewards were withdrawable under a community-voted release schedule whose forfeiture rate steps down four times: 60% for a claim at TGE, 50% from day 90, 35% from day 180, 20% from day 270, and 0% from day 365. The design applies to the 150 million tokens in the AI Alignment Node allocation, 15% of supply, on an infinite-max-supply token that launched with 1 billion tokens.
0G: Float as a Range, 16.3% to 19.3%
View →Because the penalty makes the claim optional, Tokenomist reported 0G's launch float as a band rather than a figure: assuming maximum penalties, meaning immediate claiming by everyone eligible, real float ranges between 16.3% and 19.3% of total supply. The project's own summary described the penalty-based vesting as what reduces initial float to that range.
0G: Only Part of the Allocation Is Penalised
View →The node allocation split into a TGE portion and a vesting portion. Within it, 10% was penalty-free and claimable immediately, 23% was penalty-subject, and the remaining 67% unlocked daily over a 36 month linear schedule with no penalties applied. Applying the headline penalty rate to the whole allocation overstates the deterrent by a wide margin.
Lybra Finance: 95% Forfeiture Four Days In
View →Lybra's V2 upgrade let holders vest esLBR early instead of waiting out the unstaking period, which V2 lengthened from 30 days to 90. A user vesting 4 days after receiving the tokens incurs a 95% penalty and receives only 5% of the LBR otherwise due. The protocol described the mechanism as aimed at reducing selling pressure on LBR.
Frequently Asked Questions
How do I model float when an early-claim penalty applies?
Carry a range and label the assumption behind each end. Tokenomist's 0G read did exactly this: assuming maximum penalties and immediate claiming, real float ranges between 16.3% and 19.3% of total supply at launch. The lower bound assumes claimants wait out the penalty, the upper assumes they do not. Narrow the band with observed claim transactions rather than by picking a mid-point.
Where do the forfeited tokens go?
That depends entirely on the protocol, and it is worth verifying rather than assuming. Some designs burn the forfeited share, some return it to a treasury or redistribute it to holders who waited, and each choice has a different effect on max supply and on the incentives of everyone still in the schedule. Read the specific proposal or contract before treating a penalty as a burn.
Is an early-claim penalty better for holders than a hard cliff?
It is a different trade, not a strictly better one. A hard cliff gives a certain date and an uncertain amount of pent-up pressure at that date. A penalty gives an uncertain date and a smoother distribution, since claims trickle out across the window at a declining cost. The penalty design tends to reduce single-day concentration while making the forward supply curve harder to pin down.
Why do claims cluster at specific dates under a penalty schedule?
Because the forfeiture rate steps rather than glides. With 0G's structure, a claim on day 179 costs 50% and a claim on day 181 costs 35%, so there is no reason to claim just before a boundary. Expect activity to bunch immediately after each step-down, with day 365 the largest focal point since the penalty falls to zero there.
Related Terms
released supplyfloat percentageassumption and precisionescrowed tokenclaim statuscliff unlocknode sale allocation
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