Airdrop / Claim

Overview

A gas-light airdrop. Drag a recipients CSV into the setup wizard, preview it paginated with totals, and generate the Merkle root + claims file in the browser — no CLI. Recipients check eligibility and claim with one click; only they pay gas.

Airdrop / Claim turns a list of addresses + amounts into a live claim page. In the setup wizard you drop in a CSV, review it paginated with running totals, and the Merkle root and per-recipient claims file are generated entirely in the browser — then you deploy the distributor and fund it (prefilled with the airdrop total) from your wallet.

The claim page connects a wallet, instantly shows whether it's eligible and for how much, and claims in one click. The MerkleDistributor verifies the proof on-chain and records the claim, so each wallet can claim exactly once.

You fund the distributor with the total tokens once; each recipient pays the gas for their own claim. Everything on the page — title, token, symbol — is env-driven and brandable.

What's included

• Next.js app (App Router, TypeScript, Tailwind)
• MerkleDistributor.sol + Hardhat
• In-browser Merkle list builder + claims.json generation (CLI script also included)
• Setup wizard with in-browser deploy and a fund step
• Dockerfile + docker-compose, README

Smart contracts

• MerkleDistributor.sol — a gas-light airdrop: recipients prove their (address, amount) against a Merkle root and claim exactly once; it tracks the claimed count and remaining balance, and the owner can sweep any leftovers after the campaign (OpenZeppelin SafeERC20 + MerkleProof).

Tech stack & chains

Built with Next.js, TypeScript, Tailwind, viem, Merkle, Hardhat.

Runs on: Ethereum, BSC, Polygon, any EVM. The chain is a configuration value — point it at any EVM network or a testnet like Sepolia.

Quick start

After purchase you get a zip of the full source. Unzip it, then install dependencies and start the dev server:

unzip airdrop-claim.zip && cd airdrop-claim
npm install
npm run dev

The app starts on http://localhost:3006. On first run — before any .env exists — it boots straight into the setup wizard instead of the real app.

Configure with the setup wizard

The wizard collects everything the template needs and writes a .env for you — no hand-editing required to get started.

1. Pick the network and (optionally) a read-only RPC URL — test it with the built-in button.
2. Choose theme, accent color and font.
3. Fill in your token / project details and parameters.
4. Deploy the included smart contract(s) straight from your browser wallet (MetaMask). If you set an Etherscan API key, the source is auto-verified.
5. Click View .env, copy or download the file, save it as .env in the project root, and restart the dev server.

Once a valid .env is present the wizard disappears and the live app renders. Re-running the wizard later is as simple as removing the required values again.

Customize

Branding & content (no code)

Almost everything visible — name, symbol, taglines, descriptions, caps, dates, social links — is an environment variable in .env. Edit the value and restart; the wizard documents each one with a comment.

Appearance is env-driven too: NEXT_PUBLIC_THEME (dark / light / system), NEXT_PUBLIC_ACCENT (any hex color) and NEXT_PUBLIC_FONT. Some fields aren't asked in the wizard on purpose — you'll find them in .env with sensible defaults and can edit them directly.

Languages

The UI ships translated into 10 languages under messages/*.json (en, es, fr, zh, hi, ar, pt, bn, ru, ja). Edit a value to change wording, or add a key — missing keys fall back to English.

Editing the UI

The interface is a small set of React components under components/ styled with Tailwind. The main screen is a single component you can freely edit. On-chain reads are batched through a shared lib/web3.ts helper, so adding a new stat is a one-line read.

Configuration reference

Configuration lives in .env (copy .env.example to start, or let the wizard generate it). Two kinds of variables:

• NEXT_PUBLIC_* — read in the browser (token name, addresses, theme, RPC). These are inlined at build time, so set them before you build for production.
• Server-only values (deploy keys, private RPC) — never prefixed with NEXT_PUBLIC_, never shipped to the client.

Deploy the smart contracts

You have two equivalent options. In the browser, the setup wizard's deploy step sends the deploy transaction from your wallet and (with an Etherscan key) verifies the source automatically. From the CLI:

# compile + copy artifacts the app/wizard use
npm run compile

# deploy to the network in your .env (RPC_URL + DEPLOYER_PRIVATE_KEY)
npm run deploy

Copy the printed contract address into the matching NEXT_PUBLIC_* address variable (the wizard does this for you). Auto-verification retries while the explorer indexes the new contract, so a fresh deploy verifies within a minute or so.

Deploy the app

Vercel (or any Next.js host)

1. Push the project to a Git repo and import it in Vercel.
2. Add your .env values as Environment Variables (remember NEXT_PUBLIC_* are baked at build time, so set them before the build).
3. Deploy. Next.js App Router is fully supported out of the box.

Docker (single template)

Each template ships a multi-stage Dockerfile that produces a tiny distroless runtime (just Node.js + the standalone build — no shell or package manager) and a docker-compose.yml:

# build + run; with no .env it opens the setup wizard
docker compose up --build

# once you have a .env, pass it in:
docker run --env-file .env -p 3006:3000 airdrop-claim

The container serves on port 3000 internally; the compose file maps it to 3006 on your host. Build-time NEXT_PUBLIC_* values can be passed as build args or baked from a committed .env.

VPS / bare metal

Build once and run the Node server — no Docker required:

npm install
npm run build
npm run start   # serves the production build

Production checklist

• Set NEXT_PUBLIC_CHAIN_ID to your real chain (mainnet/BNB/Polygon) — not a testnet.
• Use a dedicated RPC endpoint (Infura/Alchemy/your node) in NEXT_PUBLIC_RPC_URL for reliable reads.
• Deploy and verify your contract on the explorer so users can read the source.
• Double-check economic parameters (caps, price, supply, dates) — they're immutable once deployed.
• Set the real NEXT_PUBLIC_* values at build time, and keep server secrets out of the client.

Support

Each template includes a README with the same steps, an .env.example, and inline comments. Questions about your purchase are answered from the store.