A security-first airdrop farming checklist for daily work

Open projects from bookmarks or official documentation instead of clicking unsolicited messages. Confirm the domain character by character, check whether the announcement is current, and compare the requested action with the project primary source.

Review which wallet and network the task is meant to use. Keep long-term storage separate from experimental activity, and do not keep more value in an activity wallet than you are prepared to expose to protocol and approval risk.

• Confirm the official domain and current announcement.
• Check the wallet label and selected network.
• Review gas and bridge costs before starting.
• Stop if the task asks for a seed phrase or private key.

Read the wallet prompt rather than treating it as a login button. A message signature, token approval, permit, asset transfer, and contract interaction have different consequences. If the request does not match the action described by the project, reject it and investigate.

For approvals, verify the token, spender, amount, and network. Unlimited allowances can remain active after the campaign task is finished. Use an appropriate explorer or approval-management tool to review permissions independently.

• Match the wallet prompt to the intended action.
• Inspect spender and allowance details.
• Avoid urgency-driven signing and copied links.
• Never share a recovery phrase with support staff.

Save the transaction reference when it helps you verify the outcome, but do not paste secrets or authentication tokens into notes. Check the status on the relevant explorer or official application before marking the wallet-task cell Done.

If the transaction is submitted but unresolved, mark it Pending. If it failed or the result differs from what you expected, mark it Failed and pause related actions until you understand the cause.

Review pending and failed items while the context is still fresh. Close unnecessary tabs, disconnect active sessions where appropriate, and note any requirement that needs confirmation from an official source.

Do not use completion percentage as a reason to finish a questionable task. An accurate incomplete record is more useful than a full checklist produced by unsafe or unverifiable actions.

• Recheck unresolved transactions.
• Record why a task was skipped or failed.
• Review new approvals created during the session.
• Archive links that are no longer official or current.

Compare recurring tasks with current project documentation. Requirements, endpoints, and campaign dates can change, so a saved task should never override the primary source. Archive inactive projects and remove data that is no longer needed.

Review wallet separation, active token approvals, browser extensions, and device updates. This broader maintenance is outside the task tracker, but it affects the reliability of every status you record.

Create recurring review tasks such as Verify official announcement, Review pending transactions, and Check active approvals. Assign them only to the wallet context where they apply, and use notes for a short verification result rather than sensitive data.

The workflow guide shows how to translate requirements into specific tasks. The multi-wallet feature guide explains how to keep address context separate when the same campaign is tracked across several wallets.

A useful safety checklist includes reasons to stop, not only actions to complete. Decide in advance that you will pause when the official source is unavailable, the domain differs from your verified bookmark, the wallet prompt requests an unexpected permission, fees exceed your planned budget, or the transaction result cannot be explained. Recording a skipped task is better than improvising under time pressure.

If another person or community post recommends an urgent action, treat that message as a lead to investigate rather than authorization to sign. Return to a primary source using a separate navigation path. Screenshots and copied announcements can be altered or outdated, so compare the live publication date and destination domain.

• Reject any request for a seed phrase, private key, or recovery code.
• Pause when the requested network, contract, or spender is unexpected.
• Keep Failed or skipped status visible until you understand the cause.