launching a token

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 Gems program can create another unit. §2.4

1. 01

   upload the image

   Permanent storage, addressed by content: Arweave, Irys or IPFS. Gems holds no storage credential and runs no upload proxy, so this is yours to do and to pay for.

2. 02

   upload the metadata document

   A JSON document at a permanent URI of 200 bytes or fewer, carrying the exact name and symbol you are about to put on chain and pointing at the content-addressed image. Description and links belong in this document, not on the launch form.

3. 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. An upload that has not propagated yet will fail this check. §2.5

4. 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, sends your allocation to your wallet, and revokes the mint authority.

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 Gems allocation

Version 1 of this site exposes one audited preset rather than free numeric inputs: a 3,000,000 token supply, a 5% creator allocation leaving 2,850,000 Gems, 60-second rounds, halvings every 96,480 rounds, and an opening reward of 14.769908 tokens.

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 dig it. It is minted straight to your wallet, recorded on the config, emitted in the launch event, and displayed on the token page at the same size as every other fact. §2.3

Gems does not create or lock a liquidity pool. Your allocation stays in your wallet unless you move it yourself, and nothing about launching here implies a market, a lock, an aggregator listing or a verification badge.