80% pool funding — why the on-chain percentage matters
The metric nobody discusses
Crypto game marketing optimizes for headline numbers: total supply, percentage allocated to community, vesting curves. What gets buried in the small print: where does the project's actual revenue go?
A "40% community allocation" sounds generous. It's meaningless if 90% of post-launch revenue flows to the team wallet and only 10% flows to the airdrop pool. The community allocation gets eroded by team selling pressure within months.
The real signal is the revenue-to-pool percentage. This is what tells you whether the project is building toward long-term token health or extracting short-term founder value.
Dominance.live's 80% rule
Three things make this 80% claim verifiable:
- Pool wallet addresses are published. Anyone with Solscan / Etherscan can confirm the incoming USDC/SOL/BTC matches the stated split.
- Revenue is dual-source (crypto + Stripe), with clear delineation. Stripe revenue can't flow to the on-chain pool by definition — it's bank money. The 80% rule applies to crypto revenue only, which is the only revenue that could flow on-chain.
- The split is hardcoded, not discretionary. When a crypto payment arrives, the splitter contract / off-chain accounting routes 80/10/10 automatically. No human chooses each split.
Why 80% specifically
The split came from a math exercise: what's the minimum percentage that makes the airdrop pool grow faster than typical token-issuance pressure?
If the pool grows by $X per week and the team allocation unlocks by $Y per week (post-vesting), the pool needs to outpace Y for the airdrop to maintain real value. 80% of crypto revenue, with the project's projected revenue curve, comfortably outpaces the vesting unlock schedule. 60% would barely break even. 40% would lose ground.
The 10% to locked liquidity is also non-negotiable: without locked LP at TGE, the token has no immediate trading market. The 10% to dev/infra is the absolute minimum to keep the lights on (server costs alone are non-trivial for a real-time multiplayer game).
What's wrong with vaguer competitors
Competitor patterns that signal pool-funding opacity:
- "Majority of revenue"
- What majority? 51%? 99%? Unverifiable. Almost always means 30-50% in practice.
- "Tokenomics designed for community"
- Marketing language, zero specifics. Translation: there's no published wallet split.
- Beautiful infographic with pie charts
- Charts can lie. Wallets can't (if published). If the project ships a pie chart but no wallet list, the chart is fiction.
- "Sustainable tokenomics"
- Sustainable means different things to different teams. Without numbers, the word is empty.
How to audit a pool
If you're vetting a crypto project's airdrop in 2026, the audit checklist:
- Find the published pool wallet address. If it's not published, the project is opaque. Walk away.
- Find the published revenue wallet address. Same standard.
- Compare incoming and outgoing on-chain transactions. Use Solscan or Etherscan. The percentage flowing from revenue → pool should match the stated split (allowing for some timing variance).
- Check for "extra" outflows. If revenue flows in but most of it leaves the wallet to a "team multisig", that's the percentage actually going to the team.
- Verify the timing. The split should happen within hours of revenue arrival, not weeks. Delayed splits = team capital management = potential rug.
The TGE incentive trap
Most projects sandbag the on-chain split until after TGE. The play is: collect revenue, hold it in a team wallet, let TGE spike the token price, then dump team allocation. Once the team has cashed out, the pool is irrelevant — the price has already crashed.
Dominance.live's defense: the pool split happens before TGE, during the live-play period. Revenue arrives, 80% routes to the pool wallet immediately. By the time TGE happens, the pool is already at its "true" size based on accumulated revenue. The airdrop allocation is a function of pool size — players see the real number, not a projection.
Stripe-card revenue: why it's excluded
One nuance worth explaining: Stripe card payments are EXCLUDED from the 80% rule.
Reasoning: Stripe takes ~3% per transaction. The card-payment infrastructure (PCI compliance, chargeback management, fraud screening) has real costs. If we routed 80% of Stripe revenue on-chain, we'd lose money on every card sale — Stripe fees alone would exceed the 20% retained.
Card payments cover: Stripe processing fees, server hosting, ops headcount, customer support. Card payments DO NOT contribute to the on-chain pool. This is explicit in the airdrop rules.
For users who want their spending to feed the pool: pay in crypto. BTC, USDC on Ethereum, USDC/SOL on Solana — all flow 80% to the pool. Card payments are convenient but contribute nothing to the airdrop.
What this means for the $DOM thesis
If you believe Dominance.live grows to 10,000 daily active players with 5% conversion to crypto skin purchases at $15 average, the pool flow math is:
| Metric | Value |
|---|---|
| Daily crypto-paying users | 500 |
| Average crypto spend | $15 |
| Daily crypto revenue | $7,500 |
| Daily pool flow (80%) | $6,000 |
| Monthly pool flow | $180,000 |
| Annual pool flow (steady state) | $2.16M |
These are illustrative numbers, not promises. The point: at modest scale, the pool grows meaningfully. At larger scale (50K daily active, 8% conversion), the numbers go up an order of magnitude. The 80% rule means the pool grows in lockstep with the game's success.