Operation-Mint
By recording a minting event, you initialize the balance to the minter's address.
Only the first owner with a specific ID will receive the balance. Ethscriptions cannot recognize duplicates, so these ID fields act as a kind of random number and identifier.
To preserve sanity, all ZKC-20 events are prefixed with the raw JSON data.
Permissible Keys
Protocol
p
yes
Protocol: "ZKC-20"
Operation
op
yes
Specify the type of event, for here: mint
Ticker
tick
yes
Use the ZKC-20 token ticker you wish to mint. equivalent to a stock ticker, the symbol of ZKC-20 and limited to 1-12 characters in size. case insensitive.
Amount
amt
yes
specify the amount to mint, cannot exceed the mint limit lim set in the token's deploy event
Identifier
id
yes
For 'uniqueness'. The id field in the mint event is derived from the deploy event and follows a range from 1 through deploy's [max supply / mint limit] as a uint256 number. Has to be string for the JSON format. Only mint events with id values within this range are considered valid within the ZKC-20 standard.
This ensures that only mint events associated with the specified deploy parameters are recognized as valid ethscriptions.
Example of minting ZKC-20:
Mint 1,000 $tom. data:application/json,{"p":"ZKC-20","op":"mint","tick":"tom","amt":"1000","id": "1"} Just replace tick with your desired tick and id with a random number not used before.
Last updated