feature(smart-contracts): Airdrops

[0xTxbi]

Description

This PR introduces a smart contract for managing token airdrops with a two-step verification process. Recipients must first sign the Terms of Service (TOS) for each campaign and then provide a valid Merkle proof to claim tokens. The contract supports multiple airdrop campaigns, each with its own TOS and Merkle tree of eligible recipients. It tracks TOS signatures and claimed tokens to ensure secure and compliant distribution.

Issues

Fixes #
Refs #15541

Checklist:

• 1 PR, 1 purpose: my Pull Request applies to a single purpose
• I have commented my code, particularly in hard-to-understand areas
• I have updated the docs to reflect my changes if applicable
• I have added tests (and stories for frontend components) that prove my fix is effective or that my feature works
• I have performed a self-review of my own code
• If my code involves visual changes, I am adding applicable screenshots to this thread

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
unlock-airdrops	⬜️ Ignored (Inspect)	Visit Preview		Feb 26, 2025 4:28pm
unlock-static-site	⬜️ Ignored (Inspect)			Feb 26, 2025 4:28pm
unlock-storybook	⬜️ Ignored (Inspect)			Feb 26, 2025 4:28pm

[julien51]

Trees a good first start! Please add tests! Also I forgot but we need an extra feature: a blocklist and the ability to add to BlockList by the contract owner!