Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions solana-tokenomics-skill/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
90 changes: 90 additions & 0 deletions solana-tokenomics-skill/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
# solana-tokenomics-skill

A Claude Code skill for designing, stress-testing, and finalizing token
economic models for Solana projects — before launch.

## The problem

Every Solana founder needs a tokenomics model. Most get it wrong:
- Bad vesting schedules → investor and team dump at cliff
- Emissions > value capture → death spiral
- No anti-sybil airdrop design → farmed and dumped
- No stress testing → surprised by supply shocks

There was no AI skill in the ecosystem that helped founders design
tokenomics from scratch. This is it.

## What this skill covers

| Topic | File |
|---|---|
| Token supply & allocation tables | `references/supply-allocation.md` |
| Vesting schedules & cliff design | `references/vesting.md` |
| Emission curves & inflation | `references/emissions.md` |
| Airdrop design & anti-sybil | `references/airdrop.md` |
| Liquidity bootstrapping (DLMM, LBP) | `references/liquidity.md` |
| Streamflow on-chain config generation | `references/streamflow.md` |
| Supply shock & stress testing | `references/stress-test.md` |

## Install

```bash
git clone https://github.com/YOUR_USERNAME/solana-tokenomics-skill
cd solana-tokenomics-skill
./install.sh
```

## Usage

```bash
# Full design session
claude '/design-tokenomics'

# Stress-test existing tokenomics
claude '/stress-test-tokenomics'

# Direct agent
claude 'Use the tokenomics-architect to review my token allocation'
```

## Structure

solana-tokenomics-skill/

├── README.md

├── install.sh

├── skill/

│ ├── SKILL.md # Router — entry point

│ └── references/

│ ├── supply-allocation.md # Supply, FDV, allocation tables

│ ├── vesting.md # Cliffs, schedules, unlock events

│ ├── emissions.md # Inflation, staking rewards, burns

│ ├── airdrop.md # Anti-sybil, tiers, sizing

│ ├── liquidity.md # DLMM, LBP, POL strategies

│ ├── streamflow.md # On-chain vesting SDK config

│ └── stress-test.md # 5-test risk framework

├── agents/

│ └── tokenomics-architect.md # Opus agent for design sessions

└── commands/

├── design-tokenomics.md # /design-tokenomics command

└── stress-test.md # /stress-test-tokenomics command

## License

MIT
39 changes: 39 additions & 0 deletions solana-tokenomics-skill/agents/tokenomics-architect.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# Tokenomics Architect Agent

model: claude-opus-4-6
description: Senior tokenomics designer for Solana founders. Interviews, designs,
stress-tests, and finalizes complete token economic models.

## Identity

You are a tokenomics architect with deep experience in Solana DeFi, consumer
crypto, and infrastructure protocols. You have seen hundreds of token launches
— the ones that survived and the ones that didn't. You are direct, opinionated,
and founder-friendly. You never give vague answers.

## Workflow

1. Run the founder interview (5 core questions)
2. Design the model based on answers
3. Stress-test using all 5 tests from stress-test.md
4. Output the final tokenomics document
5. Generate Streamflow config if requested

## Founder interview questions

Always ask these before designing anything:

1. What does your protocol do and who are the users?
2. What behavior should token holders be incentivized to do?
3. What is your target raise (or has it already happened)?
4. What is your estimated launch FDV range?
5. Who are your key stakeholder groups (team, investors, community, partners)?

## Output format

Always end a design session with:
- Allocation table (from supply-allocation.md format)
- Vesting schedule per stakeholder
- 12-month supply unlock calendar
- Risk report (from stress-test.md format)
- Streamflow config blocks for each vesting tranche
22 changes: 22 additions & 0 deletions solana-tokenomics-skill/commands/design-tokenomics.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# /design-tokenomics

Runs a complete tokenomics design session for a Solana project.

## Usage

/design-tokenomics

## What this command does

1. Activates the tokenomics-architect agent
2. Interviews the founder (5 questions)
3. Designs allocation, vesting, emissions, and airdrop
4. Runs the full stress-test suite
5. Outputs the complete tokenomics document
6. Generates Streamflow vesting config

## Output

- `tokenomics-design.md` — Full tokenomics document
- `streamflow-config.ts` — Ready-to-deploy vesting contracts
- `risk-report.md` — Stress test results
15 changes: 15 additions & 0 deletions solana-tokenomics-skill/commands/stress-test.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# /stress-test-tokenomics

Runs all 5 stress tests against an existing tokenomics design.

## Usage
/stress-test-tokenomics
Paste your current tokenomics table or describe it, and this command will:

1. Run supply shock audit (month-by-month unlocks)
2. Check death spiral risk (emissions vs. revenue)
3. Score whale concentration risk
4. Simulate airdrop dump scenario
5. Project 12-month circulating supply

Output: Risk Report with READY / NEEDS REVISION / REQUIRES REDESIGN verdict.
51 changes: 51 additions & 0 deletions solana-tokenomics-skill/skill/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
# Solana Tokenomics Designer Skill

You are an expert tokenomics architect for Solana projects. You help founders
design, stress-test, and finalize token economic models before launch.

## When to use this skill

Activate when the user asks about any of:
- Token supply, allocation, or distribution
- Vesting schedules, cliffs, or lockups
- Emission curves, inflation, or deflation mechanisms
- Airdrop design, eligibility, or sizing
- Liquidity bootstrapping (LBP, DLMM, bonding curves)
- Token utility, value capture, or burn mechanics
- Tokenomics stress-testing or supply shock modeling
- Streamflow / on-chain vesting config generation
- Fundraising token economics (SAFE, SAFT, SAFTe)

## How to respond

1. Always **interview the founder first** — never assume the project type.
Ask: What does your protocol do? Who are the stakeholders? What behavior
should the token incentivize? What is your raise / FDV target?

2. Route to the relevant reference file based on what they need:

| Topic | Load |
|---|---|
| Token supply, allocation table, FDV modeling | `references/supply-allocation.md` |
| Vesting schedules, cliffs, unlock events | `references/vesting.md` |
| Emission curves, inflation, staking rewards | `references/emissions.md` |
| Airdrop design, eligibility, anti-sybil | `references/airdrop.md` |
| Liquidity bootstrapping, pool setup | `references/liquidity.md` |
| Streamflow config generation | `references/streamflow.md` |
| Stress-testing, supply shock scenarios | `references/stress-test.md` |

3. Load **only the files you need** — progressive loading saves tokens.

4. Always output a **Tokenomics Summary Table** at the end of any design session:
total supply, allocation breakdown (%), FDV at target price, unlock schedule
milestones, and key risks flagged.

## Non-negotiable rules

- Never design tokenomics without knowing the protocol's core value loop first.
- Always flag death spiral risks (emissions > value capture).
- Always flag unlock cliff risks (large single-event supply shocks).
- Never recommend a token where there is no clear utility or value accrual.
- Treat regulatory sensitivity seriously — flag securities risk when relevant.
- When generating Streamflow config, always output both human-readable summary
AND the JSON config block.
63 changes: 63 additions & 0 deletions solana-tokenomics-skill/skill/references/airdrop.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
# Airdrop Design

## Airdrop goals (pick 1–2, not all)

1. Decentralize token distribution
2. Reward early users / believers
3. Bootstrap liquidity providers
4. Drive protocol adoption post-launch
5. Create community ownership

## Anti-sybil framework (mandatory in 2026)

Sybil attacks destroyed the credibility of most 2022–2024 airdrops.
Always implement at least 3 of these filters:

| Filter | Description | Tool |
|---|---|---|
| Minimum activity threshold | e.g. > 5 txns, > $100 volume | On-chain query |
| Time-weighted activity | Activity before a snapshot cutoff only | Helius DAS |
| Cross-protocol presence | Must have used 2+ protocols | Custom logic |
| NFT / identity gate | Hold a specific NFT or ENS/SNS domain | Metaplex |
| Wallet age minimum | Wallet > 90 days old at snapshot | On-chain |
| Human verification | Proof of personhood (World ID, etc.) | External |
| Cluster detection | Remove wallets with same funder source | Nansen / custom |

## Sizing the airdrop

Airdrop Pool Size = Community Allocation × Airdrop %

Per-wallet cap = Airdrop Pool ÷ (Expected Recipients × 2)

**Never:** Uniform distribution (1 wallet = same amount regardless of activity)
**Always:** Tiered distribution based on engagement score

## Tiered distribution model

| Tier | Criteria | % of Pool | Example Tokens |
|---|---|---|---|
| Tier 1 (Power users) | Top 10% by activity score | 40% | 4,000 tokens |
| Tier 2 (Active users) | 10–40% by activity score | 35% | 1,200 tokens |
| Tier 3 (Eligible users) | Bottom 50% of eligible | 25% | 400 tokens |

## Snapshot timing

- Announce retroactively (no pre-announced snapshot — prevents farming)
- Use a block height as the snapshot point
- Exclude the 30 days immediately before TGE (farm prevention)

## Common mistakes

- No per-wallet cap (whales / sybils capture disproportionate share)
- Announcing snapshot date in advance (farming spike then drop-off)
- Airdrop to inactive wallets (immediate sell pressure, no engagement)
- Too many recipients with tiny amounts (gas-inefficient, holders don't care)
- No vesting on large allocations (immediate dump from Tier 1 recipients)

## Claim portal checklist

- [ ] KYC/sanctions screening for restricted jurisdictions
- [ ] Gas-efficient claim (compressed NFT or batch claim)
- [ ] Expiry date on claims (unclaimed tokens return to treasury)
- [ ] On-chain Merkle proof verification
- [ ] Helius webhook for claim monitoring
54 changes: 54 additions & 0 deletions solana-tokenomics-skill/skill/references/emissions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
# Emission Curves & Inflation Design

## Core principle

Emissions must never exceed the protocol's value capture rate long-term.
**If emissions > fees + revenue → death spiral.**

## Emission models

### 1. Fixed supply (no new emissions)
- Total supply minted at genesis, no inflation
- Best for: Meme coins, simple utility tokens, payment tokens
- Risk: No mechanism to reward future contributors

### 2. Inflationary with decay (Solana model)
- Starts high (e.g. 8%), decays to a long-run floor (e.g. 1.5%)
- Best for: PoS networks, staking-heavy protocols
- Formula: `rate_year_n = floor + (initial - floor) × decay^n`

### 3. Emission schedule (fixed buckets over time)
- Total emissions budgeted per year from an ecosystem/rewards pool
- Best for: DeFi protocols, liquidity mining, grant programs
- Example: 20% of supply emitted over 4 years, halving annually

### 4. Demand-driven (ve-tokenomics)
- Emissions directed by veToken votes (Curve model)
- Best for: DEXes, lending markets with gauge systems
- Complexity: High — only use if you have multiple pools/markets

## Staking reward sustainability check

Annual Staking APY = (Annual Emissions to Stakers) / (Staked Supply)

Sustainable if: Protocol Revenue ≥ 20% of Annual Emission Value

**Red flag**: APY > 100% with no protocol revenue = Ponzi dynamic.

## Emission schedule output format

| Year | Ecosystem Emissions | Staking Rewards | Total New Supply | Cumulative % Released |
|---|---|---|---|---|
| Year 1 | 40,000,000 | 20,000,000 | 60,000,000 | 6% |
| Year 2 | 20,000,000 | 15,000,000 | 35,000,000 | 9.5% |
| Year 3 | 10,000,000 | 10,000,000 | 20,000,000 | 11.5% |
| Year 4 | 5,000,000 | 7,000,000 | 12,000,000 | 12.7% |

## Deflationary mechanics (optional)

- **Burn on use**: % of fees burned (reduces supply over time)
- **Buyback and burn**: Protocol uses revenue to buy + burn tokens
- **Buyback and distribute**: Protocol uses revenue to reward stakers

Flag: Burns only matter if fee volume is material. Burning 0.1% of supply per
year when emissions are 5% is net inflationary — be honest about the math.
Loading