Skip to content

DRC-20

Source bitcoinuniverseio/core (private)
Path backend/packages/ecosystem-contracts/lib/protocols.js
Chain dogecoin
Network mainnet
Lifecycle feature-gated
Verified 2026-09-01
AvailabilityFeature-gatedImplemented, but switched off unless an operator enables its feature gate. Treat it as unavailable until you can see it working.
ChaindogecoinOwnership model: hybrid. Decimals: none.
Actions supported12 / 13Trading actions are declared supported for this protocol.
Feature gatedogecoinMarketplaceV1Every action below stays closed until an operator enables this gate.

Execution model

An external marketplace or provider owns the order book and the execution path; Core routes to it.

Registry values
Execution mode
external-execution
Owning surface
main
Availability
feature-gated
Feature gate
dogecoinMarketplaceV1
Aliases accepted
drc-20
Address roles
paymentordinals

Actions

ActionSupportedMode, or the reason it is not
ViewYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
View collectionYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
View activityYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
ListYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
Update listingYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
DelistYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
BuyYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
Make offerYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
Accept offerYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
Cancel offerYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
SellNoDRC-20 has no executable offer workflow on this marketplace surface.
SettleYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.
ReconcileYesAn external marketplace or provider owns the order book and the execution path; Core routes to it.

Why the rest are unavailable

  • Sell

    DRC-20 has no executable offer workflow on this marketplace surface.

Source of truth

QuestionWhat answers it
Which orders existDurable Dogecoin-native SQLite listings, revisions, funded offers, reservations, action requests, funding fences, broadcast lineage, history, and settlement observations
Who owns the assetProtocol-specific authoritative checkpoint ownership and exact outpoint proof corroborated by Dogecoin Core and, for TAP-DOGE, the pinned immutable TAP reader
Whether a trade settledExact Dogecoin raw transaction templates, wallet-authorized permitted input signatures, Core validation and broadcast, chain confirmation, protocol checkpoint convergence, and rollback-safe reconciliation
What the protocol state isConfigured DRC-20 checkpoint authority and Dogecoin Core

Indexer

Primary index

Configured DRC-20 checkpoint authority and Dogecoin Core

Fallbacks

None. If the primary index cannot be read, this protocol has nothing to fall back to and the page says the read failed.

What a mutation must prove

Execution requires distinct read and execution credentials, a fresh execution-authenticated readiness probe, a complete authoritative checkpoint, Core-verified funding, exact immutable economics, and protocol-native post-sign validation.

Freshness, confirmation, and reorg policy

PolicyValueWhat the registry states
Freshness enforcedNoEvery mutation is bound to the exact authority checkpoint and an execution-authenticated readiness observation; deployment readiness must enforce its configured checkpoint-age and lag limits.
Maximum index lagnot setNo numeric block-lag ceiling is configured for this protocol.
Maximum observation agenot setNo maximum age is configured for an observation used by a mutation.
Listing confirmationsnot setSettlement requires the exact Dogecoin transaction confirmation and the expected protocol-state transition in a later authoritative checkpoint.
Settlement confirmations1A trade is recorded as settled after 1 confirmation.
Automatic reorg reconciliationYesThe authority appends reorg observations, reopens or invalidates affected orders deterministically, and preserves funding, broadcast, and replacement lineage.

Where else this protocol appears

The Bitcoin Universe registry records actions per product surface. Core is the main surface. The others are named here because a reader who cannot do something in Core may be able to do it in a sibling product.

SurfaceActions recorded
Coremainviewdiscoverview-collectionview-activityview-transactionlistupdate-listingunlistbuymake-offeraccept-offercancel-offersettlereconcile
Walletwalletviewsendreceive
Inscribeinscribemint