A token allocation is not a promise
A token allocation chart is read as a map of intent. Each slice carries a name, the names describe who the supply is meant to reach, and a wedge labelled for users looks like the portion of the network set aside for the people who use it. Framed that way, the chart is a schedule of commitments.
Framed correctly, it is an internal filing system. The categories are written by the issuer, held by the issuer and revised by the issuer, and a single governance vote is enough to move a balance out of a category bearing your name into one bearing somebody else’s.
An allocation is a budget line, not an entitlement
The proposal prompting this creates a new allocation category and moves an unspent balance into it. Nothing is minted and no token changes hands on approval. What changes is the wording in the allocation documentation and the matching line in the public token accounting.
It is filed, without apparent irony, under the proposal type the forum keeps for rights protections. The classification is worth pausing on, because it raises the question of whose rights were ever at stake in a category nobody could claim against.
The boundary the proposal draws answers that. Tokens already handed out in the five completed airdrops are untouched, and not out of generosity: they are gone. A distributed token sits in somebody else’s wallet, beyond the reach of any later vote, while the unspent remainder never left the issuer at all.
Most of the pool never reached a user
Across five airdrops the network distributed roughly two hundred and sixty-nine million tokens. The balance now moving into the growth fund is about five hundred and forty-seven million.
Set against each other, those two figures say something the proposal never assembles. The part that reached users is the smaller one, roughly a third of everything ever booked to the category, against about two thirds now heading somewhere else.
The reasoning offered for the change is not unreasonable on its face. The issuer says this is not necessarily a permanent verdict on airdrops as a mechanism, only that they no longer fit the growth it is pursuing.
That ratio was legible long before any vote, to anyone who compared what the category held against what it had paid out. The gap between the two sat in public accounting the entire time.
Control is what makes an allocation revocable
The distinction doing the work here is not in the proposal, because the proposal has no reason to state it. An allocation is revocable exactly when the tokens are still held by whoever wrote the label, and irrevocable exactly when they are not.
Consider what would have had to be true for this to go differently. Had the tokens sat in a vesting contract with named beneficiaries and a schedule the issuer could not alter, no vote would have reached them. Had they been handed out, they would have been beyond recall in the same way the completed airdrops are. What made this pool movable is that it was neither: a balance under the issuer’s own control, tied to its purpose by documentation rather than by code.
So the general rule survives the particular case. A slice on an allocation chart tells you what an issuer presently intends to do with tokens it still controls, and intention is not a constraint. The chart has no way to show you which categories could be renamed tomorrow and which could not.
The governance rhythm underneath makes the same point without meaning to. Deployment from the new fund follows the practices already in place and is accounted for to the collective once a year, which is an oversight cadence rather than a distribution schedule.
The practical version
The practical checks are unglamorous. When an allocation chart is put in front of you, ask which slices name tokens the issuer still holds, because those are precisely the ones a vote can rename. Read the supply schedule for the portion already committed by code, and treat the remainder as a statement of present intent. Ask who is able to move a category at all, which is the same question as naming the counterparty. And treat an unspent allocation as supply that has not yet chosen a destination, whatever name is attached to it.
None of this makes the change improper, and putting idle tokens toward something the network is actually doing is a defensible use of them. What it settles is what the original label was ever worth: a description of a plan, and not a claim anybody held.