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-electrumx-1.5.2.0

Atomicals ElectrumX

Revision v1.5.2.0 (2025-03-27)

Open pinned path: mintParser

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

atomicals-electrumx-1.5.2.0

Atomicals ElectrumX

Revision v1.5.2.0 (2025-03-27)

Open pinned path: normalFtAllocation

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

atomicals-guide

Atomicals protocol guide

Revision unversioned

Open pinned path: arc20

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

ARC-20

Raw

The complete ARC-20 model in one page, from issuance through allocation to the safety boundary, with links to the exact rule for each part.

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
protocol/arc20/overview
Normative authority
Atomicals reference implementation
Networks
mainnet
Documentation version
2026.08
Audience
everyone, developer, creator
Owner
bitcoin-universe-docs
Sources
Known limitations
  • This is a compatibility guide, not an independent consensus specification. The Atomicals specification is defined in code.

ARC-20 is the Atomicals fungible token model on Bitcoin. One unit is one coloured satoshi. Everything else follows from that.

One unit is one satoshi

An ARC-20 balance is not a number stored somewhere. It is the satoshi value of the outputs a validator recognises as coloured for that token. An output worth 700 satoshis that a validator colours for a ticker carries exactly 700 units. Spending it spends the units. Splitting it splits the units, subject to the allocation rules.

  1. A unit is a satoshi in an output a validator recognises as coloured for a token.
  2. Supply is therefore measured in satoshis, and is bounded by real bitcoin.
  3. Issuance happens once, directly, or repeatedly through a deployment others mint against.
  4. A ticker is a globally allocated name resolved to exactly one Atomical.
  5. A transfer is an allocation over the transaction’s inputs and outputs, in order.
  6. Value that cannot be placed in an eligible output is destroyed.
  7. Coloured output totals can never exceed coloured input totals.
Area Page
The unit model and why decimals do not create fractions Unit model
Ticker allocation, candidates, and verified winners Tickers and candidates
One step issuance of a complete supply Direct issuance
Deployments with a fixed number of mints Fixed DFT
Claiming a mint against a deployment Decentralised mint
Activation gated progressive deployments Perpetual DFT
Work requirements on commit and reveal Bitwork requirements
Optional metadata and presentation decimals Metadata and decimals
How value is placed into outputs Allocation
Separating and recombining coloured lots Split and combine
How value is destroyed Burns
Moving tokens and swapping them atomically Transfers and swaps
What a PSBT must contain PSBT requirements
What a wallet must do to be safe Wallet safety
The status of Substantiation Factor material Substantiation Factor
  • Not an ERC-20 contract. There is no contract and no account.
  • Not an inscription balance. Value is the satoshi value of outputs, not a number written in text.
  • Not a claim on anything. Nothing backs a unit unless a separate legal arrangement exists, and none is created by minting.
  • Not an ARC-721 standard. No official source located during review establishes one.

The protocol supports direct mint-ft issuance. No Universe product surface exposes it today. Universe exposes verified ticker resolution, token details, holders, confirmed activity, portfolio balances, coloured UTXOs, and Marketplace v1 flows. See status and known limitations.