# 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

| Name       | Key  | Required | Description                                                                                                                                                                                                                                                                                                            |
| ---------- | ---- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://zkdx-inscriptions.gitbook.io/docs/zkc-20/operation-mint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.