TAP

An inscribed token protocol with a wider operation set than BRC-20, including token authority and privileged operations.

Chain

Bitcoin

Carrier

Ordinals inscription carrying a TAP envelope

Ownership model

hybrid

Operations

deploy, mint, transfer, authority

Also written

tap-protocol

Where it came from

Created outside Bitcoin Universe by The Trac ecosystem, 2023.

Extends the inscribed-token idea with authority-based operations and privileged mints.

Where the specification lives

The specification and reference documentation for TAP live in bitcoinuniverseio/tap and are published at https://bitcoinuniverseio.github.io/tap/. 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-tap.

Support in Bitcoin Universe products

Feature gated

Implemented, but switched off unless an operator enables the gate.

Execution model: Built and executed inside Universe products. This surface sits behind the tapMarketplaceV1 feature gate.

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: deploy, mint, transfer

Implemented

• viewin-app-execution
• view-collectionin-app-execution
• view-activityin-app-execution
• listin-app-execution
• update-listingin-app-execution
• unlistin-app-execution
• buyin-app-execution
• make-offerin-app-execution
• accept-offerin-app-execution
• cancel-offerin-app-execution
• settlein-app-execution
• reconcilein-app-execution

Not implemented, and why

sell

TAP has no executable offer workflow on this marketplace surface.

Operational behaviour

Indexing

State is read from Configured index-tap executable Marketplace authority.

What must be true before any change is accepted: 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.

Confirmation

Settlement requires the exact confirmed Bitcoin transaction, the consumed TAP transfer inscription, and the buyer indexed balance at stable checkpoints.

Settlement requires at least 1 confirmation.

Reorganisation

The authority appends reorg observations, reopens or invalidates affected orders deterministically, and preserves funding, broadcast, settlement, and replacement lineage.

Freshness

Every mutation is bound to stable TAP, Ord, Bitcoin Core, and complete-inventory checkpoints; deployment readiness must enforce the 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.