Operation-Deployment
Deploying the new ZKC-20
By logging deployment events, you can deploy ZKC-20.
You must hold the Deployment Inscription to gain ownership of the ZKC-20
To preserve sanity, all ZKC-20 events have a suffix prepended to the raw JSON data. data:application/json, only accepts ASCII characters as valid characters.
Permissible Keys
Name | Key | Required | Description |
---|---|---|---|
Protocol | p | yes | Protocol: "ZKC-20" |
Operation | op | yes | Specify the type of event, for here: deploy |
Ticker | tick | yes | equivalent to a stock ticker, the symbol of ZKC-20 and limited to 1-12 characters in size. case insensitive. |
Max Supply | max | yes | Limited to uint256, set the max supply of the token here. Has to be string for the JSON format. |
Mint Limit | lim | yes | Limited to uint256, max amount that can be minted per ethscription. Has to be string for the JSON format. |
*Example of a new ZKC-20 with defaults:* Deploy ZKC-20 named by tick $tom with max supply of 21,000,000 and limit 1000 per mint.
data:application/json, { "p" : "ZKC-20" , "op" : "deploy" , "tick" : "tom" , "max" : "21000000" , "lim" : "1000" }
Last updated