ARC-20 Bitwork requirements
Which Bitwork fields apply to a deployment, which apply to its claimants, and how to read them correctly.
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
-
protocol/arc20/bitwork-requirements - Normative authority
- Atomicals reference implementation
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- creator, developer
- Owner
- bitcoin-universe-docs
- Sources
-
- Atomicals ElectrumX
at
v1.5.2.0 - Atomicals JavaScript CLI
at
1333565efbfe
- Atomicals ElectrumX
at
Este conteúdo não está disponível em sua língua ainda.
Four Bitwork fields appear around ARC-20. They apply to different transactions and different people.
| Field | Applies to | Set by |
|---|---|---|
bitworkc |
The deployer’s own commit transaction | The deployer, per invocation |
bitworkr |
The deployer’s own reveal transaction | The deployer, per invocation |
mint_bitworkc |
Every claimant’s commit transaction | The deployment, for everyone |
mint_bitworkr |
Every claimant’s reveal transaction | The deployment, for everyone |
The two mint_ fields are the ones that matter to a minter. They come from the deployment and
apply to every claim, regardless of what the deployer paid for their own transactions.
Reading them correctly
Section titled “Reading them correctly”- Read the deployment record, not the deployer’s transaction.
- For a perpetual deployment, read the current requirement rather than the initial one.
- Apply the commit requirement to the commit transaction id and the reveal requirement to the reveal transaction id. They are separate searches.
- Recompute your fee estimate after a successful grind, because grinding changed the transaction.
Each extra hexadecimal character multiplies expected attempts by sixteen. See Bitwork for the table and the Bitwork estimator to model a specific prefix.
CLI options
Section titled “CLI options”From the generated inventory, the relevant flags are --bitworkc, --bitworkr, --mintbitworkr,
and --disablechalk. See the CLI reference.
What Bitwork does not do
Section titled “What Bitwork does not do”It does not reserve the ticker, prove identity, guarantee your claim wins the quota race, or make the mint fair. It raises the cost of spam.