Airdrop readiness
Campaign, eligibility, proof and distribution readiness without inventing a campaign or claimable allocation.
Static readiness education can explain official-source discipline, documentation preparation, and future campaign safety expectations.
No campaign, snapshot, wallet lookup, Merkle proof, allocation calculation, eligibility result, claim state, or distribution process is connected.
An approved campaign, verified dataset, privacy review, proof architecture, security validation, public rules, and release approval must exist first.
Explain how users should verify official links, announcements, and safety language before trusting any future readiness flow.
Avoid statuses such as eligible, not eligible, pending, approved, allocation, claimable, or snapshot matched.
Keep the page clear that no claim window, token distribution, wallet check, or transaction prompt is available.
- 01Review official sourcesAvailable now
Use only approved project announcements, documentation, and safety guidance when reviewing future readiness information.
- 02Keep campaign results unavailableNot active
No wallet, snapshot, allocation, eligibility, proof, claim, or distribution result is produced.
- 03Require an approved campaign gateRelease gated
Future campaign functionality depends on approved rules, data provenance, proof security, and release governance.
Safety + activation boundaryView controls
No airdrop eligibility lookup is active.
No wallet snapshot or wallet read is active.
No claim window is active.
No token distribution is active.