Deploy

Deployment requires JSON to be prefixed, and then the content encoding is sent to the specified address 0x0000000000000000000000000000000000000000. If the JSON is legal and the check has not been deployed, it is a valid deployment.

When deploying, we need to specify some required fields.

Key	Required	Description
p	yes	protocol name，ierc-20
op	yes	operation type: "deploy" | "mint" | "transfer" | "proxy_transfer" | "freeze_sell". Use "deploy".
tick	yes	token name.
max	yes	max supply.
lim	yes	limit for each mint.
wlim	yes	limit for each address can maximum mint.
dec	yes	decimal for minimum divie.
nonce	yes	don't repeat numbers with yourself.

Requires attention:

• tick itself is case-sensitive, but it is recommended that the index be case-insensitive.

• Since different indexes have different versions of JSON, here is a restriction, the last field of JSON cannot have a comma (,).

For example:

// deploy; send 0eth from self to 0x0000000000000000000000000000000000000000;
{
    "p":"ierc-20", //protocol name: ierc20
    "op":"deploy", //operation: deploy/mint/transfer/freeze_sell/proxy_transfer
    "tick":"ethi", //token tick, can't be repeatable, case insensitive.
    "max":"21000000", //max supply
    "lim":"1000", //limit for each mint
    "wlim":"10000", //limit for each address can maximum mint, address balance < deploy.wlim (Before mint, please do not receive transfers from others, transfers are also counted as balance)
    "dec":"8", //decimal for minimum divie
    "nonce":"0", //increasing interger
}