How to check a possible claim safely
A contract can contain a claim function even when your wallet has no allocation. Use these steps to separate a lead from evidence about your wallet.
1. Start with the exact contract
Choose the blockchain and compare the full contract address with the project’s published address. A matching name is insufficient: unrelated contracts can share a name and similar function signatures. ClaimScanHQ’s feed checks small batches of publicly verified contracts, and its score rates patterns in their functions.
Functions such as refund, redeem, and harvest may be routine vault or application actions. They are lower-signal leads unless other evidence connects them to a public allocation.
2. Browse before sharing an address
You can inspect the contract and its public functions without a wallet address. If it exposes a read-only function that accepts an address, you can optionally enter your public address to see its response. Public addresses can reveal linked on-chain activity, so decide whether you want to provide one. ClaimScanHQ never needs a private key or recovery phrase.
A positive read-only signal can be incomplete; a zero or failed response can depend on missing project-specific parameters. When the contract offers no suitable function, eligibility remains unknown.
3. Verify the project’s rules
Find the project’s official claim announcement, required proof or allocation data, supported network, token address, and deadline. Use its official site or documented channels to confirm the destination and expected amount. A contract balance shows funds held by the contract, not funds owed to you; a wallet balance shows tokens already held, not a possible future payout.
ClaimScanHQ is read-only. It does not submit a claim or approve a token transfer. You can use it to investigate, then decide what to do through sources you trust.
Explore contract leads