BRC-20 (5-byte)

• Proposal for Issuance and Burn Enhancements

A new field called (self_mint) can be added to the original BRC-20 protocol's deploy operation. This setting ensures that only the deployer can issue the current asset. The meanings of the other fields remain the same as in the original BRC-20 rules, such as setting (max) for the maximum issuance and (lim) for the limit per issuance, etc. Under this mode, when issuing the mint inscription, the deploy inscription must be used as the parent of the mint inscription; otherwise, the mint is invalid.

{
  "p": "brc-20",
  "op": "deploy",
  "self_mint": "true",
  "tick": "ordi",
  "max": "21000000",
  "lim": "1000"
}

• When (max=0), BRC-20 rules do not allow this situation, but it is reasonable to define (max=0) as allowing an unlimited maximum issuance for self_mint. (BRC-20 itself requires the maximum asset limit to be max_uint64, which we continue to use here).

{
  "p": "brc-20",
  "op": "deploy",
  "self_mint": "true",
  "tick": "ordi",
  "max": "0",
  "lim": "1000"
}

Adopting 5-bytes Tickers. In this way indexers not prepared yet will simply ignore these assets.