Alkanes
Source bitcoinuniverseio/core (private)
Path backend/packages/ecosystem-contracts/lib/protocols.js
Chain bitcoin
Network mainnet
Lifecycle read-only
Verified 2026-09-01
AvailabilityRead-onlyYou can see it but you cannot trade it. Core reads the protocol and shows it; no marketplace mutation is available.
ChainbitcoinOwnership model: hybrid. Decimals: asset-defined.
Actions supported3 / 13No trading action is declared supported for this protocol.
Feature gateNoneNo gate stands between the shipped build and the actions below.
Execution model
Reads only. No execution path is deployed.
Registry values
- Execution mode
read-only- Owning surface
main- Availability
read-only- Feature gate
null- Aliases accepted
alkane- Address roles
paymentordinals
Actions
| Action | Supported | Mode, or the reason it is not |
|---|---|---|
View | Yes | Reads only. No execution path is deployed. |
View collection | Yes | Reads only. No execution path is deployed. |
View activity | Yes | Reads only. No execution path is deployed. |
List | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Update listing | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Delist | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Buy | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Make offer | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Accept offer | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Cancel offer | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Sell | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Settle | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Reconcile | No | Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven. |
Why the rest are unavailable
ListUpdate listingDelistBuyMake offerAccept offerCancel offerSellSettleReconcileAlkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.
Source of truth
| Question | What answers it |
|---|---|
| Which orders exist | No executable order authority is deployed |
| Who owns the asset | Read authority only; no complete transferability proof |
| Whether a trade settled | No executable settlement authority is deployed |
| What the protocol state is | Universe Alkanes authority |
Indexer
Primary index
Universe Alkanes authority
Fallbacks
- Configured mempool/Esplora providers for UTXO and settlement reads
What a mutation must prove
Alkanes mutations remain read-only until exact Alkane state, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.
Freshness, confirmation, and reorg policy
| Policy | Value | What the registry states |
|---|---|---|
| Freshness enforced | No | No node-tip/indexer-tip comparison or maximum observation age is enforced. |
| Maximum index lag | not set | No numeric block-lag ceiling is configured for this protocol. |
| Maximum observation age | not set | No maximum age is configured for an observation used by a mutation. |
| Listing confirmations | not set | No supported mutation reaches confirmation or settlement. |
| Settlement confirmations | not set | No settlement depth applies, because no supported action reaches settlement. |
| Automatic reorg reconciliation | No | Read state follows the authority; no executable order state exists to roll back. |
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.
| Surface | Actions recorded |
|---|---|
Coremain | viewdiscoverview-collectionview-activityview-transaction |
Walletwallet | viewsendreceive |
Inscribeinscribe | mint |
Read this alongside
Section titled “Read this alongside”- The support matrix, for how Alkanes compares with the other 28 marketplace protocols.
- How to read a protocol row, for what each value on this page means.
- Market safety, before acting on anything here.