Fair token distribution is the claim that a token's supply reached its holders through a process nobody had privileged access to. It is not a percentage. Operationally it decomposes into four questions: who could participate, on what terms, at what price, and on what timetable. A table where the community bucket is the largest can still fail all four, which is why fairness is assessed on the process rather than on the split.
Any distribution mechanism that rewards a measurable behaviour gets farmed by whoever can produce that behaviour cheapest at scale. Fairness is not a property you set at launch. It is a property you defend against a counterparty who is paid to defeat it.
Fair is not a number, it is four questions
Access: could anyone participate, or did participation require an allowlist, an invitation, or a relationship. Terms: did everyone face the same price and the same lockup, or did earlier capital get both a discount and an earlier exit. Timing: how long sat between the insider entry and the public one. Deployability: does every bucket in the table have a named use and a named controller.
A distribution can be fair on access and unfair on terms, which is the most common shape by a distance. Everybody could buy, but not at the same price and not with the same lockup. Say which of the four you are claiming. A general claim of fairness that has not been decomposed is a marketing sentence and reads as one.
The mining archetype, and why it does not transfer
The archetype everyone reaches for is issuance through work. Bitcoin's entire supply enters through the block subsidy, which started at 50 bitcoin per block and halves at a fixed interval, with nothing minted outside that rule.2 There is no allocation table because there was no allocation.
It does not transfer to most modern launches for a structural reason. The qualifying work has to be genuinely costly and permissionlessly available at the same time. Where the qualifying behaviour is cheap to fake, issuance by behaviour becomes issuance to whoever automates the behaviour first, and the fairness claim inverts.
The airdrop archetype, and how it gets farmed
Airdrops moved the problem rather than solving it. The Arbitrum Foundation's published eligibility rules show what defending one actually involves: a wallet whose transactions all fell inside a 48 hour window lost a point, and any address identified as a sybil through the Hop Protocol bounty programme was disqualified outright.1
Two things are worth noticing about that. The rules are heuristics about behaviour rather than identity checks, so they trade false positives against false negatives with no clean answer available. And the Foundation published the rules without publishing a count of excluded addresses.1 Third-party analysts have produced estimates that disagree with each other by roughly half, which is a reason to reason about the mechanism rather than about anyone's score.
In our experience the defensible version is to make the qualifying behaviour expensive to fake before the snapshot, and to publish criteria in advance only when you can afford for them to be optimised against. Publishing after the fact protects the criteria and costs you the trust that transparency was supposed to buy. Both positions are defensible; drifting between them is not.
The label problem inside the table
The other half of fairness sits inside your own allocation table. An ecosystem or community bucket with no deployment plan and no named controller is treasury under a friendlier label, and any reader who recomputes insider control by looking through the labels will find it in minutes.
Not every distribution needs a giveaway to clear this bar. Sui launched its Mainnet with no token airdrop at all and a one year cliff during which initial investors could not transfer their stake, a cliff that ended in May 2024.3 That is a coherent position: lock the insiders first, distribute later, and do not manufacture a community allocation you have no plan to deploy.
How we test a table for fairness
Recompute the community share after removing every bucket without a named controller and a written deployment plan. Compare the effective sellable float at launch against the insider float at the first unlock. Then ask what a well funded farmer would have done with your published criteria.
If the answer to the third question is that they would have captured a meaningful share, the criteria were the design and the design was weak. Fairness surviving that test is worth claiming in writing. Fairness asserted from a pie chart is not, and the people reading your table professionally will run the test whether you did or not.
Common questions
What makes a token distribution fair?
Process, not proportions. Four things decide it: whether anyone could participate, whether everyone faced the same price and lockup, how long insiders were in before the public, and whether every bucket in the table has a named controller and a deployment plan. A community allocation that is the largest slice can still fail all four, which is why the split alone tells a reader very little.
Are airdrops a fair way to distribute tokens?
They are fair on access and vulnerable on execution. Any criterion based on observable behaviour can be produced at scale by someone paid to produce it, so the design work is anti-sybil rather than generosity. Arbitrum's published rules penalised wallets whose activity all sat inside a 48 hour window and disqualified addresses flagged through a bounty programme.1 Those are heuristics, and heuristics trade false positives against false negatives.
What percentage should go to the community?
No credible institutional benchmark exists for this, and we checked. Nobody publishes an averaged insider-versus-community split across a sample of launched tokens, so any round number presented as an industry standard is someone's assertion. The useful comparison is against the specific projects whose allocations are actually disclosed in primary documentation, read alongside their lockup terms rather than in isolation.
See Token Allocation and Vesting Design for how this applies in practice.
Sources
- Airdrop Eligibility and Distribution Specification
Arbitrum Foundation (docs.arbitrum.foundation), current
Publishes the anti-sybil rules used for the ARB airdrop, including the 48 hour transaction window penalty and disqualification of addresses identified through the Hop Protocol bounty programme. No aggregate count of excluded addresses is published. - Bitcoin Developer Reference: Block Chain, block subsidy and halving
bitcoin.org / Bitcoin Core developer documentation, current
Documents that new bitcoin enters supply only through the block subsidy, starting at 50 bitcoins per block and halving every 210,000 blocks. - Tokenomics on Sui
Sui Foundation / Mysten Labs (docs.sui.io), current
States the 10,000,000,000 SUI supply cap, the one year cliff blocking initial investors from transferring their stake, the cliff ending in May 2024, and that no token airdrop was run at Mainnet launch.
Last reviewed 2026-08
Know the terms but not sure how they apply to your project? That is what an engagement is for. We design, document, and stress-test the whole token economy inside the Tokenomics Data Room.
100+ projects advised. Complete tokenomics in 4 to 6 weeks.