Operation: Mint
once a token has been deployed, you can mint it.
By inscribing a mint event you initialize a balance to the minter's address.
Only the first owner with the specific id number receives the balance. Ethscriptions do not recognize duplicates, so the id fields acts as a sort of nonce and identifier.
All ESC-20 events are prefixed with data:application/json, before the raw JSON data (formatted without spaces or tabs) for sanity. Only ASCII characters are accepted as valid, to prevent users using homoglyphs to make ethscriptions appear legit.
Permissible Keys
Protocol
p
yes
Protocol: "esc-20"
Operation
op
yes
Specify the type of event, for here: mint
Ticker
tick
yes
Use the ESC-20 token ticker you wish to mint. equivalent to a stock ticker, the symbol of ESC-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 ESC-20 standard.
This ensures that only mint events associated with the specified deploy parameters are recognized as valid ethscriptions.
Example of minting ESC-20:
Mint 1,000 $tom.
data:application/json,{"p":"esc-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