A practical 30-day map for the launchpad and its first graduated token: FUN.
FUN graduated at its 1,000 USDC target. Three WLD launches are still building toward their own 2,000 WLD targets.
FUN / graduatedgraduatedEarly demand is concentrated in one proof point: FUN.
The WLD queue is healthy, but only 10.77% funded as a group.
The next bottleneck is trust and time-to-graduate, not more token pages.
Planning ranges, not promises. USDC and WLD are tracked separately.
Every stage has an exit signal. If it is not measurable, it is not a milestone.
Close the graduation loop, surface honest status and make wallet actions recoverable when a transaction is delayed.
Make the path from idea to token feel short, legible and worth sharing without adding complexity before the core loop is stable.
Improve holder clarity, graduation visibility and post-launch trading so the market can price tokens without guessing what happened.
Use FUN as the shared story of the platform: changelogs, holder feedback and a transparent reward design before any distribution begins.
Grow the launch surface only as fast as monitoring, support and liquidity explanations can keep up.
FUN starts with a fixed 100,000,000 supply. Burns can reduce it; the launchpad does not need inflation to feel alive.
USDC and WLD launches are measured on their own rails. No blended headline hides how much real liquidity each queue has.
Holder rewards should follow a published mechanism, sustainable cashflow and anti-abuse checks—not a rushed emission promise.
FUN does not promise returns. We show what can happen on-chain, what is still being built and who is accountable to each community.
A holder can sign a burn of FUN they own. The contract destroys those tokens, so total supply can only go down; there is no post-launch mint and no automatic burn without consent.
FUN holder rewards will use published snapshots, eligibility criteria, a visible budget and anti-abuse checks. They activate only when the mechanism is sustainable and documented.
Token creators must maintain metadata and links, communicate risks, answer questions, report bugs and publish changes. The launchpad provides infrastructure; the creator owns the community relationship.
No reward is guaranteed yield. Every burn or distribution requires an explicit action and a visible rule.
The roadmap moves when the numbers improve and the support queue gets quieter.