How do I snapshot NFT holders for a token airdrop?

Snapshot Mechanics and Timing

1. A snapshot captures the on-chain state of wallet balances at a specific block height, not a calendar time. This ensures immutability and eliminates manipulation windows.

2. Projects typically announce the target block height in advance, often selecting a block that falls during low-network congestion to minimize transaction inclusion variance.

3. Only wallets holding the qualifying NFT at that exact block are eligible—transfers before or after have no effect on eligibility status.

4. The snapshot does not record wallet activity history; it records only the presence or absence of ownership at that singular point in the Ethereum or Solana ledger.

5. Multi-signature wallets and contract-owned addresses require explicit whitelisting if they hold qualifying NFTs, as standard snapshot tools may misclassify them as non-human entities.

On-Chain Address Clustering Considerations

1. Heuristic clustering identifies address relationships through shared behaviors: repeated deposit patterns into centralized exchanges, coordinated token airdrop receipt across multiple wallets, or self-authorization sequences across contracts.

2. Over 10% of observed NFT holder entities control more than one address, meaning unclustered snapshots risk double-counting or missing linked accounts.

3. Wallets exhibiting identical gas fee patterns across multiple NFT mints within a 60-second window are flagged for potential sybil analysis prior to final airdrop distribution.

4. Clustering results feed into entity-level filtering—airdrops can be restricted to one per verified human entity rather than one per wallet.

5. Social account tag libraries and NFT marketplace interaction logs are cross-referenced with on-chain clusters to resolve ambiguous ownership claims.

Wallet Compatibility and Mapping Requirements

1. EOS-based airdrops require pre-mapped wallets using compatible versions like imToken 1.42; unmapped exchange-held EOS balances are excluded regardless of quantity.

2. Mapping involves generating an EOS public/private key pair and invoking a dedicated smart contract—this step is irreversible and must precede the snapshot block.

3. Private keys generated during mapping must be backed up offline; digital storage introduces compromise vectors that invalidate future airdrop claims.

4. Wallets supporting EVM-compatible chains must verify support for the specific token standard (ERC-721, ERC-1155, SPL) used by the qualifying NFT collection.

5. Hardware wallet users must confirm that their device firmware supports the chain’s signature scheme and that the connected interface correctly parses NFT ownership data.

Eligibility Thresholds and Verification Layers

1. Minimum holdings thresholds—such as 100+ EOS tokens—are enforced at the snapshot block and applied before any clustering logic.

2. Wallets flagged for suspicious behavior—including rapid mint-and-flip sequences across generative art projects—are excluded from airdrop lists even if technically eligible.

3. Airdrop contracts validate NFT ownership via on-chain ownerOf() calls rather than relying solely on event logs, preventing spoofed transfer events from granting false eligibility.

4. Projects using off-chain KYC layers apply verification status retroactively to snapshot results, allowing selective exclusion without altering on-chain eligibility criteria.

5. Token-gated access to claim interfaces requires successful resolution of both on-chain ownership and optional identity attestation proofs.

Frequently Asked Questions

Q: Can I move my NFT after the announced snapshot block but before claiming?Yes. Ownership at the snapshot block locks eligibility; subsequent transfers do not revoke airdrop rights unless the project explicitly enforces post-snapshot holding requirements.

Q: Do wrapped NFTs count toward eligibility?No. Wrapped representations—such as ERC-20 wrappers for ERC-721 assets—are not recognized as native ownership during snapshot validation unless the wrapping contract is explicitly whitelisted and integrated into the eligibility oracle.

Q: What happens if my wallet holds the NFT in a nested contract like a vault or DAO treasury?Eligibility depends on whether the snapshot tool traverses contract call stacks to identify ultimate beneficial owners. Most default tools treat such holdings as ineligible unless manually verified and whitelisted.

Q: Are gas fees required to receive the airdropped tokens?Receiving tokens incurs no gas cost if the airdrop uses a pull-based model where recipients initiate the transfer. Push-based models require the project to pay gas, but may impose claim deadlines or revocation clauses.