Skip to content

Airdrop: redesign milestone section — emphasize three core messages #1019

@realproject7

Description

@realproject7

Problem

The current "What happens as PLOT grows" section (flat rows with FDV/unlock%/burn%/PLOT/pool value) is information-dense but doesn't land the three core messages:

  1. As PLOT price grows, the airdrop pool value grows too (double benefit)
  2. 4 milestone steps — each one is realistic (anchored by CMC ranking)
  3. Even if milestones aren't reached, tokens burn forever (deflationary = good for holders)

The current layout dumps all data in one flat table. Users see numbers but miss the narrative.

Solution: Three-section layout

Replace the flat milestone rows with three distinct visual blocks, each delivering one message.

Wireframe

```
┌─────────────────────────────────────────────────────────────┐
│ │
│ ━━ 1. YOUR AIRDROP GROWS WITH $PLOT ━━━━━━━━━━━━━━━━━━ │
│ │
│ The pool is 50,000 PLOT. Its value depends on the market. │
│ │
│ ┌────────────────────────────────────────────────────┐ │
│ │ Now MCap $32K Pool value: $0.10 │ │
│ │ ────────────────────────────────────────────── │ │
│ │ Step 1 MCap $1M Pool value: ~$5K │ │
│ │ Step 2 MCap $10M Pool value: ~$150K │ │
│ │ Step 3 MCap $50M Pool value: ~$1.3M │ │
│ │ Step 4 MCap $100M Pool value: ~$5M │ │
│ └────────────────────────────────────────────────────┘ │
│ │
│ The same 50,000 PLOT — worth $0.10 today, or $5M at │
│ full distribution. Your airdrop size = market growth. │
│ │
│ ━━ 2. FOUR STEPS — NOT UNREALISTIC ━━━━━━━━━━━━━━━━━━━ │
│ │
│ Each step unlocks a bigger share of the pool. │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ $1M │ │ $10M │ │ $50M │ │ $100M │ │
│ │ │ │ │ │ │ │ │ │
│ │ ≈#1900 │ │ ≈#950 │ │ ≈#400 │ │ ≈#250 │ │
│ │ on CMC │ │ on CMC │ │ on CMC │ │ on CMC │ │
│ │ │ │ │ │ │ │ │ │
│ │ unlocks │ │ unlocks │ │ unlocks │ │ unlocks │ │
│ │ 10% │ │ 30% │ │ 50% │ │ 100% │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ (dimmed) (dimmed) (dimmed) (accent) │
│ │
│ These aren't moonshot numbers — #250 on CMC is a │
│ mid-tier project. Thousands of tokens have done it. │
│ │
│ ━━ 3. NOT REACHED? BURNED FOREVER. ━━━━━━━━━━━━━━━━━━━ │
│ │
│ ┌────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ If MCap stays below $1M: │ │
│ │ 50,000 PLOT → burned permanently 🔥 │ │
│ │ │ │
│ │ No team keeps it. No treasury recycles it. │ │
│ │ Burned = reduced supply = value for holders. │ │
│ │ │ │
│ └────────────────────────────────────────────────────┘ │
│ │
│ Either way, PLOT holders benefit: │
│ reach milestones → earn airdrop. │
│ miss milestones → supply shrinks. │
│ │
└─────────────────────────────────────────────────────────────┘
```

Design details

Section 1: "Your airdrop grows with $PLOT"

  • Simple table: MCap target → Pool value at that MCap
  • Starts with "Now" row showing current state
  • Punchline: "same 50,000 PLOT, worth $0.10 or $5M"
  • This is the "double benefit" insight — you earn PLOT AND each PLOT becomes worth more

Section 2: "Four steps — not unrealistic"

Section 3: "Not reached? Burned forever."

  • Boxed callout with fire emoji
  • Key message: burn is GOOD for holders (supply reduction)
  • "No team keeps it. No treasury recycles it." — addresses the trust concern
  • Short "either way you win" summary

Responsive

  • Desktop: sections stack vertically, cards in section 2 are 4-col
  • Mobile: same stack, cards become 2×2

Relationship to other tickets

Files to modify

  • `src/components/airdrop/CampaignHero.tsx` — replace milestone rows with 3-section layout

Acceptance Criteria

  • Three distinct sections, each delivering one clear message
  • Section 1: pool value growth table with "Now" row + 4 targets
  • Section 2: 4 step cards with MCap + CMC rank + unlock %
  • Section 3: burn callout — "burned = good for holders"
  • Uses MCap terminology
  • Responsive layout
  • "Either way you benefit" conclusion

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/T3Assigned to T3 builder agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions