Dogenals standards — v2.0 and interoperability

This directory holds long-range specifications and shared machine-readable artifacts: data models, API contracts, and event formats that let indexers, wallets, and marketplaces speak the same language. It sits beside (not above) the per-protocol spec.md files in ../../protocols/; on-chain encoding rules remain defined in each protocol’s own specification.

Relationship to “Doginals”: The inscriptions you see on Dogecoin are what the community still often calls Doginals. Dogenals is the name of this documentation and standards set. The chain is the same; the names distinguish culture from curation.

Vision (informative)

Dogenals v2.0 (research) describes a path beyond legacy ord-style envelopes: a Dogecoin-native marker, post-quantum–ready signing options, and clearer collection roots of trust. Nothing here deprecates existing inscriptions. Old envelopes remain valid for as long as the chain can parse them.

Area	v1.x (broadly)	v2.0 direction (draft)
Envelope marker	`ord` (inherited)	`dog` (proposed)
Collection assurances	Manifest + policy	Stronger signed hierarchy (spec)
Post-quantum (optional)	—	Documented in `pqc-verification-guide.md`
API surface	Varies by indexer	`api-contracts.json` as a convergence target

Files in this directory

File	Role
dogenals-protocol-spec.md	v2.0 technical draft (marker, model, extensibility)
pqc-verification-guide.md	How to verify PQC-style signatures in tooling
migration-guide.md	Migration notes for indexers and wallets (draft)
api-contracts.json	Suggested HTTP shapes for cross-indexer clients
data-models.json	Shared object definitions
event-schemas.json	Stream / feed formats for activity

Adoption checklist (informative)

These are not on-chain requirements until a future version says they are. Use them to track implementation if you are building a v2.0-aligned indexer or marketplace.

Indexers

Document which envelope markers you index (ord, dog, or both)
If you support PQC verification, state which algorithms
If you implement api-contracts.json, state version and deltas

Marketplaces and clients

Treat api-contracts.json and data-models.json as advisory interop until a protocol you ship references them
Validate collection signatures per the protocol you actually support (e.g. ÐMP collection today)

Wallets

If you inscribe, declare ord vs dog envelope in release notes
If you add PQC keys, follow the verification guide and test against vectors when published

Changes

Propose changes via pull request. Any change that affects how existing inscriptions are interpreted must be backward compatible or explicitly versioned in the relevant spec.md and changelog.

Lineage

Bitcoin Ordinals proved inscriptions on UTXO chains. Dogecoin’s indexers and this repo’s specs refine that for Dogecoin specifically: DRC-20, DRC-721-style trailers, ÐMP, Dunes, and the protocols linked from the root README. This directory’s JSON and v2.0 text exist so the ecosystem can converge without a single company gate.

Index of all documentation: ../INDEX.md · Ecosystem map: ../../README.md

Pqc Verification Guide Getting Started