Skip to content

UNAT

Natural-asset digital artifacts recorded through inscriptions and rendered from deterministic rules.

Chain
Bitcoin
Carrier
Ordinals inscription
Ownership model
utxo
Operations
mint, transfer
Also written
tap-unat, tap_unat

Where it came from

Created outside Bitcoin Universe by The UNAT community, 2024.

Where the specification lives

UNAT has no Bitcoin Universe specification repository. Its specification is Maintained upstream.

Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-unat.

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: 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
UNAT has no executable offer workflow on this marketplace surface.

Operational behaviour

Indexing

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

What must be true before any change is accepted: Execution requires distinct read and execution credentials, a fresh UNAT readiness checkpoint, exact authoritative mint membership, complete inventory, clean funding, immutable economics, and protocol-native post-sign validation.

Confirmation

Settlement requires the exact confirmed Bitcoin transaction and the authoritative UNAT mint indexed at a buyer-owned output 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 UNAT, 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.