Bitmap
Claims of Bitcoin blocks as addressable districts, established by the first valid inscription for a block number.
- Chain
- Bitcoin
- Carrier
- Ordinals inscription of the form <block>.bitmap
- Ownership model
- utxo
- Operations
- mint, transfer
- Also written
- bitmaps
Where it came from
Created outside Bitcoin Universe by The Bitmap community, 2023.
Where the specification lives
Bitmap has no Bitcoin Universe specification repository. Its specification is Maintained upstream by the Bitmap community.
Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-bitmap.
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-executionview-collectionin-app-executionview-activityin-app-executionlistin-app-executionupdate-listingin-app-executionunlistin-app-executionbuyin-app-executionmake-offerin-app-executionaccept-offerin-app-executioncancel-offerin-app-executionsettlein-app-executionreconcilein-app-execution
Not implemented, and why
sell- Bitmap has no executable offer workflow on this marketplace surface.
Operational behaviour
Indexing
State is read from Configured index-bitmap executable Marketplace authority.
What must be true before any change is accepted: Execution requires distinct read and execution credentials, a fresh Bitmap checkpoint, authoritative first-claim ownership, complete inventory, clean funding, immutable economics, and post-sign validation.
Confirmation
Settlement requires the exact confirmed Bitcoin transaction and the authoritative Bitmap claim 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 Bitmap, Ord, Bitcoin Core, and complete-inventory checkpoints; deployment readiness must enforce 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.