deploy a ticker.
mint it by inscription.

none of this is a contract. a token here is a set of rules written into calldata, and a balance is what you get by replaying every inscription under the tag that was reported within its ten minutes, in the order the chain recorded them. two readers agree because the rules are the same and the order is the chain's, not because anything on chain is enforcing them.

someone writes a deploy: a ticker, a maximum supply, and how much a single mint may take. the first deploy of a ticker wins and every later one is ignored, so a ticker cannot be taken twice.

after that anyone may mint it, the per-mint size each time, until the maximum is reached. a mint that would go past the maximum is refused rather than trimmed, so the supply is exactly what was declared and never a rounding of it.

a mint takes exactly the per-mint size, and a mint of any other amount is ignored. a short mint would leave a balance that no transfer and no listing could move, because both of those require whole mint units. one mint is one unit, so every balance stays something that can be sent and sold.

once rules v2 is active a ticker may also be 1 to 8 han characters from U+4E00 to U+9FA5. simplified and traditional forms are different tickers, like 龙 and 龍. when a ticker differs from a deployed one only by that or by a look-alike character, the page flags it and shows each one's deploy block.

declare your own on the inscribe page.