Writing something onto Dogecoin

An inscription is not a database row and not a token contract. It is bytes carried inside a Dogecoin transaction, landing on one specific satoshi.

1. The data goes into a transaction. A picture, a Bible verse, a pet's chip number, a block number, a pixel — the bytes are written into the transaction itself, so they are stored by every node that keeps the chain.
2. It lands on one specific satoshi. Not on an address and not on a wallet: on one particular unit of one particular coin. Move that satoshi and the piece moves with it.
3. The first person to inscribe it owns it. There is no registrar, no allowlist and no queue. Whoever writes it first has it — which is why some of this is a race rather than a shop.
4. The piece then rides inside an ordinary coin. Your inscription sits in a normal unspent output, indistinguishable from spending money to a wallet that does not check. That is exactly how inscriptions get handed to a miner as a fee or sent away as change — and why asset-aware coin selection exists.

This is why the wallet on this site refuses to spend any coin it has not positively classified as plain DOGE, and spends nothing at all when the classifier is unreachable. A one-satoshi mistake is permanent. Open the wallet →

Six routes onto Dogecoin from this ecosystem: three are open today, two are built but not open, and one is explicitly not for sale. Counts are read live from the public registry at page load; nothing numeric here is baked into the page.

Status chips and counts are read from the public collection registry at load. If the engine is unreachable the wording above stays as written and every link still works.

A microchip is a number, and the number is useless without something that resolves it. Chip registries go bankrupt, get sold, or put the lookup behind a subscription — the chip keeps working and the number stops meaning anything. BEACON writes the record onto Dogecoin instead, so the lookup survives the company.

Two inscriber services, one record format

The spec is published on purpose, so anyone can build a competing reader or indexer without this project existing. The two surfaces run the same code against the same chain — a record made on one is readable on the other, and on any tool that can read plain text out of a transaction.

Optional and decorative: a certificate can be minted as a second inscription — an SVG picture of the record, with a title, a choice of which fields appear, and an optional QR code whose target you pick. It is minted after the record so it can carry the record's real transaction ID. The record works perfectly without one.

Every inscriber in this ecosystem is non-custodial. The signing happens in your browser tab; the server never holds a key and never signs.

Nothing on this site can update a record for you, cancel an inscription, or move a coin on your behalf. There is no account to recover and no support desk that can reverse anything — that is the trade you are making in exchange for a record nobody can switch off.

• Give a town, not a street address. A finder needs to know roughly where the pet lives, not which door to knock on.
• Use a contact you are willing to publish. A phone number, email or URL that you are happy to have sitting on a public ledger permanently. A forwarding address is a perfectly good answer.
• Read the byte-count preview before you confirm. Every inscriber here shows the literal text that will be written and its size in bytes before anything is signed, and the confirmation dialog states the byte count, the number of transactions and the network cost.
• Assume a mistake is a new inscription, not a correction. Fixing a typo means writing an update record — the original stays on chain underneath it.

The wallet on this site has no general-purpose inscriber. It writes exactly one kind of inscription, and only because DRC-20 cannot be sent without it: the transfer parcel.

1. Build a transfer parcel to your own address. The wallet inscribes a small {"p":"drc-20","op":"transfer",…} record — a real commit and reveal pair — paid to you, funded only from coins it has positively identified as plain DOGE.
2. Wait for it to confirm. The parcel is an inscription like any other, and it is not spendable until the chain has it.
3. Send the parcel. Now the tokens move, using the same asset-transfer machinery as a doginal: the parcel is pinned as the first input, paid to the recipient at its exact value, with the fee funded from other coins entirely.

Said plainly: “send tokens instantly” is not what happens. It is two steps with a wait in the middle, because that is how DRC-20 works — not a limitation this wallet invented and not one it can skip.

Open the wallet →

Stated once, so nothing on this page has to be read charitably.

• No custody. No key of yours is ever held, stored or transmitted here. If a page ever asks you to send coins to us so we can inscribe on your behalf, it is not one of ours.
• No platform cut on BEACON. No subscription and no service fee — you pay the Dogecoin network fee and the tiny inscription output, and nothing else.
• No public mint on this host. There is no mint form, no order button and no checkout anywhere on doge.hankelsner.tech. This page is a map, not a shop.
• No buy button for BLUE COLLAR or GROUP from here. BLUE COLLAR's mint is not open anywhere yet; GROUP has no mint page at all because nothing of it is on chain.
• No sold-out counts, holder numbers, floor prices or volume. Five of the six collections have zero pieces on chain. The registry counts above are the only numbers, and they are read live.