Recursive Title Protocols (Dogenals)
Short umbrella note for standards that assign on-chain, transferable ownership to a block or transaction on Dogecoin, with first-come, first-served (FCFS) at the indexer, economic friction for fair participation, and ÐMP as the default marketplace and collection layer.
| Protocol | Title (normative) | Analogy (informative) | Spec |
|---|---|---|---|
| ÐMaps | block_height (plus chain + tier: standard in v1) | “Bitmaps”-style block + H3 geo | ../protocols/dogemaps/spec.md |
| Koinu Relics | target_txid (1:1 standard) | “Satoshi Relics”-style transaction + generative traits | ../protocols/koinu-relics/spec.md |
What they share (informative)
- Dogenals inscriptions only: no DRC-20 / wrapped
pcollision for the title JSON. - FCFS by canonical order; later duplicate claims are rejected by the indexer.
- ÐMP
dogenalsextension object incollection(and normalliston eachinscription_id) for variable / infinite-described supply where applicable (see each spec). - Parent/child
upgradeinscriptions to build value on a title without changing the title key. - Burn / fee attestations in the inscribing transaction, plus per-address caps, to raise the cost of monopolist mint bots (not a perfect Sybil cure on a permissionless chain).
Related
This file is non-normative; each protocol’s spec.md is authoritative.