Skip to content

Bitcoin Stamps

Immutable on-chain images stored in unprunable transaction outputs, indexed through the Counterparty data layer.

Chain
Bitcoin
Carrier
Bare multisig and OP_RETURN outputs carrying encoded data
Ownership model
utxo
Operations
stamp, transfer
Also written
stamp, btc-stamps

Where it came from

Created outside Bitcoin Universe by Mike In Space, 2023.

Stores image data in transaction outputs that cannot be pruned, aiming for permanence stronger than witness data.

Where the specification lives

Bitcoin Stamps has no Bitcoin Universe specification repository. Its specification is bitcoinuniverseio/btc_stamps and bitcoinuniverseio/stampchain.io.

Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-stamps and bitcoinuniverseio/btc_stamps.

Support in Bitcoin Universe products

Where it appears

  • Core: view, discover, view-collection, view-activity, view-transaction
  • Wallet: view, send, receive
  • Inscribe: inscribe, transfer
  • StampDEX: view, view-collection, view-activity, list, unlist, buy

Implemented

  • viewexternal-execution
  • view-collectionexternal-execution
  • view-activityexternal-execution
  • listexternal-execution
  • unlistexternal-execution
  • buyexternal-execution

Not implemented, and why

update-listing
Bitcoin Stamps listings must be cancelled and relisted; no atomic listing update is implemented.
make-offer
Bitcoin Stamps has no executable offer workflow on this marketplace surface.
accept-offer
Bitcoin Stamps has no executable offer workflow on this marketplace surface.
cancel-offer
Bitcoin Stamps has no executable offer workflow on this marketplace surface.
sell
Bitcoin Stamps has no executable offer workflow on this marketplace surface.
settle
Bitcoin Stamps has no executable settle authority on this marketplace surface.
reconcile
Bitcoin Stamps has no executable reconcile authority on this marketplace surface.

Operational behaviour

Indexing

State is read from StampDEX and Stampchain. Supporting reads come from OpenStamp for reference metadata.

What must be true before any change is accepted: Universe allowlists and validates the exact proxy route/body; StampDEX/Counterparty validates dispenser state. Universe does not compare provider and Bitcoin tips.

Confirmation

Confirmation policy is delegated to StampDEX/Counterparty.

Reorganisation

Universe relies on StampDEX/Counterparty state and has no local rollback worker.

Freshness

Universe does not enforce a StampDEX-versus-chain lag threshold.

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.