Runes (Native)

The first-party read path for Runes state, separated in the product so that Rune data served from Universe infrastructure is distinguishable from any other source.

Chain

Bitcoin

Carrier

OP_RETURN runestone

Ownership model

hybrid

Decimals

asset-defined

Also written

runes-native, native-runes, runes-(native)

Where it came from

A Bitcoin Universe read path, not a separate protocol.

Not a separate protocol. A Universe read path that serves Rune balances directly from Universe infrastructure.

Where the specification lives

The specification and reference documentation for Runes (Native) live in bitcoinuniverseio/runes and are published at https://bitcoinuniverseio.github.io/runes/. 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-runes.

Support in Bitcoin Universe products

Read only

You can see this protocol in the product. No trade action is implemented.

Execution model: Read paths only.

Where it appears

• Core: view, view-collection, view-activity
• Wallet: view, send, receive

Implemented

• viewread-only
• view-collectionread-only
• view-activityread-only

Not implemented, and why

list

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

update-listing

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

unlist

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

buy

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

make-offer

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

accept-offer

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

cancel-offer

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

sell

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

settle

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

reconcile

Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

Operational behaviour

Indexing

State is read from Universe Ord Rune index and Universe order book. Supporting reads come from Configured mempool/Esplora providers for UTXO and settlement reads.

What must be true before any change is accepted: Runes Native mutations remain read-only until complete Rune outpoint inventory, cardinal-input safety, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

Confirmation

No supported mutation reaches confirmation or settlement.

Reorganisation

Read state follows the authority; no executable order state exists to roll back.

Freshness

No node-tip/indexer-tip comparison or maximum observation age is enforced.

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.