Facing an "airdrop no people found" message can be confusing, especially when you are certain the recipient should be eligible. This status typically indicates a technical mismatch rather than a reflection of the recipient's value or your campaign's validity. Understanding the specific conditions that trigger this response is the first step to resolving the issue and successfully delivering your reward.
Decoding the "No People Found" Status
The phrase "airdrop no people found" appears when the distribution protocol fails to identify a qualifying wallet address within your target parameters. Unlike a simple delivery failure, this message suggests the filtering criteria were so strict that the system could not locate a single match. This often occurs when the requirements for token eligibility, such as a minimum balance or specific NFT ownership, are not met by any address in the designated list.
Common Triggers for This Error
Snapshot timing mismatches with the current blockchain state.
Incorrect configuration of wallet address filters.
Outdated or zero balance data at the time of snapshot.
The Role of Snapshot Data
Airdrops often rely on historical blockchain data, or a snapshot, to determine eligibility. If the snapshot was taken too long ago, the balances or NFT holdings of qualifying users may have changed. A user who held the required tokens at the time of the snapshot might have since moved or swapped their assets, resulting in an "airdrop no people found" result when the transaction was executed.
Troubleshooting Distribution Settings
Reviewing your smart contract or distribution platform settings is crucial. A misconfigured filter, such as an excessively high minimum token threshold, can exclude all participants. Verifying that the contract is interacting with the correct blockchain network and that the token address is accurate will eliminate many common sources of this error.
Network and Synchronization Issues
Blockchain networks experience varying levels of congestion. If the airdrop transaction was sent during a period of high gas fees or low block space, it might have been stuck in the mempool. Additionally, if your node or RPC provider is not fully synchronized, it may fail to recognize the most recent state of the blockchain, leading to the inability to locate eligible recipients.
Ensuring Future Success
To prevent this issue in future campaigns, conduct a test airdrop with a small group of known wallets. This allows you to verify the logic of your filters and the accuracy of your snapshot data. Maintaining clear communication with your community about eligibility criteria and timing also helps manage expectations and reduces support overhead.
