Realms
Top-level names in the Atomicals naming system, claimed by satisfying the protocol's mint rules.
- Chain
- Bitcoin
- Carrier
- Atomicals envelope
- Ownership model
- utxo
- Operations
- mint, transfer
- Also written
- realm, atomicals-realms
Where it came from
Created outside Bitcoin Universe by Arthur (atomicals.xyz), 2023.
Where the specification lives
The specification and reference documentation for Realms live in bitcoinuniverseio/atomicals-and-arc-20 and are published at https://bitcoinuniverseio.github.io/atomicals-and-arc-20/. 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-atomicals-nfts-and-realms.
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: mint, 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- Realms has no executable offer workflow on this marketplace surface.
Operational behaviour
Indexing
State is read from Configured Atomicals ElectrumX authoritative realm authority.
What must be true before any change is accepted: Mutations fail closed unless the realm resolver returns the verified winner at the exact live owner outpoint.
Confirmation
Settlement requires at least one confirmation by default; operators may configure 1-100.
Settlement requires at least 1 confirmation.
Reorganisation
Authoritative winner and outspend reconciliation preserve signed evidence across rollback.
Freshness
Every mutation rechecks the Bitcoin and Atomicals checkpoint; deployment readiness must enforce operator 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.