launching a token
What you have to prepare before opening the form, the parameters the program will accept, and what you give up permanently.
what you give up
Read this part first, because it is the part that cannot be undone. When the launch transaction confirms, you have no further authority over the token. There is no update instruction, no stored admin key and no setter. The creator field on the config is attribution and is never accepted as a signer by anything. §2.1
Supply, emission schedule, difficulty, round length and the creator allocation are frozen at that moment. The mint authority is revoked in the same transaction, so not even the Lode program can create another unit. §2.4
prepare in the form
- 01
choose the image
Drop one PNG, JPEG or WebP image into the image field, or choose a file from your device. The browser checks the real file type and shows a circular preview before any wallet action.
- 02
approve storage separately
Review the quoted cost, then approve the creator-funded upload. The browser sends the image and generated JSON directly to Irys. Lode holds no storage credential and runs no paid upload proxy. Devnet uses temporary Irys test storage; mainnet uses permanent Irys mainnet storage.
- 03
check it resolves
Before building the transaction, the browser fetches the document and refuses to proceed unless the name and symbol match exactly and the image is content-addressed. The uploaded image and metadata are also read back byte for byte. Devnet also accepts an existing content-addressed metadata URL. Mainnet requires the verified upload in this form. §2.5
- 04
sign once
One transaction creates the mint, the config, the emission vault, the stake vault and the immutable metadata account, mints the full supply, revokes the mint authority, and opens the Raydium pool: your chosen pool SOL pairs with the pooled share of the allocation, the rest lands in your wallet, and Raydium charges a fixed 0.15 SOL pool creation fee. §1.4
what the program will accept
These bounds are compiled into the program and checked in the launch instruction. Because no admin exists afterwards, they are the only protection against absurd parameters, and nothing can widen them later. §2.2
- round length
- 30 to 3,600 seconds
- halving interval
- 1,440 to 5,256,000 rounds
- creator allocation
- 0 to 1,000 bps, must be at least one base unit
- decimals
- exactly 6
- equihash
- exactly n=96, k=5
- base weight
- exactly 0
- name
- 32 bytes
- symbol
- 10 bytes
- metadata uri
- 200 bytes
- difficulty target
- non-zero
- schedule
- must be able to release the whole mineable allocation
Version 1 of this site exposes one fixed preset rather than free numeric inputs: a 3,000,000 token supply, a 5% creator allocation leaving 2,850,000 mineable, 60-second rounds, halvings every 96,480 rounds, and an opening reward of 14.769908 tokens.
the creator allocation
The allocation is capped at 10% and must be greater than zero, because a token with no circulating units has nothing anyone could stake to mine it. It is recorded on the config, emitted in the launch event, and paired with your SOL in a Raydium pool created in the same transaction, so the token trades from its first second. §2.3
You receive the pool's LP tokens and they are not locked. Raydium charges a fixed 0.15 SOL pool creation fee on top of the launch fee, and nothing about launching here implies an aggregator listing or a verification badge.
this page expands
- 2.2Launch parameters are validated against fixed ranges, then frozen
- 2.4The supply cap is structural at the token-program level
- 2.5Metadata is immutable and is funded by the creator
- 2.3The creator allocation is capped at 10% and is displayed at full size
The paper is the authority. Where this page and §2.2 disagree, the paper is right and this page is a bug.