Skip to content

Sources behind this page

Every claim on this page resolves to these pinned revisions. Follow a path to read the exact source the statement was verified against.

atomicals-js-cli

Atomicals JavaScript CLI

Revision 1333565efbfe

Open pinned path: commandIndex

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

atomicals-electrumx-1.5.2.0

Atomicals ElectrumX

Revision v1.5.2.0 (2025-03-27)

Open pinned path: realmValidation

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

Claim a Subrealm

Raw

Satisfy a parent Realm's rules, including any payment, and confirm you actually won the name.

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-subrealm
Normative authority
Atomicals reference implementation
Networks
mainnet
Documentation version
2026.08
Audience
everyone, creator
Owner
bitcoin-universe-docs
Sources
Known limitations
  • Rules can be changed by the parent. Read them at the height you are claiming at, not from a cached page.
  • Supported networks: mainnet.
  • Status: protocol behavior.
  • The parent controls the rules and can enable or disable claiming.
  1. Read the parent Realm’s current Subrealm rules, at a current height.

  2. Confirm Subrealm claiming is enabled.

  3. Confirm the name is available and has no competing candidate.

  4. Build a claim that satisfies every rule, including the payment output and its marker if a payment is required.

  5. Mint:

    yarn cli mint-subrealm <realm>
  6. Confirm and wait for indexing.

  7. Confirm you are the verified winner.

Where a rule requires payment, all of the following must be true in the same transaction:

  • the payment goes to the exact output the rule specifies;
  • the amount is exact;
  • the payment marker is present and well formed.

Paying the right amount to the wrong script makes the claim invalid, and the fee is spent.

  • The rules you built against are the rules currently published.
  • The payment output script and value are exactly as required.
  • The payment marker is present.
  • The name is exactly the string you intend.
Failure Meaning
Claiming disabled The parent turned it off
Rule not satisfied Re-read the rules and rebuild
Payment wrong Invalid claim, fee spent
Already claimed Another claim won
Pending, not resolved Wait. Do not present it as owned

Record the Atomical ID and move the output into your protected pool.

Subrealms and claims and rules.