Find the project's official distribution announcement and use its documented checker or eligibility rules for your public address. Confirm the campaign round, network, and snapshot period. An eligibility result describes that distribution; it does not guarantee future airdrops or require immediately signing a claim.

Find the authoritative rules for one distribution

Projects can distribute tokens using different criteria, including past activity, a particular holding, governance participation, or another documented contribution. Do not assume that activity valuable to one campaign qualifies for another.

Identify the round or distribution number and the official publication describing it. A search result can mix historical rules with speculation about future rewards. Record the date and whether the material is a final announcement or a proposal.

Look for the measurement period or snapshot. Activity after the stated cutoff may not affect that round. An account that currently meets a balance threshold may not have held it at the relevant time.

Some campaigns use points, exclusions, or anti-abuse adjustments. Arbitrum's published historical distribution specifications illustrate why a single visible action might not explain an allocation. Use such material as an example of method, not a statement that an old claim is currently open.

If rules remain unpublished, label the result unknown. A community spreadsheet or social post can suggest questions to investigate, but cannot establish an official entitlement.

Campaign rulesAddress evidenceEligibility result
Compare a specific campaign's rules with the correct address history before interpreting its eligibility result.

Select the address whose history matters

A wallet application can display multiple accounts, imported keys, hardware-linked accounts, and smart-contract wallets. Determine which address actually performed the qualifying action. The account currently selected may not be the one involved.

Check the network and the action's public record. A transaction on a different chain may not count under the campaign's definition. The same interface can route activity through different networks or contracts.

Custodial exchange activity often appears on-chain under infrastructure controlled by the provider. Buying or holding on an exchange does not automatically make your personal wallet address the holder measured by a project.

If a campaign supports delegates, linked accounts, or smart-contract accounts, read its specific treatment. Do not combine unrelated addresses into one presumed identity merely because you control them.

Keep address-level evidence in a private research note. A public address is not a secret key, but connecting it with your identity and activity can have privacy implications. Share only the information required for a legitimate support inquiry.

Use the checker with the least necessary authorization

  1. Reach the checker through an independently verified official announcement or project documentation. Inspect the domain and distribution round.
  2. Read whether a public-address lookup is supported. If so, enter the intended address rather than connecting an unrelated account.
  3. If a wallet connection is required, inspect the requested access. A connection and an asset-spending authorization serve different purposes.
  4. Record the displayed result, allocation, network, date, and any conditions. Mark whether the result is preliminary, final, claimable, or already distributed under the site's actual labels.
  5. Compare the result with the published rules and relevant address history. Keep unresolved differences as questions rather than assuming the checker or your interpretation must be correct.
  6. Do not sign a claim, pay a fee, or perform extra transactions merely to finish an eligibility check unless the official process clearly requires a separate action you understand.

Investigate a missing allocation systematically

First compare the address and round. Many apparent failures come from checking a different account or reading criteria from another distribution. Reopen the original announcement instead of repeatedly refreshing the same screen.

Next, compare timestamps with the eligibility period. A transaction can have been submitted before a cutoff but confirmed afterward. Read how the project defines the relevant activity and evidence.

Check the exact function or qualifying condition. A token approval is different from a swap, and an attempted transaction is different from a completed action. An application interaction can contain several steps, only some of which meet a rule.

Review exclusions and allocation formulas where published. Meeting one criterion may not establish the final amount. A project can include additional conditions in its distribution policy.

If an official appeal or correction channel exists, provide the address, relevant hashes, rule you believe applies, and observed result. Never provide a recovery phrase or private key to establish that public history.

If there is no published appeal process, do not invent one through a private helper offering guaranteed approval. Preserve the evidence and watch official updates rather than paying for an alleged manual allocation.

Separate checking from trying to qualify for a future reward

A project may explicitly state that past criteria do not guarantee future eligibility. Optimism's published airdrop material includes that distinction. Repeating historical tasks can cost money without establishing a future entitlement.

When someone promotes a farming checklist, identify which parts come from an official future policy and which are speculation. Costs can include network fees, swaps, bridging, time, and asset exposure. Keep those visible before considering any activity.

Do not manufacture volume or identity information to get around published rules. Aside from any platform restrictions, doing so makes your own cost and risk assessment depend on assumptions about screening you cannot verify.

A checker that asks for payment to reveal a guaranteed allocation should be evaluated against the project's actual rules. A public-address lookup and a claim transaction are different tasks, and a fee at one stage needs an explanation specific to that stage.

Keep an eligibility record that remains useful

Save the official rule source, campaign version, address, network, observed result, and supporting transactions. This allows you to revisit a result after an update without confusing it with another round.

If eligibility is confirmed, read the claim period and delivery terms separately. There may be a vesting schedule, governance action, or automatic distribution. Do not let a positive status rush you into a signature you have not inspected.

If eligibility is absent or uncertain, the practical result can be deciding not to spend more time or money on that round. A good check answers a defined entitlement question; it does not need to end with a transaction.

Before any later claim, verify the site again and review the actual wallet request. A previously genuine announcement cannot authenticate every future message using its logo or token name.

When sharing the result with someone helping you, identify the round and the source date. The same address can have different outcomes across separate distributions.

Reader questions

Can a checker determine eligibility from my email instead of a wallet?

It depends on the campaign's official method. Do not enter personal data unless the published process requires it through a verified channel.

Does transferring a token to a new wallet carry historical eligibility with it?

Only if the distribution rules say so. Many criteria concern an address at a past snapshot rather than the token's current holder.

Does a zero allocation mean my wallet is broken?

No. It can reflect criteria, exclusions, the selected address, or an unresolved checker issue. Wallet functionality is a separate question.

Sources and further reading