← back to blog

Do failed and reverted transactions still count toward airdrop eligibility?

Anyone who has spent real time interacting with testnets, bridges, or new L2s has watched a transaction fail. The wallet still gets charged gas, the block explorer shows a red “failed” tag, and the question that follows is always the same: does that transaction do anything for eligibility, or was the gas just burned for nothing?

The honest answer is that it depends on what a project is actually measuring, and that measurement is never disclosed in advance. But the mechanics of what a failed or reverted transaction actually is, and what it leaves behind on-chain, are not a mystery. Understanding that mechanism is more useful than guessing at any specific project’s snapshot rules.

Failed and reverted are not the same event

These two terms get used interchangeably, but they describe different things at the protocol level.

A reverted transaction is one where the EVM executed the call, hit a condition that failed (an assertion, a require statement, insufficient balance, slippage tolerance exceeded, an out-of-gas error mid-execution), and rolled back all state changes. The transaction is still mined. It still consumes gas up to the point of failure. It still gets a transaction hash and a permanent slot in a block. The only thing that “reverts” is the state change the transaction was trying to make, not its existence in the chain’s history.

A failed transaction in the colloquial sense usually means the same thing: it made it into a block but the execution status field is set to 0 instead of 1. Explorers like Etherscan display this as “Fail” or “Failed” in the transaction list. There’s a separate, rarer case where a transaction never makes it into a block at all, for example if it’s dropped from the mempool because the nonce was replaced or the gas price was too low to be included. Those transactions don’t exist on-chain in any permanent form. There’s nothing for anyone to count, because there’s no record.

The distinction matters because “on-chain but reverted” and “never confirmed” are treated completely differently by anyone reading chain data, whether that’s an airdrop team’s snapshot script or a clustering tool.

Why a reverted transaction still costs money

The EVM charges gas for computation that already happened, not for computation that succeeds. If a swap reverts because slippage exceeded the tolerance set, the wallet still paid for the gas used to load the pool state, run the router logic, and hit the revert condition. Only the last step (actually moving tokens) didn’t happen. This is why “failed transaction, gas spent” is such a common and irritating experience: the chain doesn’t refund effort, only unused gas limit.

This matters for the eligibility question because it means a reverted transaction is not free from the wallet’s perspective, and it is not invisible from the chain’s perspective. It’s a real, indexed, permanently retrievable event tied to a specific address, block, and timestamp. Anything that queries transaction history by address will see it, whether or not that querying tool chooses to act on it.

How airdrop criteria usually handle this

Projects that run point systems or eligibility snapshots build their own indexing pipelines, and those pipelines almost always filter by execution status. The overwhelming default is to only count transactions where status == 1, meaning successful execution. This isn’t a courtesy to farmers, it’s just the sane way to measure actual usage of a protocol. If the goal of an airdrop is to reward people who bridged assets, provided liquidity, or made trades, then a transaction that reverted before doing any of those things didn’t produce the activity being measured. Counting it would reward noise.

There are a few situations where failed transactions can still matter indirectly, even if they don’t count as “activity” themselves:

  • Interaction count metrics. Some criteria look at “number of transactions sent to this contract” rather than “number of successful state changes,” particularly for simpler point systems built quickly. This is uncommon for anything with real funding behind it, but it happens on smaller or newer programs.
  • Gas spent as a proxy for engagement. A handful of programs have weighted total gas paid to a protocol’s contracts as part of a scoring formula. A reverted transaction still burns gas, so in that specific model it could contribute, even with zero successful outcome.
  • Wallet age and transaction count as a Sybil filter, not a reward metric. This is the most common place failed transactions actually show up. A project isn’t rewarding the failed transaction, but it is looking at total transaction count (successful or not) as one signal for whether an address looks like a real, aged wallet versus a bot spun up the week before a snapshot.

None of this is a guarantee. Every program sets its own rules, most don’t publish the exact query logic before the snapshot, and some change scoring after the fact. Nothing here should be read as a claim about how a specific airdrop will actually score anyone’s history.

What failed transactions reveal to chain analysis

This is the part that’s more consistently useful than guessing at eligibility formulas. Chain analysis firms and in-house Sybil detection teams don’t care whether a transaction succeeded when they’re building wallet clusters. They care about patterns.

A batch of wallets that all send a transaction to the same contract, in the same block range, using gas prices within a tight band, funded from the same source address, and hitting the same revert condition at the same execution step, is a very clean cluster signal. It doesn’t matter that none of those transactions moved any tokens. The pattern is in the timing, the funding graph, and the behavioral fingerprint, not in whether the call succeeded.

This is worth internalizing for anyone running more than one wallet: a failed transaction is not a “free” or “invisible” action just because it didn’t change any balances. It’s still a fully-formed data point with a sender, a nonce, a gas price, a target contract, and a timestamp. If a script is retrying the same failed call across many addresses in a loop, that retry pattern is itself a signal, sometimes a stronger one than a single successful transaction would have been, because organic users rarely fail the same call in the same way at the same time.

What this means for how wallets should be operated

None of this changes the basic logic of running wallets defensively. Funding sources, timing spread, gas price variance, and independent RPC or proxy paths per wallet matter regardless of whether a given transaction on any one wallet succeeds or reverts. A failed transaction doesn’t get a pass from clustering just because it produced no state change, and it doesn’t get counted toward eligibility just because it cost gas.

The practical takeaway is to treat every transaction, successful or not, as a permanent, attributable record, and to build wallet operations around that assumption rather than around what any single project’s snapshot script might or might not count. Testing new contract interactions on a small number of wallets before scaling activity across many addresses also has a side benefit here: it surfaces revert conditions (wrong approval amount, wrong chain, stale calldata) before they get repeated at scale across a whole set of wallets, which keeps both gas waste and behavioral fingerprinting down.

Failed and reverted transactions are real, permanent, and readable by anyone querying the chain. Whether they help with a specific airdrop is up to that project’s own criteria, which is rarely public in full before the snapshot. Whether they hurt with clustering depends far more on the pattern across a wallet set than on any single transaction’s outcome.

For more breakdowns like this, along with tested reviews of the wallets, RPC providers, and anti-detect tools used to run airdrop farming as an actual operation rather than a guessing game, head back to the homepage.

Get new guides and videos first — join the Telegram channel.

need infra for this today?