Deploy

Publish a token

A deploy publishes two outputs: the token card with the parameters, and the mint contract, still inactive. Nothing is issued yet and no name is claimed — symbols are not unique, and two tokens may carry the same one. What a deploy does fix, it fixes forever.

STEP 1Details

STEP 2Check

STEP 3Deploy

STEP 4Block

STEP 5Activate

STEP 6Live

Symbol One to twelve characters, A–Z and 0–9. Not unique: the id is what identifies your token.

Name

Issuance

Cap (satoshis; 100 sats = 1.00 token) —

Premint (satoshis) What you take at activation, in plain sight.

Max per mint (x) Per transaction, not per address. A contract has no memory of addresses.

Mint fee (sats) Paid to you per public mint, enforced by the contract.

Allow public minting Off means only you can issue, through issuer batches.

Default transfer fee

Only a default. The holder chooses per transaction.

Description (optional)

Website (optional)

Issuer name (optional)

Issuer .web3 name (optional) A claim on the card; verification comes from the ORDnet .web3 registry.

Icon (optional, PNG/JPEG/WebP/GIF, max 60 kB)

Links (optional) — X, Telegram, Discord, GitHub

The card only allows these four keys; everything on the card is immutable once deployed.

⚠

A deploy cannot be edited or undone Cap, premint, maximum per mint and the mint fee are fixed at deploy. There is no upgrade path and no admin key: not for you, and not for anyone else. Decimals are fixed at two for every ORD20 token, so a hundred units are one token.

Token card · output 0 application/json

What it costs

Deploying is signed in the ORD20 Wallet browser extension. Two transactions, one block apart: the deploy, then the activation.