LogoLogo
Go to SiliconJoin Telegram 💬
  • About
    • Silicon Overview
      • Features
      • Missions
    • Silicon identity protocol
  • Users
    • Wallet configuration
    • Bridge
      • Deposit to Silicon
      • Withdrawal from Silicon
    • Block explorer
    • Fees
  • Builders
    • Build on Silicon
    • Build on OpenCohort & NamedWallet
      • Contract
        • OpenNameTag
        • Account Abstraction
      • Framework
        • Merkle Tree & Merkle Proof
        • Participants
        • Components Overview
        • Address & Identity
        • Use Case
        • Developer
          • Cohort
          • Protocol
            • Base API
            • Manage API
            • Prover API
          • Airdrop
            • Reward Type
          • Play OpenCohort
          • Named Wallet
        • Public Prover Lists
    • Network information
    • zkEVM contracts
    • Testnet
      • Setup
      • Faucet
      • Bridge
      • Block Explorer
      • zkEVM Testnet Contracts
  • Support
    • Contact Silicon
    • Silicon quick guide
  • More
    • Brand
    • Security
    • Terms of use
    • Privacy Policy
    • Open Source License
  • External Links
    • Polygon CDK
    • Polygon zkEVM
  • Agglayer
Powered by GitBook
LogoLogo

Sites

  • Silicon
  • Scope
  • Bridge

Community

  • X
  • Medium
  • Telegram

Developers

  • Testnet Scope
  • Testnet Bridge

Copyright Silicon(Highdraw). All Rights Reserved.

On this page
  • Weight
  • Count
  • Constant
  • Unit

Was this helpful?

  1. Builders
  2. Build on OpenCohort & NamedWallet
  3. Framework
  4. Developer
  5. Airdrop

Reward Type

This page outlines the amount receivable for each of the four RewardTypes supported by Airdrop in OpenCohort.

Weight

  • Calculated based on the same snapshot.

  • Token amount receivable: (Recipient’s weight within the snapshot) / (totalWeight of the snapshot ) * (totalAmount of airdropped tokens)

  • Total eligible recipients: totalCount of the snapshot (all Merkle Tree leaves)

Count

  • Calculated based on the same snapshot.

  • Token amount receivable: (totalAmount of airdropped tokens) / (totalCount of the snapshot)

  • Total eligible recipients: totalCount of the snapshot (all Merkle Tree leaves)

Constant

  • Calculated based on the same snapshot.

  • Token amount receivable: A fixed amount of amountPer for each recipient

  • Total eligible recipients: Up to totalAmount / amountPer of the first Merkle Tree leaves are eligible to receive tokens.

    • The first totalAmount / amountPer leaves in the Merkle Tree

  • If the total number of cohort users is smaller than totalAmount / amountPer, then effectively every user receives tokens, making it function similarly to the Count type.

Unit

  • Calculated based on each user's activity (weight) in the latest snapshot.

  • Token Amount Receivable: Users receive tokens in "amountPer" units based on their weight in the snapshot.

    • (amountPer of the Airdrop) * (Recipient’s weight within the snapshot)

  • Total Eligible Recipients: Determined on a first-come, first-served basis, but the exact number of eligible recipients isn’t fixed.

    • Total receivable weight: (totalAmount of airdropped tokens) / amountPer

  • In this type, if a user’s weight increases, they may claim additional tokens according to their added weight*amountPer.

  • However, if a user’s weight decreases, it does not reduce their previously claimed amount.

PreviousAirdropNextPlay OpenCohort

Last updated 6 months ago

Was this helpful?