How launchpads filter sybil attackers wallet age activity and snapshots
Launchpads face a straightforward problem: they want to distribute tokens to real humans, not to one person controlling a hundred wallets. The solution is a set of technical filters that make sybil attacks expensive and detectable.
Wallet age is the first filter. Most launchpads require an account to have been created at least 30 days before a sale; some push that to 90 days. The reasoning is simple. Creating a thousand fresh wallets in an hour is trivial. Making them all appear six months old requires patience a sybil attacker usually lacks.
Activity requirements go further. A wallet that sits empty for months then receives funding days before a sale looks suspicious. Launchpads look for transaction history - deposits, swaps, or interactions with other protocols. The threshold varies. Some require ten transactions; others look for a minimum total volume.
The timing of activity matters as much as its existence. A wallet that shows a burst of qualifying trades in a single week before a snapshot raises a flag. Legitimate users accumulate gradually, while sybil wallets often show patterns that cluster in time.
Snapshot timing is a critical variable. Launchpads take a snapshot of eligible wallets at a specific block, and that block is not announced in advance. If attackers knew the exact block, they could fund enough wallets just in time. By randomising the snapshot within a window, launchpads eliminate that workaround.
Some platforms use multiple snapshots. They might take one at announcement, another at the end of a staking period, and a third just before the sale. A wallet that appears in the first but not the second loses eligibility. This catches people who borrow funds temporarily to pass one check.
Merkle proof verification is the cryptographic layer. After all filtering, the launchpad generates a Merkle tree of eligible addresses, and each address gets a unique proof. To claim an allocation, you submit that proof on-chain. The contract checks it against the stored root. If your address is not in the tree, no transaction can force it in.
This method prevents last-minute manipulation because the Merkle root is fixed before claims open. No one can add wallets after the fact. The proof also keeps the list size off-chain, so a sale with ten thousand participants doesn't bloat the contract.
The commit-reveal mechanism defends against front-running. In a commit-reveal scheme, participants first submit a hash of their intended contribution - that hash commits them to a specific amount without revealing it. Later, they reveal the actual value, and the contract checks that it matches the hash.
Why does this matter? Without it, a front-runner watches the mempool for transactions. If they see a large contribution coming, they can submit an even larger one at a higher gas price, jumping ahead in the block. With commit-reveal, no one knows your contribution until after the commit window closes, and the attack path disappears.
The tension between sybil resistance and accessibility is real. Strict filters exclude genuine new users. A person who just created their first crypto wallet cannot meet a 90-day age requirement and might not have ten transactions yet.
Some launchpads address this by offering tiered eligibility. A base allocation requires no history; a larger allocation requires more proof of activity. This lets newcomers participate at a minimal level while rewarding established users.
Others use proof-of-personhood systems, which require users to verify they are human through a third-party identity check. That introduces privacy tradeoffs and centralisation risks. The sybil resistance improves, but the user now trusts the identity provider.
There is no perfect solution. Every filter catches some legitimate users. Every open door lets in some attackers. Launchpads balance these tradeoffs based on their goals: a project that values broad distribution uses lighter filters, while a project that wants to reward loyal supporters uses heavier ones.
The technical details matter less than understanding the incentives. Sybil resistance is an arms race. As filters improve, attackers develop new strategies. As of August 31, 2026, the methods described here represent current practice. That will change.
Not financial advice. flovicommunity.com 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.