跳转到内容

本页面的来源

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

atomicals-guide

Atomicals protocol guide

修订 unversioned

打开固定路径: specification

Concept and command-line explanation. Explicitly states that the specification is defined in code.

atomicals-electrumx-1.5.2.0

Atomicals ElectrumX

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

打开固定路径: mintParser

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

Source of truth

Raw

The authority order every technical statement follows, and how to resolve two sources that disagree.

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
develop/source-of-truth
Normative authority
Atomicals reference implementation
Networks
mainnet
Documentation version
2026.08
Audience
developer, operator, integrator
Owner
bitcoin-universe-docs
Sources

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

  1. Executed source code, conformance tests, generated route inventories, schemas, deployment manifests, and runtime contracts, at an exact revision.
  2. Final or Living Atomicals Improvement Proposals applicable to the feature.
  3. The official Atomicals reference implementation or released validator, at an exact commit or release.
  4. Official Atomicals protocol and CLI documentation.
  5. Universe implementation documentation, at an exact revision.
  6. Third-party integrations, always identified as third-party and non-normative.

Explanatory prose is never independent consensus, including this documentation.

Question Answered by
What does this transaction do? The validator revision you run, at that height
Is this rule active? The activation condition for your network
What does this API return? The service contract at its deployed revision
Is this proposal implemented? Implementation evidence, never the proposal itself
Does this product support it? The product’s own statement, dated

Do not vote. Check, in order:

  1. Same network?
  2. Same chain position, or is one behind?
  3. Same validator revision?
  4. Is the behavior activation sensitive at that height?
  5. Same projection?

Only when all five match does a disagreement mean one source is wrong. Until then it is a version, position, or scope difference.

Compare more than one compatible source, and treat any disagreement as a hold rather than a tie-break. Record the revision and generation of each answer so the difference can be explained afterwards.

Every source-sensitive page carries a source panel with the repository, the exact revision, the path, the applicable networks, the last verified date, and the known limitations. Where evidence is missing, the page says so rather than guessing.

See networks and versions.