TAP on Doge
Execution model
An external marketplace or provider owns the order book and the execution path; Core routes to it.
- Execution mode
external-execution- Owning surface
main- Availability
feature-gated- Feature gate
dogecoinMarketplaceV1- Aliases accepted
tap-on-dogedoge-taptap-doge- Address roles
payment
Actions
| Action | Supported | Mode, or the reason it is not |
|---|---|---|
View | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
View collection | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
View activity | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
List | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Update listing | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Delist | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Buy | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Make offer | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Accept offer | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Cancel offer | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Sell | No | TAP on Doge has no executable offer workflow on this marketplace surface. |
Settle | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Reconcile | Yes | An external marketplace or provider owns the order book and the execution path; Core routes to it. |
Why the rest are unavailable
SellTAP on Doge has no executable offer workflow on this marketplace surface.
Source of truth
| Question | What answers it |
|---|---|
| Which orders exist | Durable Dogecoin-native SQLite listings, revisions, funded offers, reservations, action requests, funding fences, broadcast lineage, history, and settlement observations |
| Who owns the asset | Protocol-specific authoritative checkpoint ownership and exact outpoint proof corroborated by Dogecoin Core and, for TAP-DOGE, the pinned immutable TAP reader |
| Whether a trade settled | Exact 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 is | Configured pinned Dogecoin TAP reader and Dogecoin Core |
Indexer
Configured pinned Dogecoin TAP reader and Dogecoin Core
None. If the primary index cannot be read, this protocol has nothing to fall back to and the page says the read failed.
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
| Policy | Value | What the registry states |
|---|---|---|
| Freshness enforced | No | Every 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 lag | not set | No numeric block-lag ceiling is configured for this protocol. |
| Maximum observation age | not set | No maximum age is configured for an observation used by a mutation. |
| Listing confirmations | not set | Settlement requires the exact Dogecoin transaction confirmation and the expected protocol-state transition in a later authoritative checkpoint. |
| Settlement confirmations | 1 | A trade is recorded as settled after 1 confirmation. |
| Automatic reorg reconciliation | Yes | The 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.
| Surface | Actions recorded |
|---|---|
Coremain | viewdiscoverview-collectionview-activityview-transactionlistupdate-listingunlistbuymake-offeraccept-offercancel-offersettlereconcile |
Walletwallet | viewsendreceive |
Inscribeinscribe | mint |
Read this alongside
Section titled “Read this alongside”- The support matrix, for how TAP on Doge compares with the other 28 marketplace protocols.
- How to read a protocol row, for what each value on this page means.
- Market safety, before acting on anything here.