Introduction

Droppie is a no-code tool for launching Merkle-proof token airdrops on any EVM chain.

You bring an ERC-20 token and a CSV of recipients. Droppie builds a Merkle tree in your browser, has your wallet deploy a lightweight escrow contract for your campaign — you own it — and fund it with a single token transfer, then gives you one claim link to share. Recipients connect their wallet, prove they're on the list, and claim — each paying only their own small claim transaction.

No spreadsheet gymnastics, no multisend contracts, no paying gas for ten thousand transfers.

Why Merkle airdrops?

There are two ways to distribute tokens to a large list of addresses:

Push: send tokens to everyone

The classic "batch transfer" approach loops over the list and calls transfer for each recipient (directly or via a multisend contract). It works, but the creator pays for every single transfer:

• Each ERC-20 transfer to a fresh address costs roughly 30,000–60,000 gas.
• Cost scales linearly with list size: 10,000 recipients is on the order of hundreds of millions of gas — many ETH at mainnet prices, all paid up front by you.
• Tokens land in dead wallets, exchange deposit addresses, and contracts that can't use them. Once sent, they're gone.
• Large lists must be chunked across many transactions, each of which can fail halfway.

Pull: let recipients claim

A Merkle airdrop flips the model. The entire recipient list is compressed into a single 32-byte Merkle root stored on-chain. The creator pays for exactly two things:

1. Deploying a small drop contract from their own wallet (a few hundred thousand gas, regardless of list size).
2. One plain transfer moving the total budget into the drop.

Each recipient then submits their own claim with a Merkle proof — a short list of hashes showing their (address, amount) pair is in the tree. The contract verifies the proof against the root and transfers the tokens.

	Push (batch transfer)	Pull (Merkle claim)
Creator gas cost	Linear in list size	Constant (deploy + fund)
Recipient gas cost	Zero	One small claim tx (~90k gas)
10 vs 100,000 recipients	10,000× more expensive	Same creation cost
Unclaimed tokens	Stuck in inactive wallets	Recoverable via sweep
On-chain footprint	Every transfer	One 32-byte root
Claim window	Not possible	Optional start/end times

The trade-off — recipients pay a small gas fee to claim — is also a feature: tokens only move to wallets whose owners actually showed up, and anything unclaimed can be swept back by the creator after the drop ends.

Product tour

Everything runs at droppie.notcool.in:

• Dashboard (/app) — wallet overview, your drops and tokens, a claims-over-time chart built from on-chain Claimed events, and a live activity feed.
• Create wizard (/app/create) — a 4-step flow: pick a token, upload recipients, review the tree, deploy. Drafts persist locally so you can leave and come back. See the Quickstart.
• Token Alchemist (/app/tokens) — a no-code ERC-20 deployer for when you don't have a token yet: name, symbol, premint, optional mintable/burnable flags — deployed straight from your wallet. See DroppieERC20.
• Drop detail (/app/drops/[chainId]/[address]) — live stats, claim progress, the recipient list, claim UI, and creator admin (sweep, share link).
• Claim page (/claim/[chainId]/[address]) — the link you share with recipients. See the Claiming guide.

Under the hood:

• Contracts — one DroppieDrop escrow per campaign plus DroppieERC20 for no-code tokens, each deployed directly by the creator's wallet. No factories, nothing pre-deployed — Droppie works on any EVM chain. Foundry, Solidity ^0.8.24, OpenZeppelin v5.
• SDK — @droppie/sdk: CSV parsing, Merkle tree construction, proofs, distribution files, ABIs, and contract creation bytecode. The same code the app uses is yours to build on.
• Open source — the entire stack is MIT-licensed and self-hostable.

Where next?

• Launching a drop? Start with the Quickstart.
• Received a claim link? Read the Claiming guide.
• Curious about the machinery? See How it works.