Skip to content

Airdrop: 'First Conditional Airdrop' innovation banner #1013

@realproject7

Description

@realproject7

Problem

The airdrop page presents the campaign as just another airdrop with point farming. Nothing communicates that this is a fundamentally different mechanism. The current 3-column comparison (Typical Airdrop / Typical Staking / This Airdrop) includes staking which is unnecessary — the contrast should be direct: typical airdrop vs this airdrop.

Solution: Two-column comparison

Wireframe

```
┌─────────────────────────────────────────────────────────────┐
│ │
│ ── HOW IS THIS DIFFERENT? ─────────────────────────── │
│ │
│ ┌──────────────────┐ ┌──────────────────┐ │
│ │ TYPICAL AIRDROP │ │ THIS AIRDROP │ │
│ │ │ │ │ │
│ │ Fixed amount │ │ Pool grows │ │
│ │ │ │ with market │ │
│ │ Dumps on │ │ │ │
│ │ day 1 │ │ Burned if │ │
│ │ │ │ no growth │ │
│ │ No skin │ │ │ │
│ │ in game │ │ Everyone wins │ │
│ │ │ │ together │ │
│ └──────────────────┘ └──────────────────┘ │
│ dimmed accent border │
│ │
│ "The pool isn't pre-valued — it's valued BY the market. │
│ At $100M MCap, 50,000 PLOT = $5M distributed. │
│ At $0 growth, 50,000 PLOT = burned forever. │
│ Everyone — team, holders, earners — wins only if │
│ PLOT grows." │
│ │
└─────────────────────────────────────────────────────────────┘
```

Changes from previous design (#1013 original)

  1. Remove "Typical Staking" column — unnecessary comparison, dilutes the message
  2. "Dumps on listing" → "Dumps on day 1" — more direct and relatable
  3. Two columns only — cleaner, stronger contrast
  4. Use "MCap" not "FDV" in the summary paragraph (per Airdrop: redesign milestone section — emphasize three core messages #1019)

Placement

Below CampaignHero, above UserPoints/Leaderboard grid.

Files to modify

  • `src/components/airdrop/InnovationBanner.tsx` — simplify to 2-column
  • Use "MCap" terminology throughout

Acceptance Criteria

  • Two-column comparison only (Typical Airdrop vs This Airdrop)
  • "Dumps on day 1" wording
  • No staking column
  • Summary paragraph uses MCap terminology
  • Responsive: side-by-side on desktop, stacked on mobile

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