Getting Started — ÐMS, ÐMP DogeTag Offers, and ÐWhisper

This guide shows how the newest Dogenals systems work together. These are launch-draft standards for the first Dogenals drop; test them carefully before treating them as production infrastructure.

The short version:

1. Use ÐMS to describe an asset.
2. Use ÐMP DogeTag Offers to send wallet-detectable buy interest.
3. Use ÐWhisper for encrypted negotiation context.
4. Use ÐMP for the actual offer, acceptance, and settlement record.

The Example Scenario

Alice owns a Koinu Relic. Bob wants to buy it, but Alice is not logged into Bob’s marketplace.

Bob can still:

• Discover the relic and its metadata through ÐMS.
• Send Alice a DogeTag Offer with a small DOGE attention amount.
• Attach a ÐWhisper encrypted message explaining the offer.
• Convert the signal into a full ÐMP offer if Alice responds.

Step 1 — Describe the Asset with ÐMS

ÐMS gives wallets and marketplaces common display fields. New inscriptions SHOULD use compact keys when the record is meant to live on-chain.

{
  "p": "dms",
  "v": "1.0",
  "o": "m",
  "c": "dogecoin",
  "a": {
    "t": "inscription",
    "i": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaai0",
    "pr": "koinu-relics"
  },
  "s": "relic",
  "d": {
    "ti": "Early Dogecoin Transfer Relic",
    "at": "relic",
    "rr": "standard"
  }
}

Wallets SHOULD show this as metadata, not ownership or legal title.

Step 2 — Send a ÐMP DogeTag Offer

A DogeTag Offer is a compact Ð:𝕏 OP_RETURN signal plus a spendable DOGE output to the recipient.

It tells Alice’s wallet:

• Bob is interested in a specific asset.
• Bob suggested a price.
• Bob paid an attention amount to Alice.
• Bob may create a full ÐMP offer later.

DogeTags are not escrow and not settlement.

Step 3 — Add ÐWhisper Context

If Bob wants to include private context, he creates a ÐWhisper message and sets the DogeTag flag for linked encrypted contact.

{
  "p": "Ð:W",
  "v": "1.0",
  "o": "m",
  "c": "dogecoin",
  "x": {
    "t": "dmp-dogetag-offer",
    "tx": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
  },
  "e": "xchacha20poly1305",
  "k": "secp256k1-ecdh-hkdf-sha256",
  "r": [
    {
      "i": "sha256:00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
      "epk": "02aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "w": "base64:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA="
    }
  ],
  "n": "base64:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB",
  "ad": "base64:w5A6Vy0xLjA=",
  "ct": "base64:CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC",
  "h": "sha256:dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd"
}

The message body is encrypted, but the transaction graph and timing are public.

Step 4 — Settle with ÐMP

If Alice accepts, the real market flow moves to ÐMP:

• Bob creates a full ÐMP offer, optionally linking tag_txid.
• Alice accepts or counters.
• The final transfer is verified by ÐMP settlement rules.

The important boundary: DogeTag and ÐWhisper are discovery and communication layers; ÐMP remains the marketplace state layer.

What to Read Next