List an ARC-20 lot

Before you start

• Supported networks: mainnet.
• Status: Universe implementation. Action gates default to off.
• Your lot must be a clean, unmixed coloured output.

The lifecycle

1. Challenge. Request an authentication challenge.
2. Verify. Prove control of the owner address with a BIP-322 simple proof for P2WPKH or key-path P2TR. This issues a short lived owner session. It does not move anything.
3. Prepare. Submit the listing intent. The authority resolves the ticker to its verified winner and verifies the collateral against Bitcoin Core and the Atomicals provider, under one stable checkpoint.
4. Sign. Sign what the prepare step returned, with the exact scope it specifies.
5. Finalise. Submit the signed material. The listing becomes active.

What the authority checks before accepting your lot

The 9 October 2026 source repair is awaiting functional qualification and release. The sale consumes the whole selected Bitcoin output; exact token quantity is recorded separately from its Bitcoin value. A verified single-FT allocation smaller than collateral remains eligible; missing quantities and mixed or ambiguous allocations do not. Protocol validity alone does not bypass the marketplace’s ownership, confirmation, checkpoint and signature checks.

Marketplace v1 accepts priceAtomic per token and calculates the lot total as priceAtomic times quantityAtomic. Core Portfolio’s signed-offer lane instead accepts a whole-lot priceSats total. For 600 tokens on 1,000 sats collateral, a 1,200-sat total means 2 sats per token. Bitcoin output and payout checks retain their exact satoshi values.

The candidate does not establish mainnet activation or a completed test-network journey. Private Signet requires challenge, rule profile, interpreter artifact and isolated database attestation. Funded real-wallet flows and publisher gates remain outstanding; listing gates stay closed where qualification is missing.

• The ticker resolves to its verified Atomical FT winner.
• Bitcoin Core reports a confirmed, live output with the exact value and owner script.
• The Atomicals provider reports exactly that location, script, value, and one authoritative FT.
• The script hash view reports exactly one active row with the exact positive token amount for that Atomical; Bitcoin collateral is checked independently.
• Heights and hashes on both sides stay unchanged across the verification bracket.

Any disagreement, or any movement mid-check, fails the request closed.

Always rejected

Mixed collateral, spent outputs, checkpoint drift, ambiguous balances, Atomicals operations, burns, and output assignments that do not move the exact selected Atomical.

Check before signing

• The asset in the listing is the Atomical ID you intend, not just the ticker.
• The price and the exact payment script are what you agreed.
• The signature scope binds the payment output exactly.
• The listing does not spend anything now. Only settlement does.

If it fails

Failure	Meaning
Owner session missing or expired	Redo the challenge and verify steps
Mixed collateral	Separate the output first
Checkpoint drift	The chain moved mid-check. Retry
Gate disabled	Listing is not enabled on this deployment

After

Read the listing back and confirm the asset, price, and payment script. Your lot stays in your control until a settlement transaction is signed and broadcast.

Source

Marketplace v1 and transfers and swaps.