docsReference LibraryEra2 Namespace

Dogenals Era 2 OP_RETURN Namespace

Status: Draft guidance
Scope: Future OP_RETURN-native Dogenals features
Guiding narrative: Doginals = spark, Dogenals = fire.

Era 2 is the shared namespace for future Dogenals OP_RETURN protocols. It gives wallets and indexers a common first marker while keeping each module compact and independently versioned.

Format

Ð:<module>:<kind>:<payload>

Rules:

  • Ð is the global Dogenals Era 2 marker.
  • Ð is UTF-8 c3 90.
  • module identifies the Dogenals subsystem.
  • Module identifiers SHOULD use plain Latin letters for predictability, except the DXD exchange module’s preferred stylized 𝕏.
  • kind identifies the operation inside that subsystem.
  • payload is module-defined and SHOULD be as compact as practical.

Module Legend

MarkerModuleIntended use
Ð:𝕏DXD exchangeExchange, marketplace, swap, offer, and settlement signaling
Ð:XDXD exchange fallbackSpace-saving fallback for Ð:𝕏
Ð:WÐWhisperEncrypted messaging discovery and routing
Ð:MÐMSMetadata references and compact metadata hints
Ð:TReservedFuture token / transfer primitives

DXD Smart Fallback Rule

Implementations SHOULD use the brand-forward marker Ð:𝕏 by default.

If including the stylized 𝕏 would cause the total OP_RETURN payload to exceed 76 bytes, implementations MUST automatically and transparently fall back to plain X, producing Ð:X.

This fallback MUST happen silently from the user’s perspective. Wallets and applications MAY expose the chosen wire marker in advanced transaction details, logs, or developer tooling.

Byte Values

MarkerUTF-8 bytes
Ðc3 90
𝕏f0 9d 95 8f
X58
Ð:𝕏c3 90 3a f0 9d 95 8f
Ð:Xc3 90 3a 58
Ð:Wc3 90 3a 57
Ð:Mc3 90 3a 4d

Why 76 Bytes?

The 76-byte threshold is a practical policy target for compact OP_RETURN payloads. It leaves room for the namespace, module kind, hashes, flags, and small numeric fields while avoiding unnecessary relay-policy friction.

The rule intentionally balances:

  • Branding: Ð:𝕏 is the preferred DXD marker.
  • Practicality: Ð:X keeps long payloads compact.
  • Implementation quality: parsers MUST handle both forms deterministically; lazy parsers that only accept one form are incomplete.

Implementation Rules

  1. New OP_RETURN-native Dogenals modules SHOULD use Era 2 markers.
  2. DXD parsers MUST normalize Ð:𝕏 and Ð:X to the same exchange module internally.
  3. Implementations MUST NOT treat the fallback marker as lower-quality or less valid.
  4. Wallets SHOULD keep the fallback silent in normal user-facing flows.
DogewhisperInconsistencies Resolved