Bitcoin-adjacent airdrops, explained honestly

Why plain Bitcoin has no native airdrop mechanism

The Bitcoin developer guide describes a ledger of unspent transaction outputs. Each transaction spends outputs created by earlier ones, each output can be spent once, and any surplus of inputs over outputs becomes the miner's fee. There is no account balance a contract can top up, and no contract layer for a project to run a distribution script. Bitcoin Script, per the same documentation, is stateless and not Turing complete, with no loops.

So when Bitcoin gets "an airdrop", one of four things is happening, and they differ completely in risk. We list them in the next section. The one structural exception is a chain split, which the developer guide describes: a hard fork produces "permanently divergent chains". Since both sides share the history, holders can end up with coins on each. We would call that a fork outcome and not an airdrop, because nobody chose to give anything away. We do not cover specific historical forks here, since we did not review first-party sources for them.

The four things people call Bitcoin airdrops

Our Babylon page is the only Bitcoin-linked campaign in our database. For the rest we hold no verified records, which is itself informative.

A small classifier for any "Bitcoin airdrop" offer

Answer three questions about the offer you were sent. The result names the category and the first thing to check. It uses the table above and cannot judge an individual offer.

Runes, inscriptions and BRC-20

The Ordinals handbook says ordinal theory gives each satoshi an identity so it can be tracked, and that inscriptions attach arbitrary content to individual sats. The content is stored in taproot script-path spend scripts, so inscribing takes two transactions: a commit and a reveal. Inscriptions move through ordinary Bitcoin transactions, but sending a specific sat requires a transaction that controls the order and value of its inputs and outputs according to ordinal theory.

That last point matters for safety. The handbook does not state that wallets must avoid spending inscribed sats, but it does imply that moving a specific sat needs ordinal-aware construction. Our judgement: a wallet that is not ordinal-aware could spend a sat carrying an inscription as ordinary money. If you hold inscribed assets, keep them in a wallet designed for them, separate from coins you spend.

Runes

Runes is a protocol for fungible tokens on Bitcoin. A runestone, the protocol message, sits in an output that starts with OP_RETURN and OP_13. A rune's ID is the block of its etching plus the transaction index, such as 500:20. Etching sets immutable properties: name, divisibility, symbol and an optional premine for the etcher. A rune may have an open mint with a cap and a fixed amount per mint, bounded by start and end heights or offsets. While it is open, anyone may create a mint transaction. Malformed runestones are cenotaphs, which burn the runes they involve. The handbook content we read does not mention airdrops.

Our reading: an "open mint" is the opposite of an airdrop. You pay a fee and receive a fixed amount if you are in time. That can be a reasonable action, but it is not free and it is not a gift, and nothing in the protocol makes the token valuable.

BRC-20

The BRC-20 document calls it an experimental standard that creates off-chain balance states with inscriptions. It defines three JSON operations (deploy, mint and transfer), where a transfer needs a transfer inscription that is then sent to the recipient. The author strongly discourages financial decisions based on it, and notes the balances may not be safely tradable with existing marketplace infrastructure. Because balances are derived by aggregating history, they depend on the indexer. See our NFT airdrops guide for adjacent risks.

Bitcoin staking: the Babylon case

Babylon docs describe native Bitcoin staking directly on Bitcoin: stakers keep control of their BTC, there are no wrapped assets, and stakes lock coins in a time-bound contract whose spending conditions include the holder's signature, timelock expiry and a covenant committee for slashing. Stakers delegate to finality providers, and security violations can lead to partial or complete forfeiture. The docs do not give lock durations or reward rates in the pages we read.

The airdrop tied to it was for Phase-1 stakers: per the foundation announcement as reported by Decrypt (we could not open the foundation post), 600 million BABY or 6% of supply, with 335 million as base Phase-1 staking rewards and 200 million as a bonus for stakes that moved into Phase 2. A BABY address had to be registered and linked to the staking wallet. Tokens were credited when Babylon Genesis launched, so no claim site was needed. The main lesson is that eligibility was capital at risk, not social tasks. The distribution is closed, and recent Babylon posts focus on Bitcoin vaults and lending, not a new airdrop. Compare the Cosmos context on our Cosmos page.

Fees and signing

The transactions guide says Bitcoin fees depend on a transaction's byte size, and the per-byte rate rises with demand for block space. The fee goes to the miner, and since a UTXO is spent whole, anything not sent to an output becomes the fee unless returned as change. That last fact is the practical risk: a wrongly built transaction can overpay by a lot. We give no typical fee since the docs give no current figure.

The guide also explains what a signature authorises. By default (SIGHASH ALL) a signature covers all inputs and all outputs. Other types sign fewer outputs, so others could change them, and the ANYONECANPAY modifier lets others add or remove inputs. Wallets normally hide this. As an editorial matter, if any page or tool asks you to sign something with an unusual signature type, stop.

Scam patterns around Bitcoin airdrops

1. "Free mint" sites that ask for a signature or deposit instead of describing a plain mint transaction.
2. "Verify your wallet to receive an airdrop" pages asking for a seed phrase. The Ordinals wallet guide itself labels exported descriptors "DO NOT SHARE WITH ANYONE" because they contain private keys.
3. Staking clones imitating a real protocol's page. Start from the project's docs, not a search ad.
4. Inscription lures, where an inscribed sat arrives unprompted and the page that "values" it asks you to connect a wallet.
5. "Fork claim" offers that ask for keys to "claim" coins from a chain split. Ask for the official source first.

The general rules are in our scam guide. Use separate wallets as described in the burner wallet guide.

What we would check first

1. Which of the four categories is it, and does the page say?
2. Where are the rules published, and who is accountable for them?
3. If it needs a transaction, can the wallet show every output?
4. If it needs a lock-up, what are the timelock and slashing terms in the docs?
5. If tokens appear elsewhere, which network, and is its page in our ecosystems list?
6. Could I afford to lose everything I send, including fees?

See also the airdrop basics guide, the potential airdrops list and the Starknet page, which covers a Bitcoin-linked incentive programme.

Written by the airdrop.promo Editorial Team. See how we verify. Educational content only, not financial advice.