> For the complete documentation index, see [llms.txt](https://vitality-project.gitbook.io/vitality-token-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitality-project.gitbook.io/vitality-token-project/participation-and-reward-opportunities/campaign-and-airdrop-framework.md).

# Campaign & Airdrop Framework

Controlled framework for preparing, validating, funding and activating future Vitality claim and airdrop campaigns.

**Status: INFRASTRUCTURE / NO PUBLIC CLAIM IMPLIED**

Vitality has prepared campaign and claim infrastructure so future distributions can be built deterministically and reviewed before activation.

## Framework components

The campaign framework may include:

* allocation-manifest schema;
* deterministic campaign identifiers;
* Merkle-root and proof generation;
* local proof verification;
* integrity hashes;
* campaign preflight checks;
* distributor configuration;
* funding and reconciliation;
* campaign-specific module approval;
* public activation records.

## Activation sequence

A future Merkle-based claim should normally progress through:

```
Rules approved
→ allocation manifest finalized
→ proofs generated and validated
→ campaign created
→ campaign funded
→ funding reconciled
→ Merkle root configured / locked
→ claim module approved
→ campaign activated
→ public status record published
```

None of these intermediate steps alone means a public claim is open.

## Multi-reward framework

Campaigns are not limited to VTY. Depending on purpose and approved rules, a campaign may use VXP, CHI, NFTs / collectibles, access benefits or a governed VTY allocation.

## Public boundary

A user should only consider a campaign live when the official current-status page identifies the campaign, network, contract / campaign ID, opening time, closing time, eligibility source and transaction path.

No screenshot, social post or deployed distributor contract substitutes for that live-status record.