跳转到内容

本页面的来源

本页面的每条论断都对应固定的修订版本。打开路径即可查看验证所依据的确切来源。

atomicals-js-cli

Atomicals JavaScript CLI

修订 1333565efbfe

打开固定路径: commandIndex

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

atomicals-electrumx-1.5.2.0

Atomicals ElectrumX

修订 v1.5.2.0 (2025-03-27)

打开固定路径: realmValidation

Version-sensitive ARC-20 and Atomicals validation behavior used as the pinned reference baseline.

Claim a Realm

Raw

Request a top-level name, confirm it resolved to you, and protect the output that carries it.

Protocol behavior Verified 2026-08-31 Metadata & Sources

Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.

Page ID
guides/claim-a-realm
Normative authority
Atomicals reference implementation
Networks
mainnet
Documentation version
2026.08
Audience
everyone, creator
Owner
bitcoin-universe-docs
Sources

此内容尚不支持你的语言。

  • Supported networks: mainnet.
  • Status: protocol behavior. The Universe read model exposes realm resolution and hierarchy.
  • A request is not a name. It becomes one only when the rules resolve it.
  1. Search for the name. find-realms, get-realm, and realm-info read the current state.
  2. Check for existing candidates for the same name.
  3. Check for confusable variants that already exist. See Unicode and confusable names.
  4. Confirm the name passes validation for your target rule set.
yarn cli mint-realm <realm>

Options include --satsoutput, --initialowner, --container, --bitworkc, --bitworkr, --funding, --satsbyte, --rbf. See the CLI reference.

Two Bitcoin fees, grinding if you set Bitwork, and the output value that will carry the Realm.

  • The name is exactly the string you intend, character by character.
  • No confusable variant is already claimed by someone else.
  • The output value is above the dust threshold.
  • The funding input is cardinal.
  1. Confirm, then wait for indexing.
  2. Read the resolution. Confirm you are the verified winner, not a pending or losing candidate.
  3. Record the Atomical ID.
  4. Move the output into your protected pool. Losing that output loses the name.
  5. If you plan to allow Subrealms, configure the rules deliberately. See claim a Subrealm.

Another claim resolved first. Your Atomical exists without the name. Do not present it as the Realm.

Realms and candidates and winners.