TAP on Doge
The TAP protocol as applied to Dogecoin inscriptions.
- Chain
- Dogecoin
- Carrier
- Doginals inscription carrying a TAP envelope
- Ownership model
- hybrid
- Operations
- deploy, mint, transfer
- Also written
- tap-on-doge, doge-tap, tap-doge
Where it came from
Created outside Bitcoin Universe by The Trac ecosystem, 2024.
Where the specification lives
The specification and reference documentation for TAP on Doge live in bitcoinuniverseio/tap-on-doge and are published at https://bitcoinuniverseio.github.io/tap-on-doge/. That site is the authority. This page exists so you can find it and compare it with the rest of the estate.
Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-doge-tap.
Support in Bitcoin Universe products
Where it appears
- Core: view, view-collection, view-activity, list, update-listing, unlist, buy, make-offer, accept-offer, cancel-offer, settle, reconcile
- Wallet: view, send, receive
- Inscribe: mint
Implemented
viewexternal-executionview-collectionexternal-executionview-activityexternal-executionlistexternal-executionupdate-listingexternal-executionunlistexternal-executionbuyexternal-executionmake-offerexternal-executionaccept-offerexternal-executioncancel-offerexternal-executionsettleexternal-executionreconcileexternal-execution
Not implemented, and why
sell- TAP on Doge has no executable offer workflow on this marketplace surface.
Operational behaviour
Indexing
State is read from Configured pinned Dogecoin TAP reader and Dogecoin Core.
What must be true before any change is accepted: 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.
Confirmation
Settlement requires the exact Dogecoin transaction confirmation and the expected protocol-state transition in a later authoritative checkpoint.
Settlement requires at least 1 confirmation.
Reorganisation
The authority appends reorg observations, reopens or invalidates affected orders deterministically, and preserves funding, broadcast, and replacement lineage.
Freshness
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.
Provenance
Capability facts on this page were generated from backend/packages/ecosystem-contracts/lib/protocols.js in bitcoinuniverseio/core at 15dd03b5986a. Implemented behaviour is not the same as production availability: see how to read our status.