Mint ARC-20
Claim against a deployment without wasting a fee on a claim that was never going to be valid.
Protocol behavior Verified 2026-08-31
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
-
- Atomicals JavaScript CLI
at
1333565efbfe - Atomicals ElectrumX
at
v1.5.2.0
- Atomicals JavaScript CLI
at
- Known limitations
-
- A confirmed Bitcoin transaction is not a successful mint. Quota, height, and Bitwork are checked by the validator, not by Bitcoin.
本頁內容尚未翻譯。
Before you start
Section titled “Before you start”- 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.
Check before you build
Section titled “Check before you build”- Resolve the ticker to a verified winning Atomical ID.
- Confirm the Atomical ID matches the one the project published.
- Read the deployment: mode, mint amount, maximum mints, mint height, Bitwork.
- Read claims made so far, with the height that figure came from.
- Confirm the current height is at or past
mint_height. - 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.
The command
Section titled “The command”yarn cli mint-dft <ticker>Useful options: --current, --initialowner, --funding, --satsbyte, --rbf,
--disablechalk. See the CLI reference.
What happens
Section titled “What happens”- Commit transaction, ground if commit Bitwork applies.
- Reveal transaction, ground if reveal Bitwork applies.
- Output zero of the reveal carries exactly
mint_amountsatoshis.
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.
If it fails
Section titled “If it fails”| 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 |
After broadcast
Section titled “After broadcast”- Confirm on Bitcoin.
- Wait for indexing at that height.
- Read the claim result. A confirmed transaction is not a successful mint.
- If valid, read your new coloured outpoint and record it.
- Move it into your protected pool. See protect coloured outputs.