Community Allocation: Who Gets Tokens and Why

Almost every token supply includes a slice labelled "community". It might be 20 percent or 60 percent, and it often looks generous on a pie chart. What matters more is how that slice is actually distributed, to whom, when and under what rules. A vague community allocation invites suspicion. A clear one becomes one of the strongest signals that a project intends to share ownership.

Break the community allocation into parts

"Community" can mean many things. Split it into specific pools:

Pool	Purpose
Retroactive airdrop	Reward early users and supporters
Ongoing usage rewards	Encourage continued product use
Contributor rewards	Pay people who build, translate, moderate and create
Ecosystem grants	Fund projects building on or around the protocol
Liquidity incentives	Support trading depth in early stages
Community treasury	Reserve for future decisions by governance

Publishing these sub-allocations with percentages makes the plan concrete.

Define goals for each pool

Each pool should have a clear goal:

• Airdrops might aim to reward genuine early users and decentralise ownership
• Usage rewards might aim to bootstrap activity until organic demand grows
• Grants might aim to expand integrations and tools
• Treasury funds might aim to give future holders flexibility

Goals guide design decisions, such as eligibility rules and vesting.

Set eligibility and distribution rules

For each pool, publish:

1. Who qualifies and how eligibility is measured
2. How amounts are calculated
3. When distributions happen
4. Whether tokens vest or unlock immediately
5. Who decides, whether the team, a committee or governance

Rules decided and published in advance feel fairer than rules revealed after distribution.

Vesting for community pools

Not every community distribution needs vesting, but large rewards often benefit from it. Vesting for contributor rewards and grants encourages ongoing involvement. Airdrops frequently unlock immediately to keep things simple, although partial vesting can reduce immediate selling.

Liquidity incentives usually decline over time, with emissions reducing as organic liquidity grows.

Avoid hidden insider allocations

Community pools sometimes become a place to hide insider benefits. Examples include team-controlled wallets receiving large "ecosystem" grants, advisors receiving community rewards or airdrops weighted toward insiders' wallets.

Holders notice these patterns on-chain. To avoid them:

• Keep team and advisor allocations separate and clearly labelled
• Publish grant recipients and amounts
• Exclude team wallets from airdrops or disclose participation
• Use multisigs with named signers for community treasury funds

Report distributions publicly

Transparency sustains trust:

• Publish the addresses holding each community pool
• Report distributions on a regular schedule
• List grant recipients and deliverables
• Show remaining balances in each pool
• Explain any changes to allocation plans

A public dashboard or a quarterly report works well.

Plan for changes

Plans change as projects learn. If community allocations need adjusting, involve holders through discussion and, where appropriate, governance votes. Explain the reasons and effects clearly. Quiet reallocation damages credibility far more than an openly debated change.

Communicate what community ownership means

Holding tokens from a community allocation may come with governance rights, access or simply ownership of the asset. Explain what holders can and cannot expect, without implying financial returns.

Make the allocation easy to verify

Community allocations are only as trustworthy as the information around them. Keep token documentation, treasury addresses and official links consistent across your website, docs and profiles such as a Proud Globe pin, so community members can check the numbers without relying on screenshots.