KOLs, communities & eligibility.
An invitation brings people to a campaign. An eligible, explicit registration counts them.
In this guide
A KOL brings the community
An organizer creates a community profile with a name, image, social identity and organizer wallet. The team joins an open campaign or one that has invited it. A referral link takes people to that team’s campaign page.
Campaign terms must say who can register teams and when the roster closes. The bounded-roster reference freezes approved teams before participant entry opens, so the settlement calculation has a complete set to evaluate.
Any verification badge must specify what was checked, such as social account control or wallet control. Verification is not an endorsement or an assessment of token value.
Join with a wallet you control
Read the campaign
Check the mint, allocation, selected team, deadline, eligibility and release terms before entering.
Prove wallet control
Use a scoped authentication challenge with origin, nonce and expiry where off-chain authentication is required. Connecting a wallet alone is insufficient.
Check eligibility
Apply the published qualification rule and snapshot. An exclusion needs a reason and the disclosed review route.
Confirm the team
An explicit registration creates the authoritative entry. The reference design fixes one wallet to one team for the campaign and rejects duplicate retries.
Eligibility is campaign-specific
| Community | Possible rule | What it does not prove |
|---|---|---|
| Existing token community | Hold a minimum amount at a specified historical snapshot, possibly with holding history. | One wallet equals one person. |
| KOL audience | Explicit registration plus published wallet-history/activity checks, with optional authenticated social membership. | A social account or wallet age is a perfect identity check. |
The registration-based reference does not require buying the newly launched coin. A holder of some other qualifying asset is not automatically a holder of the new coin. Exact balance thresholds, data sources and anti-farming rules require a published policy.
Make the count reproducible
Freeze a reproducible eligibility dataset when the campaign design permits it. Publish the rule version and review process. A Merkle proof can prove membership in that dataset, but it cannot independently establish that the dataset was fair or that a wallet represents a unique human.
Shared funding sources are review signals, not automatic proof of a shared owner. Exchange funding can connect unrelated users. Pools, vaults and custodial accounts need explicit treatment. Eligibility must not change secretly after an operator sees the result.