Past Crypto Events Ranked by CoinLaunch Score: Completed Web3 Events, Contests and Airdrops With Recorded Outcomes

Each completed entry keeps the score it held while live alongside what it delivered, which makes the scoring model auditable rather than merely asserted. Recorded per event:

• Realized reward per qualifying participant, in the token and in dollar terms at distribution.
• Participant and qualifier counts, which convert an advertised prize pool into real odds.
• Distribution date and the lag between qualification and payment.
• Whether eligibility criteria changed after the event was announced.
• Final status: distributed, partially distributed, delayed, or never delivered.

That last field is the one no marketing page will ever show you, and it is the reason this archive is more useful than a cryptocurrency events calendar that only lists what was promised.

Sorting completed entries by realized reward against hours invested produces a consistent ranking across cycles:

1. Retroactive usage airdrops led by a wide margin, rewarding people who used a protocol genuinely before any announcement existed.
2. Hackathons came next on expected value, because prize pools are deep and the field is small relative to the reward.
3. Testnet and bug-bounty participation paid reliably, if modestly, and almost always delivered.
4. Quest and learn-and-earn campaigns paid small amounts but paid quickly and consistently.
5. Social task campaigns ranked last, with the highest ratio of announced to undelivered rewards.

The ordering is visible in the data rather than anecdotal, which matters because the loudest campaigns sit at the bottom of it. Anyone deciding where to earn crypto online is better served by this ranking than by engagement volume.

Advertised prize pools and distributed prize pools are different numbers, and past crypto trading competitions are where the gap shows most clearly. The archive records, per competition:

• Advertised pool against the amount genuinely distributed.
• How far down the leaderboard rewards actually reached.
• Entrant counts, which set real odds rather than implied ones.
• Whether volume-ranked or return-ranked formats produced better outcomes for smaller accounts.

Reviewing an exchange's completed competitions before entering its next one is the cheapest diligence available. A venue that consistently pays deep into its leaderboard deserves more of your time than one whose pool always concentrates in the top three places, and that pattern is stable enough per venue to be predictive.

A meaningful share of announced campaigns never paid, and the archive tags them rather than removing them. Roughly 50% of crypto projects launched since 2014 are now considered defunct according to CoinGecko research, and undelivered rewards track that base rate closely. The recurring causes:

• The project wound down before token generation, so nothing existed to distribute.
• TGE slipped indefinitely and the campaign was quietly dropped from communications.
• Eligibility was narrowed after the snapshot, shrinking the qualifying set dramatically.
• Sybil filtering excluded far more wallets than participants anticipated.

Each of these leaves a trace in the record before it becomes obvious in the market, which is precisely what makes the historical view worth consulting first.

Patterns that look ambiguous in a single announcement become obvious across a history, which makes the archive the most reliable scam filter available:

• Check whether the project's previous events distributed at all. A record of announced-but-undelivered rewards is the clearest signal there is.
• Compare advertised against realized rewards across several campaigns. Persistent large gaps indicate a marketing budget rather than a rewards budget.
• Measure how long past distributions took relative to what was promised.
• Look for eligibility rules that were rewritten after a snapshot, a recurring feature of campaigns designed to shrink the payout.

Standard precautions still apply to anything live: burner wallet, never share a seed phrase, never pay upfront to claim, verify URLs against official channels, revoke approvals afterward. What the archive adds is the ability to check a track record before connecting anything at all.

The events database is split into three views, each built for a different job:

• Upcoming: scheduled events not yet started. Built for registration.
• Active: events running right now. Built for participation.
• Past (this page): completed events with outcomes and payout records. Built for judging what to enter next.

Because one record persists across all three, the score an event carried while scheduled can be compared directly against what it eventually paid.