A snapshot is a record of blockchain activity or holdings at a specific block height or point in time, used to decide who qualifies for an airdrop and how much each person receives. Projects take snapshots because they need a fair, verifiable cutoff: instead of rewarding anyone who acts after an announcement, they reward people who were already using the protocol or holding an asset before that moment. Understanding snapshots is therefore essential for anyone hoping to qualify for retroactive distributions.

Snapshots can capture different things depending on the project's goals. Some record token balances at a moment, rewarding holders; others record transaction history over a period, rewarding active users; and some combine both, rewarding holders who also used the product. The criteria are defined by the project, often published in an announcement or documentation, and they may include minimum balances, minimum activity, or exclusion rules for certain types of addresses, such as exchange wallets or known sybil clusters.

Timing is where beginners most often lose eligibility. If a snapshot is announced in advance, activity after the announcement but before the snapshot may still count, but activity after the snapshot cannot change a record that has already been taken. Conversely, if a snapshot is retroactive and unannounced, only past activity counts, and trying to qualify after the announcement is too late. That is why consistent, genuine usage over time matters more than rushed activity after an airdrop is announced.

Moving assets at the wrong time can also affect eligibility in subtle ways. Transferring tokens to a new wallet shortly before a snapshot, bridging assets to another chain, or holding assets on an exchange instead of a self-custody wallet can all change whether and how you are recorded, depending on the project's rules. Some projects explicitly exclude exchange addresses because they cannot identify individual holders, while others include them through exchange partnerships, so check the rules rather than assuming your holdings will be counted wherever they sit.

Minimum thresholds and activity filters are common and often misunderstood. A project may require a minimum balance, a minimum number of transactions, activity across multiple months, or interaction with specific features, and failing any one filter can exclude an otherwise active user. Those filters exist to reduce sybil farming and reward genuine users, but they also mean that a single transaction, or a tiny balance held briefly, rarely qualifies on its own, however enthusiastic the user may be.

Checking eligibility, when a checker is available, should be done through official channels only, by entering a wallet address without signing transactions or connecting a main wallet. If you qualify, note the allocation, claim window, and any vesting or lock-up terms, because some airdrops distribute immediately while others vest over months. If you do not qualify, treat that as information about the project's criteria, not as a reason to rush into artificial activity for the next snapshot, which filters are designed to detect.

The practical lesson of snapshots is to behave like a genuine, long-term user of protocols you actually value, keep assets in wallets you control where possible, and document your activity in a simple record. That approach will not guarantee any specific airdrop, because projects set their own rules and change them, but it positions you fairly for retroactive rewards without encouraging the rushed, artificial behaviour that snapshots and sybil filters are built to exclude. Patience and consistency beat last-minute scrambling every time.

One practical snapshot habit is to keep a simple dated log of your significant on-chain activity, noting when you acquired, moved, or staked major assets, so you can later understand why a snapshot did or did not include you. That log also helps with tax records and portfolio reviews, turning snapshot awareness into general good record-keeping. Over time, the log reveals your own patterns, such as holding assets on exchanges during key periods, and lets you adjust future behaviour deliberately rather than discovering eligibility rules only after a snapshot has already been taken.