Verify the airdrop through official project sources, confirm that your account is eligible, and read the claim instructions before connecting or signing. Inspect the requested contract, permissions, and fee. A free allocation can still involve network costs, and an unexpected token is not proof of a legitimate claim.

Authenticate the campaign independently

Start with an official project announcement reached through a known domain or independently verified documentation. Compare the claim URL with the announced destination. A direct message, sponsored result, or token description can point to an impersonator.

Check that the announcement concerns the correct distribution round, network, eligibility period, and deadline. A genuine historical campaign can be copied into a fraudulent current claim page. Old branding does not establish that claims remain open.

Identify whether the campaign requires a manual claim or distributes automatically. If no manual action is required, an unsolicited request to sign for release deserves investigation. Follow the actual delivery model rather than a generic airdrop tutorial.

Do not treat a large portfolio valuation as proof of value. Unknown tokens can carry misleading prices or names designed to lead holders to a website. Research the exact contract before trying to sell or redeem an unexpected asset.

Verified campaignReviewed requestConfirmed allocation
Verify the campaign before authorizing its specific request, then confirm the actual allocation from the resulting record.

Review your allocation before authorizing it

Use the campaign's documented eligibility method for the intended public address. If a read-only address lookup exists, it can answer the eligibility question without signing an asset-moving transaction.

An eligible status, a displayed allocation, and a completed claim are different milestones. Read whether tokens become immediately available, vest over time, or require further conditions. An allocation number alone does not establish a spendable wallet balance.

If identity or regional conditions apply, verify the official process and the entity requesting information. Never supply a wallet recovery phrase to establish entitlement. Control of a public address can be checked through appropriate mechanisms without giving away the underlying secret.

Read the economic terms. A governance delegation or other action can form part of a campaign, but it needs an explicit explanation. Do not assume every requested permission is necessary merely because the button says Claim.

Inspect the wallet request

  1. Open the official claim interface and confirm the account and network. Compare the selected public address with the one checked for eligibility.
  2. Read the next request's type. A connection, message signature, token approval, and execution transaction can have different effects.
  3. Inspect the contract or spender and the assets involved. A request for broad access to unrelated holdings needs a clear, verified explanation before you proceed.
  4. Check the network fee and any legitimate conditions stated in the campaign documentation. A payment demanded by a private contact is not established by a claim-page logo.
  5. Read warnings or simulation results and resolve unexplained behavior. Reject a request you cannot connect to the stated claim.
  6. After authorizing, retain the transaction or claim reference and inspect its final result. Do not repeat the operation solely because the page has not refreshed.

Understand the cost of trying

A manual on-chain claim can consume the network's fee asset. Confirm the balance needed on the actual network. A fee estimate from another chain or an old screenshot is not the budget for the current request.

If you must move funds or use a bridge to obtain that fee asset, include those steps in the cost. Some claims can use sponsorship or a different payment design, but that must be documented and visible in the actual flow.

An executed transaction can fail and still incur costs. Repeatedly signing the same failing request is not an effective diagnosis. Inspect the status and error before trying again.

Compare the prospective allocation with the full cost and the terms of receipt. A token may have limited liquidity or transfer restrictions. You do not need to claim every distribution simply because an address is eligible.

Keep estimated market values separate from realized proceeds. A token amount displayed by a campaign is more concrete than an assumed sale value based on a thin or unrelated market.

If tokens do not appear after a claim

Open the transaction record on the correct network. Check whether the action succeeded and whether the allocation went to the expected address. A message signature alone may not have completed an on-chain delivery.

If a vesting arrangement was involved, find the position or claim schedule described by the project. Do not expect an immediate transferable balance when the official terms specify another representation.

If the expected token reached your account but is absent from the interface, verify its contract and use the wallet's supported display function. Adding a display entry cannot create a missing allocation.

If the claim remains pending, inspect that request rather than submitting multiple new transactions. Where a project has an official support process, provide public identifiers and the exact stage you reached.

Preserve the announcement, domain, account, network, and references if the outcome conflicts with the terms. These establish what you relied on without exposing private recovery information.

If you suspect the page was malicious

Stop creating new approvals or payments. Distinguish an exposed connection from a signed permission or an exposed recovery phrase, because each creates a different problem.

Disconnecting a site does not automatically revoke token allowances. Inspect permissions using the wallet's official guidance and verified tools. If a secret key or recovery phrase was disclosed, changing a connection setting does not make it private again.

Save the relevant domain and transaction hashes for reporting. Use the wallet, platform, or network's official incident guidance rather than accepting unsolicited recovery help.

An unexpected token appearing in your account does not by itself prove that all funds are compromised. The dangerous step may be a later interaction. Establish what was actually signed or disclosed before selecting a response.

The claim task ends when the official allocation and its conditions are understood and the authorized result has been verified. A successful claim is a specific delivery outcome, not a reason to trust every future message using the same project name.

Before a claim, write down the expected change in your wallet. Identify which asset should arrive, whether any existing asset should leave, and what permission should remain afterward. Compare that expectation with the wallet preview. A claim that unexpectedly authorizes spending of another holding needs investigation even when the interface promises a reward. This simple comparison turns the word Claim into a specific action that you can evaluate rather than a general invitation to approve.

Reader questions

Should I enter my recovery phrase to prove eligibility?

No. Eligibility checks and claim authorization should not require disclosing the secret that recreates the wallet.

Does receiving an unsolicited token mean I already claimed it?

Not necessarily. Tokens can be sent directly to public addresses, including as spam. Verify the campaign and contract independently.

Can an airdrop page guarantee what the token will sell for?

A claimed amount does not establish future price or available liquidity. Treat any sale estimate as a separate question.

Sources and further reading