Перейти к содержимому

Источники страницы

Каждое утверждение страницы привязано к закреплённой ревизии. Откройте путь, чтобы увидеть точный источник.

universe-index-atomicals-nfts-and-realms

Universe Atomicals NFT, Realm, and Subrealm index

Ревизия 1d9109c68d95

Открыть закреплённый путь: server

Materialized read model for plain NFTs, Realms, and Subrealms projected from Atomicals ElectrumX.

atomicals-js-cli

Atomicals JavaScript CLI

Ревизия 1333565efbfe

Открыть закреплённый путь: commandIndex

Reference command surface used for the documented CLI inventory and the visual asset provenance.

Inspect an Atomical

Raw

Read identity, location, history, and sealed state, and know which of the four you are actually looking at.

Universe implementation Verified 2026-08-31 Metadata & Sources

Describes what a Bitcoin Universe service actually does today. It is not a statement about the protocol in general.

Page ID
guides/inspect-an-atomical
Normative authority
Universe implementation documentation
Networks
mainnet
Documentation version
2026.08
Audience
everyone, holder, developer
Owner
bitcoin-universe-docs
Sources

Это содержимое пока не доступно на вашем языке.

  • Supported networks: mainnet.
  • Status: Universe implementation for the read model, protocol behavior for the underlying facts.
  • Read only.

The Atomical ID, in the form <txid>i<index>. If you only have a name, resolve it first. See inspect a ticker.

  1. Read the asset by Atomical ID.
  2. Confirm the type and subtype. A plain NFT, a Realm, a Subrealm, a Container, and a DMINT item are different things.
  3. Read the current location and owner script.
  4. Read the history. Look at what changed and when, not only at the current state.
  5. Check the sealed flag. Unsealed state can change.
  6. Read the metadata, and treat every field as unverified.
  7. Record the generation identifier and indexed height.
Command Reads
get The Atomical
location Current location
state and state-history State, now and over time
tx-history Transaction history
at-location What is at an outpoint
ftinfo Fungible token details

See the CLI reference.

  • The number is not the identity. Key on the Atomical ID.
  • Metadata proves nothing. See metadata trust.
  • A media file is hostile input. Do not render it in a trusted context.
  • A name in the payload is not the name it won. Resolve names separately.

If you are about to act on what you read, re-read at a current generation immediately before acting. A location read minutes ago can be stale.

Atomicals digital objects and NFT and Realm API.