Index Rules

• Transaction data converted to text must start with "data:${mime-type}," or it won't be indexed. $mime-type can be left blank, e.g. "data:,"

• Only one mint is valid per address per block, multiple mints are invalid

• Each transfer inscription can only be used once

• The first deployment of a ticker is the only one that has claim to the ticker. Tickers are not case sensitive (DOGE = doge).

• If two events occur in the same block, prioritization is assigned via order they were confirmed in the block. (first to last).

• Minting transfer inscription to yourself first is necessary to avoid others spending your balance

• The mint function and the second step of the transfer function are the only events that cause changes in balances

• The first mint to exceed the maximum supply will receive the fraction that is valid. (ex. 21,000,000 maximum supply, 20,999,242 circulating supply, and 1000 mint inscription = 758 balance state applied)

• Mint function inscriptions do not have a padding requirement

• No valid action can occur via the spending of an ordinal via transaction fee. If it occurs during the inscription process then the resulting inscription is ignored. If it occurs during the second phase of the transfer process, the balance is returned to the senders available balance.

• Standard limited to uint128

• Maximum supply cannot exceed uint64_max