inscribe

deploy declares a ticker that does not exist yet: its name, the total that will ever exist, and how much a single mint takes. the ticker belongs to the first deploy of it, and every later one is ignored. it gives you no tokens.

mint takes one share of a ticker somebody already deployed, exactly its per-mint size. that is the one that gives you a balance. you may mint the same ticker twenty times and no more, which is what stops the first script to see a deploy from taking all of it. there is a mint button beside every ticker on the tokens page, which is easier than typing one here.

transfer sends whole mint units of a token you hold to another address. an amount you have listed for sale is not free to send until the listing is cancelled and its lock (ten minutes, twenty from rules v2) has passed.

chinese tickers count only once rules v2 is active. before then this page does not build a deploy, mint or transfer of one, because the index would ignore it.

each template writes a small json object with a p field. that field is the protocol tag, and it is the only reason a reader can pick your writing out of everything else on the chain. the templates here all write rbrc.

you are not required to use them. pick free text and write whatever bytes you like: text that is not json is still an inscription and is still indexed. the templates exist so that the common shapes are consistent enough to be read by more than one program.

this page records writing; it does not decide what a protocol means. what the words under a tag are worth is up to whoever defines that protocol, and anyone can define a new one by writing inscriptions with a new tag.