A good token allocation splits total supply across five buckets: team and advisors, investors, community and ecosystem, treasury, and launch liquidity. There is no universal percentage that works. What works is an allocation you can defend line by line: each bucket has a stated purpose, a vesting schedule that matches that purpose, and a size that does not leave too little circulating supply at launch or too much in the hands of insiders. This guide gives you a framework for deciding the split, the questions exchanges and investors will ask about it, and the red flags that make a distribution table look weak.
Any percentages below are illustrative, not industry standards. Projects differ in stage, funding path and utility, and the right split for a protocol that raised two rounds is not the right split for a community-first launch.
What a Token Allocation Table Is Actually For
Founders often treat the allocation chart as a marketing graphic. In practice it is read as a risk document. Three audiences read it closely:
- Investors want to see that the team is locked in and that the insider share is not so large that unlocks will flood the market.
- Exchanges check how much supply is liquid at listing and who controls it, because concentrated or fully unlocked supply is a listing risk.
- Your community uses it to judge whether the project is fair. A table that gives most of the supply to a few wallets reads as extractive, whatever the roadmap says.
The allocation is also the starting point for your float, your unlock schedule and your market maker's inventory. A mistake here propagates into everything covered in our tokenomics design guide.
The Five Buckets and What Each One Is For
Team and advisors
This bucket compensates the people building the project. Its job is retention and alignment, so its structure matters more than its size. A cliff followed by linear vesting is the common pattern, with a total duration long enough that the team is still building when the last tokens unlock. Advisors typically sit on shorter schedules than founders, and their share should be modest and tied to actual contribution.
Investors
This covers seed, private and strategic rounds. Size follows from how much you raised and at what valuation: raising more at a lower valuation means selling a larger share of supply. Every round needs its own price, vesting and cliff terms recorded, because your unlock calendar is built from them. If your fundraising structure is still open, SAFT versus token warrant affects when investors actually receive tokens.
Community and ecosystem
This is the largest conceptual bucket and the most commonly mismanaged. It usually funds airdrops, rewards, grants, liquidity incentives, partnerships and future contributors. The mistake is to label a large pool "community" without a plan for how it is released. A big, vaguely defined community bucket is both a fairness claim and a future sell-pressure overhang. Define sub-allocations and an emission schedule so the bucket does not look like a second treasury.
Treasury and foundation
This funds operations, development and runway after the raise is spent, and it often backs buybacks or strategic reserves. It should have clear governance: who can move it, under what limits and with what reporting. Where it sits legally is its own decision, which we compare in our guide to token foundation jurisdictions. For policy options, see treasury management for crypto projects.
Launch liquidity and market making
This bucket is small in percentage terms but critical at launch. It funds market maker inventory, DEX pool seeding and exchange-specific needs. If you leave it out of the table, you will end up lending tokens from the treasury or team allocation on short notice, which is both messy and visible on-chain. Sizing it is covered in how much liquidity a token needs at launch.
A Decision Framework for the Split
Rather than start from a template, work through these four decisions in order.
Step 1: Decide your target circulating supply at TGE
Pick the float you want on day one first, then work backwards. A low float can make a token easy to move and prone to sharp swings; a high float demands more liquidity to absorb it. Low float versus high float launches lays out the trade-off. Your float is the sum of everything unlocked at TGE across buckets, so every bucket's TGE unlock should be a deliberate number.
Step 2: Cap the insider share
Add team, advisors and investors together. This is the share of supply controlled by people with a cost basis far below the market price and a reason to sell. There is no magic threshold, but a combined insider share that exceeds what the public holds invites scrutiny, especially if the vesting is short. If your numbers push the insider share high, extend vesting rather than shrinking the number, and be ready to explain why.
Step 3: Size the community bucket to what you can actually deploy
Ask how many tokens you can responsibly distribute over the next three to four years through airdrops, rewards and grants. If you cannot write down a plan for a quarter of the community bucket, it is too large or the plan is missing. Programmes such as a points programme versus an airdrop have different supply needs, so decide your distribution mechanics before locking the percentage.
Step 4: Reserve for runway and liquidity
Estimate runway in months, convert it to tokens at a conservative price, and make sure the treasury covers it without relying on the token price rising. Add the liquidity reserve on top. Whatever is left is the headroom you have for the other buckets.
Illustrative Comparison of Allocation Approaches
The table shows how emphasis shifts by project type. These are descriptions of tendencies, not benchmarks.
| Project type | Where the weight sits | Main risk |
|---|---|---|
| VC-backed protocol | Investors and team are large; long vesting | Unlock overhang, insider concentration |
| Community-first launch | Community and ecosystem dominate; small team share | Funding runway, weak treasury |
| Utility or app token | Ecosystem rewards and treasury | Inflation from rewards outpacing demand |
| Infrastructure network | Network incentives and validators | Emission design, security budget |
Common Allocation Mistakes
- No separate liquidity line. Market making inventory ends up borrowed from other buckets, muddying the table.
- Giant undefined ecosystem pool. It looks like a hidden insider reserve.
- Identical vesting for every group. Different roles warrant different cliffs and durations.
- Ignoring the combined unlock calendar. Individually sensible buckets can unlock in the same month. Model them together using token unlock management practices.
- Rounding for aesthetics. Choosing round percentages because they look tidy is not a reason. Each number should trace to a purpose.
- Changing the table after publishing. Revising allocations after investors and exchanges have reviewed them damages trust more than any imperfection in the original.
Allocation Review Checklist
- Every bucket has a one-sentence purpose
- Every bucket has a vesting schedule recorded, including cliff and TGE unlock
- Circulating supply at TGE calculated and matches your launch plan
- Combined insider share calculated and defensible
- Community bucket has sub-allocations and a release plan
- Treasury covers runway without depending on token price
- Launch liquidity and market making inventory budgeted explicitly
- Combined monthly unlock calendar modelled for at least two years
- Wallet addresses, multisig signers and lockups documented
Allocation Is a Launch Dependency
The allocation you publish becomes the base for your listing conversations, your market maker's inventory plan and your investors' expectations. Treat it as something to stress-test, not just to design. At Fibonacci Capital we review distribution tables against launch liquidity and unlock calendars so teams find the weak spots before an exchange or an investor does. If you want a second opinion on your split, talk to us about your pre-TGE plan.