Skip to content

TAP

Source bitcoinuniverseio/core (private)
Path backend/packages/ecosystem-contracts/lib/protocols.js
Chain bitcoin
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.
ChainbitcoinOwnership model: hybrid. Decimals: none.
Actions supported12 / 13Trading actions are declared supported for this protocol.
Feature gatetapMarketplaceV1Every action below stays closed until an operator enables this gate.

Execution model

Core builds and validates the transaction; your wallet signs it.

Registry values
Execution mode
in-app-execution
Owning surface
main
Availability
feature-gated
Feature gate
tapMarketplaceV1
Aliases accepted
tap-protocol
Address roles
paymentordinals

Actions

ActionSupportedMode, or the reason it is not
ViewYesCore builds and validates the transaction; your wallet signs it.
View collectionYesCore builds and validates the transaction; your wallet signs it.
View activityYesCore builds and validates the transaction; your wallet signs it.
ListYesCore builds and validates the transaction; your wallet signs it.
Update listingYesCore builds and validates the transaction; your wallet signs it.
DelistYesCore builds and validates the transaction; your wallet signs it.
BuyYesCore builds and validates the transaction; your wallet signs it.
Make offerYesCore builds and validates the transaction; your wallet signs it.
Accept offerYesCore builds and validates the transaction; your wallet signs it.
Cancel offerYesCore builds and validates the transaction; your wallet signs it.
SellNoTAP has no executable offer workflow on this marketplace surface.
SettleYesCore builds and validates the transaction; your wallet signs it.
ReconcileYesCore builds and validates the transaction; your wallet signs it.

Why the rest are unavailable

  • Sell

    TAP has no executable offer workflow on this marketplace surface.

Source of truth

QuestionWhat answers it
Which orders existDurable index-tap SQLite listings, revisions, funded offers, reservations, action requests, funding fences, broadcast lineage, history, and settlement observations
Who owns the assetExact live TAP transfer inscription, Ord location, Bitcoin prevout and outspend, and complete 29-protocol output inventory agreement
Whether a trade settledExact PSBT templates, wallet-authorized input signatures, Bitcoin Core preflight and broadcast, chain confirmation, consumed TAP transfer state, buyer indexed balance, and rollback-safe reconciliation
What the protocol state isConfigured index-tap executable Marketplace authority

Indexer

Primary index

Configured index-tap executable Marketplace authority

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 TAP readiness checkpoint, exact complete inventory, clean funding, immutable economics, and protocol-native post-sign validation.

Freshness, confirmation, and reorg policy

PolicyValueWhat the registry states
Freshness enforcedNoEvery mutation is bound to stable TAP, Ord, Bitcoin Core, and complete-inventory checkpoints; deployment readiness must enforce the 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 confirmed Bitcoin transaction, the consumed TAP transfer inscription, and the buyer indexed balance at stable checkpoints.
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, settlement, 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
Inscribeinscribedeployminttransfer