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

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

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

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)

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

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

Mint ARC-20

Raw

Claim against a deployment without wasting a fee on a claim that was never going to be valid.

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/mint-arc20
Normative authority
Atomicals reference implementation
Networks
mainnet
Documentation version
2026.08
Audience
everyone, creator
Owner
bitcoin-universe-docs
Sources
Known limitations
  • A confirmed Bitcoin transaction is not a successful mint. Quota, height, and Bitwork are checked by the validator, not by Bitcoin.

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

  • Supported networks: mainnet.
  • Status: protocol behavior. Universe products expose decentralised mint flows.
  • You need funding for two fees plus the mint amount locked in output zero.
  1. Resolve the ticker to a verified winning Atomical ID.
  2. Confirm the Atomical ID matches the one the project published.
  3. Read the deployment: mode, mint amount, maximum mints, mint height, Bitwork.
  4. Read claims made so far, with the height that figure came from.
  5. Confirm the current height is at or past mint_height.
  6. Confirm the current Bitwork requirement, especially for a perpetual deployment.

If claims made is already at the maximum, stop. There is nothing left to claim.

yarn cli mint-dft <ticker>

Useful options: --current, --initialowner, --funding, --satsbyte, --rbf, --disablechalk. See the CLI reference.

  1. Commit transaction, ground if commit Bitwork applies.
  2. Reveal transaction, ground if reveal Bitwork applies.
  3. Output zero of the reveal carries exactly mint_amount satoshis.

Exactly. Not at least.

Two Bitcoin fees, grinding time, and mint_amount satoshis locked in output zero. In a contested mint, fee rates rise, so budget above the current rate.

Failure Meaning
Quota already full The claim is invalid. The fee is spent
Before mint_height Invalid. Wait and try again
Bitwork not met The grind targeted the wrong requirement
Wrong output zero amount Invalid. It must be exact
Ticker was a candidate, not a winner You minted against something that does not hold the name
  1. Confirm on Bitcoin.
  2. Wait for indexing at that height.
  3. Read the claim result. A confirmed transaction is not a successful mint.
  4. If valid, read your new coloured outpoint and record it.
  5. Move it into your protected pool. See protect coloured outputs.

Decentralised mint claims.