Skip to content
On this page


Inscribe-Mint refers to the unique inscription of each mint event. The inscription on mint events of an ORC-20 project allows the receiving address to obtain an initial balance.

After minting, the initial balance can be transferred by transferring the mint inscription before the first full transaction. However, after a full transaction occurs, the mint inscription becomes invalid and the balance cannot be transferred.

Note. If the Inscribe-Mint event exceeds the max supply of the ORC-20, it will be considered invalid.

pyesProtocol: orc-20 or orc20 case-insensitive. (OIP-1)
Any ordinal tokens supporting ORC-20 implementation (like src-20, xrc-20, including wrapped BRC-20) can be included for wider adoption.
tickyesTicker: symbol of ORC-20 in any size, eg. ORC = orc
idyesIdentifier: inscription number.
Subsequent operations must use the inscription number (OIP-3).
eg. Initial ORC-20 deployment doesn't require id; but you must specify the inscription number of the deployment for subsequent mint, send, migration, and upgrade.
opyesOperation: mint event, specify the type of event, eg. deploy, mint, send, cancel
amtyesMint Amount: specify the amount to mint, cannot exceed the mint limit set in deploy event
msgnoMessage: custom text, message, or manifesto in any size


The example below shows that 10,000 ORC was minted with id #2504160, which is the inscription number when the orc was deployed.

  "p": "orc-20",
  "tick": "orc",
  "id": "2504160",
  "op": "mint",
  "amt": "10000"