Launch Competition
Sign in with X

Competition rules

A simple, auditable path from community proposal to main-app launch order.

Frozen rules snapshot. SHA-256 5df25ba08c24842420a2523d327f81dabd673f8fad50b2a415b685d86ea3dfb9 · Frozen Aug 13, 2026, 2:51 AM UTC.

Who can participate

Anyone can browse. Creating an OTF or voting requires a verified, public X account with at least 100 followers that is at least 30 days old. Eligibility is refreshed from the public profile whenever the account connects. A fixed operator allowlist may waive verification and follower-count requirements; public-account and account-age requirements still apply.

Creating an OTF

  • The first 7 days are reserved for submissions. Voting opens on competition day 8, and submissions remain open throughout the 30-day voting phase.
  • Each eligible X account may submit as many OTF proposals as it wants. A submission may be deleted while it has 0 votes.
  • The name must end in “OTF”; tickers are uppercase and no longer than 16 characters.
  • Choose at least 2 distinct 18-decimal assets and allocate at least 1% to each. View verified assets.
  • Verified assets use the price source stored in their catalog row: Robinhood bids for stock tokens and Coinbase ETH/USD bids for ETH exposure. Submitters cannot override these sources.
  • Unlisted assets are checked server-side through Robinhood RPC first. Their pool must be a canonical Uniswap V3 pool containing the asset and exactly canonical WETH or USDG, with a supported fee, initialization, at least 64 observations, and a successful one-hour observation. GeckoTerminal evidence must then show at least $30,000 liquidity, at least $100,000 verified market cap (never FDV), seven-day pool age, GT verification, GT score at least 50, no honeypot flag, and at least 50% locked liquidity.
  • Weights must total exactly 100%.
  • Add your own optional context, publish the prepared post from X, and paste its public URL for verification.
  • An OTF is Verified only while every current constituent is verified; otherwise it is Non-verified. Verification selects the performance XP pool but never affects eligibility, pricing, fees, permissions, votes, or launch order.
  • Competition return snapshots come from the external API selected by each asset's saved price source. Missing competition prices make performance Pending but do not affect votes or launch rank.

Voting

  • Voting begins after the 7-day submission-only phase. Each eligible X account starts with 3 unlocked votes.
  • 1 additional vote unlocks every 3 voting days, up to 12 votes total. No vote is added on the final voting day.
  • Unlocked votes may be cast across one or more OTF proposals. Creators may vote for any proposal, including their own.
  • Once cast, a vote cannot be moved, removed, redistributed, or made available again.
  • Every voting action requires a public X post. Several unlocked votes may be cast together and verified by one post.
  • OTF picks are omitted from each post by default and appear only when the voter chooses to reveal the OTFs and vote counts in that batch.
  • Every required voting post must remain public and unchanged, including after the competition ends. Deleting or editing a voting post is prohibited and never restores its spent vote slots.

Ranking and launch order

Votes from valid activated ballots count. Proposals sort by allocated votes descending, then earlier submission time, then immutable proposal ID. Ranks are unique ordinal positions.

The final ranking directly becomes main-app launch order: #1 first, #2 second, #3 third, and so on. Public pages show order only—not internal dates or readiness windows.

Moderation

Manipulation, impersonation, automated abuse, deleted evidence posts, or invalid asset records may invalidate an action. Later fraud voids the affected slot; ranks are not renumbered.

XP allocation

Exactly 10,000,000 XP will be allocated once, after the competition closes and the final audit is complete: 3,500,000 verified-performance XP, 1,750,000 non-verified-performance XP, 2,750,000 participation XP, and 2,000,000 creator XP. No provisional XP balance or ranking is calculated or published during the competition.

Performance XP

Every verified vote batch creates a separate immutable tranche. Votes for Verified OTFs compete for the 3,500,000 XP verified-performance pool—a 100% boost over the 1,750,000 XP pool for Non-verified OTFs. Vote activation references the newest complete saved price checkpoint at or before activation; it never calls a provider. Market cap, FDV, and token supply never enter return calculations.

Participation and creator XP

Participation uses valid vote units only and never follower count. The full 2,000,000 creator pool is divided among proposal creators in direct proportion to the valid votes their proposals receive.

Final allocation

If either performance pool has no eligible score, that pool rolls to participation. After close, the OTF team exports the frozen competition inputs, calculates the final XP allocation outside the launch app, verifies the 10,000,000 XP total, and publishes the result. View the allocation method.

XP has no guaranteed monetary value. It is separate from launch ranking, which continues to use valid votes and the published tie-breakers only.

Changes

The hashed rules snapshot cannot change after the competition opens. Non-material clarifications may be published here with their effective time and recorded in the audit history; a material rule change requires a new competition snapshot.