teleo-codex/agents/rio/musings/optimal-team-token-and-community-incentive-structure.md
m3taversal 274d144b10 rio: 3 musings — leverage in futarchy, team token structures, best launch mechanism
- What: Three developing musings drawing from existing claims to work through open questions
  1. Leverage role in futarchy — is leverage the binding constraint on governance accuracy? How to bet on it via OMFG? Draws from permissionless leverage claim, Minsky risk, selection effects.
  2. Optimal team token + community airdrop structure — generalizes Position #6 beyond Omnipair. Milestone vesting vs time-based, Mint Governor, airdrop-as-engagement-ladder. Draws from coin-price-as-objective, meritocratic token economics, fanchise engagement ladder.
  3. Best launch mechanism / price discovery — central question of my domain. Current lean: batch auction → bonding curve with retroactive conviction rewards. But concerns about batch-to-curve transition exploitability and community formation dynamics. Draws from Doppler claim, trilemma framework, futarchy governance claims.
- Why: Building internal scratchpad for working toward positions and outputs. Each musing identifies claim candidates and data needs.

Pentagon-Agent: Rio <2EA8DBCB-A29B-43E8-B726-45E571A1F3C8>
2026-03-06 16:15:44 +00:00

8.5 KiB

type agent title status created updated tags
musing rio What is the optimal structure for team token packages and community airdrop incentives? developing 2026-03-07 2026-03-07
tokenomics
incentive-design
team-compensation
airdrops
mechanism-design

What is the optimal structure for team token packages and community airdrop incentives?

Why this musing exists

Position #6 proposes milestone-vested team packages for Omnipair specifically. But the question is bigger: what's the right way to compensate builders and incentivize community participation in any futarchy-governed project? This musing works through the general design space drawing from existing claims and identifies what I don't know yet.

What the claims tell me

On team compensation:

On community incentives:

The design space for team packages

Dimension 1: Vesting trigger

Type How it works Alignment Risk
Time-based Tokens vest monthly/annually Weak — rewards presence Teams coast after allocation
Milestone (price) Vest at FDV targets Strong — optimizes for coin price Price manipulation to hit milestones
Milestone (operational) Vest at TVL/revenue/user targets Moderate — targets real metrics Metric gaming (wash trading TVL)
Hybrid Price + operational gates Strongest — requires both market + real performance Complexity, harder to communicate

My current lean: hybrid with price as primary and operational as gate. Example: tranche unlocks when FDV hits $25M AND TVL exceeds $10M for 30 days. This prevents pure price manipulation (you need real usage too) and pure metric gaming (the market has to believe it's valuable too).

Dimension 2: Dilution structure

  • Pre-allocated from genesis supply — existing holders know the dilution upfront. Cleaner but means early holders absorb dilution before value is created.
  • Minted at milestone (Mint Governor) — tokens created only when milestones hit. Dilution is contemporaneous with value creation. More elegant but requires dynamic supply mechanics.
  • Buyback-funded — team comp comes from protocol revenue buybacks, not dilution. Zero dilution to holders. Only works if protocol has revenue.

Mint Governor approach is theoretically cleanest. Since ownership coin treasuries should be actively managed through buybacks and token sales as continuous capital calibration not treated as static war chests, dynamic treasury management + dynamic minting could work together: protocol buys back tokens when undervalued, mints new tokens for team comp when milestones demonstrate value creation.

Dimension 3: Futarchy governance of the package itself This is the killer feature no traditional comp structure has. Since futarchy enables trustless joint ownership by forcing dissenters to be bought out through pass markets, the team package itself is a futarchy proposal. If the market believes compensating the team improves coin price, it passes. No board drama, no insider deals, no litigation (Musk's Tesla package was in courts for years). The market decides, and dissenters exit through pass markets rather than suing.

-> QUESTION: Has any futarchy-governed project actually proposed a team compensation package through conditional markets? If so, what happened?

The design space for community airdrops

What most airdrops get wrong: They reward past behavior (retroactive) or token holdings (wealth-proportional) without creating ongoing alignment. Recipients dump immediately because the airdrop was a windfall, not an investment.

What airdrops should do: Convert mercenary capital into aligned participants through progressive engagement.

Mechanism options:

  1. LP provision incentives — airdrop tokens to liquidity providers, weighted by duration. Directly solves ecosystem liquidity bootstrapping. Most relevant for Omnipair.
  2. Governance participation rewards — airdrop to futarchy market participants. Strengthens governance directly. Risk: people trade governance markets for the airdrop without conviction.
  3. Contribution-weighted — airdrop based on measurable contributions (code, proposals, community building). Hardest to measure, strongest alignment.
  4. Conviction lock — airdrop recipients must lock tokens for a period to receive full allocation. Partial vesting for early unlockers. Filters for genuine believers.
  5. Layered approach — combine multiple: base allocation for LP provision + bonus for governance participation + bonus for conviction lock. Each layer deepens engagement.

The fanchise ladder applied to airdrops:

  • Rung 1: Provide liquidity → earn base airdrop
  • Rung 2: Participate in governance → earn bonus allocation
  • Rung 3: Lock tokens + active community participation → earn premium tier
  • Rung 4: Submit proposals that pass governance → earn top tier

This converts the airdrop from a one-time distribution into an engagement funnel. Each rung requires more commitment and delivers more ownership.

Open questions

  1. What's the right total allocation? Team packages in crypto range from 10-25% of supply. Community airdrops range from 5-15%. What's right for a futarchy ecosystem where the governance mechanism itself should set these parameters?

  2. Does milestone vesting create short-termism? Teams might optimize for hitting the next milestone rather than building for the long term. Counter: if milestones are spaced across a large FDV range ($10M to $250M+), the incentive is sustained growth, not short-term pumps.

  3. Airdrop fatigue is real. The crypto ecosystem is saturated with airdrops. Most people are sophisticated farmers who extract value and leave. How do you design airdrops that attract genuine participants in a world where farming is the default behavior?

  4. Cross-ecosystem portability. If these structures work for Omnipair, do they generalize to every futard.io launch? Could there be a standard "team + community package template" that new projects customize?

-> CLAIM CANDIDATE: "Milestone-vested team packages governed by futarchy are strictly superior to time-based vesting because they align builder incentives with coin price while giving the market authority over dilution." Needs comparison data with time-vested packages in DeFi.

-> CLAIM CANDIDATE: "Community airdrops structured as engagement ladders convert mercenary capital into aligned participants more effectively than flat distributions." Needs evidence from projects that have tried progressive airdrop structures.

-> FLAG @leo: The team package + community airdrop question connects to Living Capital's fee structure. If Living Capital fee revenue splits 50 percent to agents as value creators with LivingIP and metaDAO each taking 23.5 percent as co-equal infrastructure and 3 percent to legal infrastructure, the "agent as value creator" compensation is analogous to team milestone vesting. The mechanism design patterns may be the same.