Create DMINT items

Before you start

• Supported networks: mainnet.
• Status: protocol behavior.
• You need a Container whose name already resolved to your Atomical ID. See create a Container.

Order matters more than anything else here

Seal first, then open minting. A manifest that can still be edited while people mint against it makes every verification meaningless.

The procedure

1. Assemble the final item set in a folder. Final means final.

2. Build the manifest:

   yarn cli prepare-dmint <folder> <mintHeight> <bitworkc>

3. Prepare the item files with prepare-dmint-items.

4. Verify locally that every item you intend to allow is in the manifest, and nothing else is.

5. Attach it:

   yarn cli enable-dmint <container> <jsonFilename>

6. Read the manifest back from the chain and compare it byte for byte with what you built.

7. Only then seal:

   yarn cli seal <atomicalId>

8. Publish the Container Atomical ID, the sealed state, and the manifest.

9. Open minting at or after the mint height.

Step six is the one people skip. Read back what is actually on chain before making it permanent.

What claimants do

yarn cli mint-item <container> <itemId> <manifestFile>

They can check first with validate-container-item, without minting.

Failure states for a claimant

State	Cause
Item not in the manifest	Wrong identifier
Digest mismatch	Content differs from the manifest entry
Before mint height	Claimed too early
Bitwork not satisfied	Grinding incomplete
Payment missing or wrong	A payment rule was not satisfied
Already claimed	Someone else won the race

Every one of those produced a confirmed Bitcoin transaction and cost a fee.

After

Verify a sample of minted items against the manifest yourself, and publish the verified item count alongside the manifest total.

Source

DMINT and sealing and rules.