DOG on Bitcoin is the rune DOG•GO•TO•THE•MOON, identified as 840000:3. Its units are tracked through Bitcoin transaction outputs using the Runes protocol. The launch created the entire initial supply upfront; a later community airdrop is a separate part of its history.
Read the asset in three steps: identify the exact rune, establish how units were created and trace how outputs transfer them. A ticker, a distribution claim and a Bitcoin confirmation each answer a different part of that task.
Start with the identifier and supply record
The Ordinals explorer entry records DOG’s etching on April 20, 2024, at block 840,000. It lists Rune ID 840000:3, rune number 3, an initial supply of 100 billion units, a 100 percent premine, and no open mint. These are token properties, rather than an estimate of what the asset should be worth.
The Ordinal Theory Handbook explains that a rune ID combines the block height and the etching transaction’s index. Names can contain bullet spacers for readability. Identifying an asset by its exact record avoids treating a similar name, ticker, or image as proof that two assets are equivalent.
A hypothetical listing labeled DOG could describe the native Bitcoin rune, an asset elsewhere, or something unrelated. Matching the identifier is therefore a question about what the listing represents. It does not establish that the listing or its operator is reliable.
Premine and airdrop describe different steps
In Runes terminology, a premine is an allocation created when the rune is etched. DOG’s explorer record shows that its initial supply was created this way. There was no open mint through which users could independently create further units under mint terms.
A distribution claim needs another source. DogSwap’s community launch history says the supply was given to Runestone holders on April 24, 2024, without a presale or reserved team allocation. The site is run by community volunteers and operates a swap service, so this is an interested account of the launch. The explorer independently establishes the etching and supply properties; it does not by itself verify every later distribution claim.
The history gives 112,383 Runestone collectibles and the same entitlement per Runestone. Those collectibles could change hands before the DOG distribution. Equal per collectible therefore differs from equal per original address, current wallet, or person. Someone holding several collectibles had several entitlements.
“Fair airdrop” can describe the stated allocation rule. It cannot establish equal ownership today, prevent later concentration, or guarantee a financial outcome. Even a distribution with no team reserve leaves questions about how assets trade and who subsequently holds them.
Bitcoin outputs carry two different balances
The Bitcoin transaction guide describes unspent transaction outputs, or UTXOs. Spending consumes earlier outputs and creates new ones. A wallet assembles the outputs it can spend rather than retrieving coins from inside an app.
Runes adds token accounting to this output model. An output can carry bitcoin value and a rune balance. The amounts answer different questions: how many satoshis the Bitcoin output contains, and how many DOG units Runes software assigns to it. A DOG balance does not entitle its owner to an equal quantity of BTC.
This becomes clearer with a hypothetical transfer. Alice controls an output carrying 1,000 DOG and wants Ben to receive 100. A Runes-aware transaction can spend that output, allocate 100 DOG to Ben’s new output, and allocate the remaining 900 to Alice’s change output. Bitcoin amounts also move between outputs, with BTC used for the miner fee.
The numbers illustrate accounting; they are not a live fee quote or a complete transaction-building recipe. A real wallet must also choose inputs, create appropriate outputs, and handle the Bitcoin amounts correctly.
Instructions are recorded; software interprets them
The handbook calls a Runes protocol message a runestone. That lowercase protocol term should be distinguished from the Runestone collectible collection used in the airdrop history.
Runestones are stored in an OP_RETURN output with a Runes marker and encoded instructions. They can specify allocations from transaction inputs to outputs. The data output holds the message; the spendable outputs carry the allocated balances.
This separates two jobs. Bitcoin software validates the underlying transaction according to Bitcoin’s rules. Runes-aware software interprets its token message and calculates the rune balances. A valid Bitcoin transaction is not a promise that its author expressed the intended DOG allocation correctly.
For Alice and Ben, a Bitcoin signature authorizes spending the inputs. It does not approve the economic wisdom of the transfer or guarantee that Alice chose Ben’s intended receiving destination. The resulting wallet balance depends on the transaction and the token rules, not on a separate DOG blockchain processing a second payment.
Handling errors can change the result
A wallet that recognizes only BTC may spend a rune-bearing output without managing its token balance deliberately. The transaction can still be valid for Bitcoin while the Runes allocation differs from the user’s intention.
The handbook also describes malformed messages, called cenotaphs: rune inputs to such a transaction are burned. This is a concrete protocol consequence, separate from a temporary display issue in a wallet. A familiar ticker or a successful Bitcoin confirmation cannot substitute for checking the intended asset and allocation.
The thumbnail’s branching dog tiles illustrate upfront creation and later distribution. They do not show BTC turning into DOG, a guaranteed equal distribution among people, or a promise that the token can retain value.
Network activity is not an investment conclusion
DOG transfers use Bitcoin block space and BTC fees. Increased token activity can therefore add demand for the same transaction capacity used by other Bitcoin transactions. That mechanism does not establish a particular DOG price or return.
A fixed initial supply says nothing by itself about demand, ownership concentration or a buyer’s return. Those questions remain separate from whether the transfer system works; Bitcoin’s scarcity and price illustrate the same distinction for a different asset.
Our Bitcoin output explanation follows the underlying transaction model in more detail. For DOG, keep the extra layer visible: identify the rune, distinguish creation from distribution, and separate Bitcoin transaction validity from token accounting. That is the useful meaning of being Bitcoin-native here.
