Skip to content

Trustless Airdrop Launchpad

Problem

Airdrops are a common way for protocols to reward contributors and bootstrap communities — but today’s designs often require blind trust.

On the creator’s side, indexing eligible users typically happens in a centralized backend. On the user’s side, there’s no guarantee the indexing was done correctly — insiders could be added, or legitimate contributors could be excluded. Without verifiable proofs, eligibility remains a matter of trust.

Solution

The Trustless Airdrop Launchpad leverages the GitHub Prover to make eligibility provable and verifiable by anyone.

Instead of trusting an airdrop creator’s backend, claimants generate a zero-knowledge proof — on their own device — showing that they meet the eligibility criteria (e.g., “I have more than N contributions to repo X”). The proof is based on a cryptographically certified GitHub API response, so the airdrop contract can verify it without contacting GitHub or trusting the creator.

For Airdrop Creators

Creators can launch a campaign through our interface, which deploys a dedicated Airdrop contract using our AirdropFactory. Each campaign specifies:

  • The token to distribute
  • The treasury address
  • Rewards per contribution
  • The verifier contract to check proofs

For Airdrop Claimants

Claimants use a dedicated interface to:

  1. Fetch their GitHub contribution data through the GitHub Prover.
  2. Generate a zero-knowledge proof of eligibility locally.
  3. Submit the proof to the airdrop contract.

If the proof is valid, tokens are released automatically — no centralized validation step required.

Contracts Design

Contracts diagram

  • Per-campaign contracts: Each airdrop runs on its own deployed contract with fixed parameters.
  • Commit–Reveal scheme: Protects against front-running by requiring claimants to first commit a hash of their proof before revealing it.

By building on zkTLS-based certification and client-side proving, the Trustless Airdrop Launchpad removes the need to trust an off-chain server, ensuring that rewards go only to provably eligible participants.