Choosing the winning community.

Qualification, ranking and final settlement each do a different job.

Community rewards
In this guide

Qualifying is not winning

The researched registration model gives each eligible registered wallet one point. The team with the highest valid score at the deadline wins if it meets the minimum threshold. This scoring model requires final policy approval and must be fixed in the campaign terms.

Illustration · 200-wallet qualification threshold
TeamEligible registrationsResult at close
Team A260Highest score; qualifies to win.
Team B225Qualifies, but ranks below Team A.
Team C170Does not meet the example threshold.

Reaching the threshold does not end the campaign. Trade volume, follower count and website activity do not replace the chosen eligibility and scoring rule. Members outside the winning set receive no campaign allocation.

Freeze, verify, settle

  1. Close entry

    Apply the published deadline using authoritative chain time for on-chain registration.

  2. Resolve results

    Freeze counts and apply the disclosed verification/finality window. Leaderboards remain provisional until settlement.

  3. Calculate the winner

    In the bounded on-chain roster design, evaluate every registered team. Reject omitted or duplicate team accounts. If a service publishes results, disclose its authority and evidence.

  4. Commit entitlements

    Record the winning set, eligible member count, allocation and release terms once. Repeated settlement cannot reset claim history or increase the reserved obligation.

Ties and failed campaigns need rules first

The research proposes sharing a tie between top teams by eligible participant count, giving every winning member the same amount. A deterministic single-winner rule is an alternative. Neither should be chosen after registration closes.

If no team qualifies, there is no winning entitlement to pay. The conservative reference keeps the reserve restricted. Reuse in another campaign, expiry, unclaimed awards and dust all require explicit policies; none creates an automatic developer refund.

A settled award is not yet a transfer

Settlement establishes who earned tokens. Claim availability additionally depends on funded custody and the published release schedule. An external engine can impose its own migration and vesting conditions before tokens are collectable.