Running an Airdrop Campaign

An airdrop campaign moves through a fixed lifecycle. Each step has its own page in this section; this page is the map.

create collection → upload media → build audience → estimate cost
      → launch (dry-run first) → fund via wallet → delivery → open claims

1. Create a collection and upload media — the content that will be inscribed. A collection groups media items; a campaign links one or more collections.
2. Build your audience — the wallets that will receive the inscriptions. Use an on-chain cohort (e.g. “ordinals whales”, “active traders”) or add addresses manually.
3. Estimate the cost — per-tier (slow / normal / fast) totals for inscribing the whole campaign, priced from live Bitcoin fee rates, plus a dry-run that shows the exact delivery plan without touching the chain.
4. Launch and fund — launching creates a batch and returns a payment address and an exact amount. You fund it from your own wallet (one click with UniSat); Skrybit’s engine does the rest.
5. Track delivery — watch the batch progress: payment seen → payment confirmed → commit tx → reveal tx → inscription in the recipient’s wallet.
6. Open claims — let recipients prove ownership on a public claim page and connect with your campaign.

How fast is it?

With a normal fee tier and normal mempool conditions, a campaign runs end-to-end in about three Bitcoin blocks. A real production run on mainnet (July 30, 2026) went from payment sent to claimed inscription in about 30 minutes:

Slower fee tiers cost less but each confirmation can wait more blocks; see Estimating Cost.

Rehearse on testnet4

The entire lifecycle — collections, cohorts, launch, funding, delivery, claims — works identically on testnet4 with valueless coins. If this is your first campaign, run it there first.