# Mint Event Type

This rule type allows tracking both <mark style="color:yellow;">**1/1 NFT collection type**</mark> and <mark style="color:yellow;">**Edition collection type**</mark>**&#x20;**<mark style="color:$danger;">**Mint**</mark> events. The <mark style="color:yellow;">**1/1 NFT collection type**</mark> tracking guaranteed works for supported <mark style="color:$warning;">**EVM**</mark> chains and <mark style="color:$warning;">**Solana**</mark>. The <mark style="color:yellow;">**Edition collection type**</mark> tracking guaranteed works for supported <mark style="color:$warning;">**EVM**</mark> chains, but <mark style="color:red;">didn't test on</mark> <mark style="color:$warning;">**Solana**</mark>.

## <mark style="color:$primary;">Explanation of the Fields.</mark>

* In the <mark style="color:$primary;">**Rule Name**</mark> field, enter your desired rule name.
* In the <mark style="color:$primary;">**Blockchain**</mark> dropdown, select the blockchain where your collection contract is deployed.
* In the <mark style="color:$primary;">**Contract**</mark> field, enter the <mark style="color:yellow;">**1/1 collection type**</mark> or <mark style="color:yellow;">**Edition collection type**</mark> [collection contract address](/appendix/getting-collection-contract-address.md).
* In the <mark style="color:$primary;">**Info Channel**</mark> dropdown, select the prepared <mark style="color:yellow;">**#events-tracker**</mark> channel you wish to send the embeds.

{% hint style="danger" %}
Be especially careful when setting the <mark style="color:$primary;">**Contract**</mark> field for <mark style="color:$warning;">**Solana**</mark> collections! Check this [link](/appendix/getting-collection-contract-address.md) before starting!
{% endhint %}

## <mark style="color:$primary;">Setting Up the Rule.</mark>

<figure><img src="/files/HtT1ntqojzR7aqORPJ2l" alt=""><figcaption></figcaption></figure>

Depending on [your tier](/plugins/nft-tracker/introduction.md#capabilities-comparison), to see the first embeds in your prepared <mark style="color:yellow;">**#events-tracker**</mark> channel, you will have to wait up to 15 minutes after the rule is created.

## <mark style="color:$info;">Examples of the embeds.</mark>

The <mark style="color:yellow;">**1/1 NFT collection type**</mark> <mark style="color:$danger;">**Mint**</mark> embed will look like this:

<figure><img src="/files/VRWIRAfJBnBrlYaoI9IZ" alt=""><figcaption></figcaption></figure>

The <mark style="color:yellow;">**Edition collection type**</mark> <mark style="color:$danger;">**Mint**</mark> embed will look like this. The additional <mark style="color:$primary;">**Amount**</mark> field reflects how many editions of the NFT with this ID were minted during the transaction.

<figure><img src="/files/7vLJCheDM326BiTjVq4b" alt=""><figcaption></figcaption></figure>


---

# 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://guide.bocto.octopeeps.com/plugins/nft-tracker/discord-tracker-rules/mint-event-type.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.