Version history

Changelog

Two histories. What changed in this documentation, and the protocol activation heights on Dogecoin that any indexer must reproduce.

Documentation

1.0.0, 2026-09-01

Complete rebuild of this repository as protocol documentation. The previous content was a three page promotional site; nothing in it was normative and its links pointed at a GitHub organisation that does not exist.

Added a specification with numbered rules covering the Doginals scriptSig envelope, payload encoding, identifiers, tapping, all eleven operations, the state model, activation heights, and invalid conditions.
Documented the Dogecoin inscription carrier in detail: push data in the signature script of input 0, a piece count that counts down, 520 byte chunks, and continuation across a chain of transactions. This is the largest single difference from TAP on Bitcoin and the previous content did not mention it.
Added a reference covering confirmation, mempool, and reorg semantics as they behave on a one-minute chain, fee and size behaviour without a witness discount, limitations, security considerations, and an implementation checklist.
Added test vectors for the envelope, payloads, addresses, and state transitions, with envelope cases derived from the Doginals parser.
Added a client-side payload validator and a confirmation time comparator.
Recorded three Bitcoin artefacts in the published Dogecoin specification text: the "valid Bitcoin addresses" wording and bc1 lowercasing rule in token-send, the Bitcoin example addresses throughout, and a privilege authority activation height that is a Bitcoin height. See specification section 10.
Documented the failure mode where a payload carries p: "tap" with a bare DRC-20 operation name such as mint or transfer. Such an inscription confirms, costs a full fee, and is then indexed by no one. The validator names this case explicitly and the guide explains it.
Replaced the Bitcoin Universe support claims with the actual contents of the protocol registry and the generated capability snapshot, including the recorded reason that sell is unsupported.
Corrected every site link: the previous pages linked to bitcoinuniverse.github.io and github.com/bitcoinuniverse, neither of which is this organisation.
Added local search, a dark and light theme with a persisted toggle, a 404 page, sitemap.xml, robots.txt, and an accurate llms.txt.
Merged the existing docs.manifest.json rather than replacing it, keeping its accurate field values and adding the specification and upstream declarations.

0.1.0, before 2026-09-01

Initial three page promotional site: a home page, a discover page, and a getting started page. It described TAP on Doge in general terms without operation names, payload rules, envelope details, or indexer semantics, and it did not distinguish Dogecoin from Bitcoin anywhere. Preserved here for history; none of it was normative.

Protocol activations on Dogecoin mainnet

These are properties of the chain and the protocol, not of this document. An indexer must reproduce the behaviour that applied below each height.

Heights at which behaviour changes, oldest first.
Height	Change	Effect on an indexer
`4,600,000`	First Dogecoin mainnet height at which `ord-dogecoin` indexes inscriptions.	Content below this height is not an inscription for indexing purposes. This is a Bitcoin Universe configuration choice, and an indexer should publish whichever height it uses.
`4,771,259`	Ord wallet 1.0.1 behaviour becomes required. Also the beginning of Dogemap.	The protocol follows ord wallet releases conservatively with announced activation heights, so an indexer that simply tracks the newest release is not conforming.
`5,487,639`	Ticker lengths widen from "exactly 3, or 5 to 32" to "1 to 32" Unicode symbols.	Applying today's rule to historical blocks admits deployments that were invalid at the time, and produces balances that do not reproduce.
`5,497,100`	DMT element field numbers and the `blk` value must be precise. Announced 2024-12-12.	Below this height both are read with JavaScript `parseInt` rules, which stop at the first non-digit character. Both behaviours must be implemented.

Upstream sources

This documentation tracks two upstream sources. When either changes materially, a new document version follows.

Trac-Systems/doge-tap-protocol-specs: the Dogecoin TAP protocol rules. The upstream document states that it is worked on continuously and that protocol updates are announced in advance with a grace period for indexers.
Trac-Systems/ord-dogecoin: the Doginals client the specification names as the standard TAP operates against. Bitcoin Universe maintains a production fork of it, from which the envelope and reorg details on this site are drawn.