How Can You Use a CSV File to Claim an Airdrop Without Exposing Your Main Wallet?
A CSV file by itself cannot claim an airdrop. What the question usually refers to is using a Merkle tree proof, often distributed as a CSV, to verify your eligibility without connecting your main wallet to a suspicious claim interface. The CSV contains the data needed to generate or validate a cryptographic proof that you are entitled to tokens, and you can submit that proof using a burner wallet or a read-only wallet connection, keeping your main wallet's private keys untouched.
What the CSV actually contains
When a project distributes an airdrop via a Merkle tree, it publishes a root hash on-chain. Each eligible address gets a "leaf" in that tree, which is a hash of the address plus the amount of tokens owed. The CSV file typically lists addresses and their corresponding amounts, along with a "proof" - a set of intermediate hashes that allow a smart contract to verify that the leaf belongs to the tree. Without the proof, the contract cannot confirm your eligibility.
The CSV itself is not executable code. It is data. You cannot paste it into MetaMask or sign it. You need to use it in a process that constructs a transaction.
The General Procedure
The exact steps depend on the airdrops/claim-airdrop-vs-automatic-distribution/">airdrop claim site and the tools it provides, but the logic is consistent.
1. Download the CSV from a Trusted Source
Only obtain the CSV from the project's official website or its verified GitHub repository. Scammers create fake CSV files that look identical but contain manipulated proofs that point to their own wallets. Cross-check the Merkle root hash against the one published on-chain via a block explorer.
2. Prepare a Burner Wallet
Create a fresh wallet with no funds you care about. Transfer a small amount of native gas token (ETH, MATIC, etc.) into it - just enough to pay the claim transaction fee. This wallet will be the one that actually connects to the claim interface.
3. Use a Read-Only Connection for Your Main Wallet
Some claim sites allow you to "check eligibility" by entering an address without connecting a wallet. If the site requires a wallet connection to check eligibility, use the burner wallet for that step too. Never connect your main wallet to any claim interface, even just to "check."
4. Construct the Claim Transaction Off-Chain
If the airdrop project provides a command-line tool or a web-based tool that accepts your CSV proof and your burner wallet address, use that to generate the raw transaction data. This tool does not need your private key - it only needs the proof from the CSV and the destination address.
5. Submit the Transaction via the Burner Wallet
Take the raw transaction data (usually hex-encoded) and broadcast it using the burner wallet. You can do this via a block explorer's "contract interaction" feature or a wallet like MetaMask on the burner account. The burner wallet signs the transaction, and the gas fee comes from its balance.
6. Verify the Tokens Arrive in Your Main Wallet
The claim transaction should send the airdropped tokens directly to the address you specified - your main wallet. If the claim contract is designed correctly, the tokens never pass through the burner wallet. Check the transaction on a block explorer to confirm the destination.
Why This Works
The Merkle proof does not require the claiming wallet to be the eligible address. The proof only demonstrates that some address (your main wallet) is entitled to tokens. The smart contract checks the proof against the on-chain root hash, then sends the tokens to the address specified in the claim transaction. As long as the proof is valid, the contract does not care which wallet submitted it.
The scam variant to watch for
Scammers distribute CSVs that appear to be Merkle proofs but are actually phishing payloads. A common trick is a CSV that contains an "import" link or instructions to "load this CSV into your wallet" - which is not a standard wallet feature. Any site that asks you to upload a CSV directly into your browser wallet extension or to copy-paste a "private key" from the CSV is a scam. The CSV is data for a tool, not for your wallet's seed phrase.
When this method is not possible
Some airdrop claim contracts require the eligible address to be the msg.sender - meaning the wallet that signs the transaction must be the same address that appears in the Merkle leaf. In that case, you cannot delegate the claim to a burner wallet. The only safe approach is to use a hardware wallet and carefully review the transaction before signing. If the project's documentation does not specify whether the claim contract supports delegation, assume it does not until proven otherwise.
Not financial advice. tilly-aidog.site publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.