Classic DRC-20 → Ðunes (light migration)

Status: Era 2 orientation · Suite: CORE_SUITE.md · Compare: DUNES_VS_TREATS.md

Dogenals targets a clean slate: new indexers and wallets optimize for Ðunes, ÐogeTreats, ÐMP, and ÐSwap Core. Classic inscription DRC-20 is not a first-class build target.

This document defines a light, optional migration path so good-faith holders can move value forward without forcing the team to maintain a heavy legacy indexing stack.

Clean slate (what we do not build)

Legacy balance viewing MAY use existing community indexers or wallet integrations (MyDoge, Doggy Market, etc.) — best-effort, not a Dogenals maintenance obligation.

Why a light migration path still helps

• Unites holders on one fungible economy (Ðunes + Treats companion lane)
• Reduces fork/drama from abandoned bags
• Rewards good actors; ticker squatters who refuse to move fade naturally
• Low cost: verify burn + mint new asset — no perpetual legacy ledger in our indexers

Migration flow (v1 — ship this)

1. Holder proves legacy balance (community indexer snapshot OR wallet export + txids)
2. Holder burns classic DRC-20 (inscription burn OR provable burn output)
3. Issuer mints equivalent Ðune (or project-mapped Ðune) + optional ÐRep bonus

Example (one line): Burn 1000 $TICK via inscription burn txid:abc… → receive 1000 units of etched Ðune TICK•MIGRATED + Bronze ÐRep attestation.

Step 1 — Prove balance

Accept any of:

• Public legacy indexer API response (signed snapshot hash optional)
• Wallet-held transfer inscriptions + deploy txid for ticker
• Project-run migration window with allowlist from their own indexer

Dogenals indexers do not need to re-index full DRC-20 history for this — projects and wallets can supply proofs.

Step 2 — Burn

Normative options (pick one per migration campaign):

Burn MUST be visible on-chain. Indexer verifies burn tx before minting new Ðune.

Step 3 — Mint Ðune

• 1:1 supply mapping by default (project may publish different ratio with disclosure)
• Etch via standard Ðunes etch if new name; or mint into pre-etched migration Ðune
• Optional ÐRep attestation via ÐMS (migration_bonus: true)
• Optional DogeRelic / Shiba badge for early migrators (cosmetic, not required)

Treats lane alternative

Meme/community tokens MAY migrate to ÐogeTreats (p:"dt") instead of Ðunes when the project wants OP_RETURN ledger semantics and cheap airdrops — see DUNES_VS_TREATS.md. Default recommendation remains Ðunes for serious fungibles and ÐSwap Core DOGE pairs.

Wallet UX (Dojak / dogenals.com)

• Tab: Legacy DRC-20 (read-only balances where provider supports it)
• CTA: Migrate to Ðunes → guided burn + mint (when campaign live)
• No new two-step transfer wizard in Era 2 primary flows

Indexer responsibilities (minimal)

No requirement to maintain classic available/transferable balance state in dogex for Era 2 greenfield deployments.

Phase 2 (optional on-chain linking)

Future normative pattern: single tx or atomic pair with OP_RETURN:

{ "p": "Ð:MIGRATE", "from": "drc-20", "tick": "EXAMPLE", "amt": "1000", "burn": "<txid>", "to": "dune:<name>" }

Research stub — not required for first migration campaigns.

Who this is for

Much clean slate. Very forward. Such migrate.