LogoLogo
  • Introduction
  • For Founders
    • TokenTable Airdrop Pro
    • TokenTable Airdrop Lite
      • Getting Started
      • Set Up the Project
      • Deposit Tokens
      • Publish the Project
    • TokenTable Unlocker
    • Custom Token Claiming Portal
  • For Token Recipients
    • Airdrop Token Claiming
    • Unlocker Token Claiming
  • For Developers
    • Airdrop
      • EVM
      • TON
        • Getting Started
        • Architecture
        • Usage
        • Smart Contract Schema
        • Integration
    • Unlocker
      • EVM
        • APIs
          • Core
            • Unlocker
              • Data Models
            • FutureToken
            • TrackerToken
          • Utilities
            • Deployer
            • External Hook
            • Fee Collector
            • Versionable
        • SDK
      • Starknet
  • SUPPORT
    • FAQ
    • Feedback and Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. For Developers

Airdrop

PreviousUnlocker Token ClaimingNextEVM

Last updated 4 months ago

Was this helpful?

TokenTable Airdrop empowers users to distribute tokens at a massive scale with powerful optional vesting rules, access control rulesets, and optimized gas cost (e.g. sharding for TON).

How Does Airdrop Work?

At its core, TokenTable Airdrop uses merkle trees to enable constant-cost token distributions and vesting rules. If a token allocation needs to be split across 6 calendar months to claim, we simply process and pre-split the data into 6 calendar months when generating the merkle tree. As a result, said allocation actually consists of 6 leaf nodes and are treated as 6 separate claims to the smart contract. Our frontend then abstracts this technical detail away, providing users with a smooth experience. Access control rulesets can be implemented via an external hook contract that's called when a claim is made and reverts when certain conditions fail, similar to the one found . We also use this mechanism to charge fees for token claims.

When the recipient claims their token allocation, a merkle proof is generated by our backend that's then fed to the smart contract. Note that although we generate the proofs, the smart contract ownership itself is assigned to the project owner and there is nothing we can do to assert control over the smart contract.

here
An overview of the Airdrop workflow