deploy

Description

Create a new KRC-20 token. The operation can specify "Mint Mode" or "Issue Mode".

Parameters

JSON format example:

{"p":"krc-20","op":"deploy", "tick":"kasp","max":"2100000000000000","lim":"100000000000","to":"kaspa:..."}

Mint Mode

Enabled when ( DaaScore >= 83441551 AND DaaScore <= 83525600 OR DaaScore >= 90090600 ).

Key	Required?	Description
p	Yes	Protocol header. Must be "krc-20" (case-insensitive).
op	Yes	Operation. Must be "deploy" (case-insensitive).
tick	Yes	Ticker. 4 to 6 letter unique identifier of the token (case-insensitive).
max	Yes	Max supply of the token, including decimal.
lim	Yes	The balance obtained for each mint, including decimal.
to	No	The deployer address of the token and receiver address of the pre allocated token (If pre is provided).
dec	No	Decimal. Default to 8.
pre	No	The amount of tokens allocated to a particular address after deployment.

Issue Mode

Enabled when ( DaaScore >= 110165000 ).

Key	Required?	Description
p	Yes	Protocol header. Must be "krc-20" (case-insensitive).
op	Yes	Operation. Must be "deploy" (case-insensitive).
mod	Yes	Deployment Mode. Must be "issue".
name	Yes	Token name: 4 to 6 letter, allow duplicates (case-insensitive).
max	Yes	max supply of the token, "0" means unlimited issuance, including decimal.
to	No	The owner address of the token and receiver address of the pre allocated token (If pre is provided).
dec	No	Decimal. Default to 8.
pre	No	The amount of tokens allocated to a particular address after deployment.

Notice

• if pre > max, only max amount of tokens will allocate to toaddress.

• To deploy a token, the transaction fee (gas fee) paid should not be less than 1000 KAS.
• If to field is not configured, it defaults to the transaction sender address.

• In "Issue Mode", Use the deployment transaction ID as the token contract address (CA).

• Use API to check whether the corresponding tick is available before deployment to avoid loss of transaction fee.