# Mint an NFT (721)

This task can be a powerful tool for driving engagement with your NFT projects, rewarding early adopters, or encouraging participation in exclusive communities or events.

## **General settings** <a href="#general-settings" id="general-settings"></a>

For instructions on setting up the general parameters of your Web3 task (name, header, description, etc.), visit [**Web3 tasks**](https://claimr-io.gitbook.io/claimr-help-center/tasks/web3-tasks).

## **Task type selection** <a href="#task-type-selection" id="task-type-selection"></a>

* Select **Web3** to indicate that the task will be completed using a Web3 action.
* Once you've selected Web3, choose **Mint an NFT (721)** from the dropdown menu.

## **Task settings** <a href="#task-settings" id="task-settings"></a>

{% hint style="info" %}
**Pro tips**

* Provide clear and concise instructions on how to mint the NFT, including any necessary steps like connecting a wallet, approving transactions, or paying minting fees.
* Specify the NFT collection or project name, the benefits of owning the NFT, and any relevant links (e.g., to the minting website or marketplace) in the task description.
* Consider displaying images or previews of the NFTs within the task description to make it more engaging.
  {% endhint %}

<figure><img src="https://2111509621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBtEHhi1fQEriwxTxRejw%2Fuploads%2FHN4302Y6Aqa1drUAE321%2FScreenshot%202024-10-08%20at%2001.20.01.png?alt=media&#x26;token=bcee0cf8-e9e5-451e-9900-0b95b1b787e9" alt="" width="375"><figcaption><p>Task settings</p></figcaption></figure>

### **Network**&#x20;

Select the blockchain network on which the NFT will be minted. In the example, Ethereum Mainnet is selected.

### **Contract address**

Enter the contract address of the NFT collection or project. This is the address where the NFT smart contract is deployed.

### **Has server signature support (optional)**

Enable this toggle if your NFT minting process requires server-side signature support. This is an advanced security feature that protects your NFT mint from unauthorized minting by external users.

To utilize this feature, you will need a special contract template. Request this template from the сlaimr support team.

#### **Why server-side signature is important?**

All data and events on the blockchain are publicly accessible. This means that anyone with technical knowledge can potentially exploit the NFT minting process. They could bypass your campaign's tasks and mint NFTs directly to their own wallets.

claimr's server-side signature adds a layer of protection. It utilizes a secure server-side wallet to sign a special message that is verified within the NFT contract. This ensures that only authorized mints initiated through your claimr campaign can be successful.

### **Allow multiple mints? (optional)**

Enable this toggle if you want to allow users to mint multiple NFTs within this task.

By default, a wallet is typically allowed to mint a specific token only once. However, with this option enabled, the token can be minted multiple times across different tasks. They must be different tasks.

### **Mint fee (optional)**

If there's a fee associated with minting the NFT, specify the amount here. You can also specify the token in which the fee is paid (e.g., ETH, stablecoins).

### **SB token? (optional)**

Enable this toggle if the NFT being minted is an SB (soul-bound) token. This option allows users to mint the token again even if they have already minted it previously but not within your campaign. claimr will check the user's balance of this token. If it's greater than 0, the task will be marked as completed after the user clicks <mark style="color:green;">**Complete**</mark>.

### **Wallet already connected? (optional)**

This option ensures a smooth and efficient minting experience for users in specific web browser environments where wallet connections are managed externally via SDK.

* Enable this toggle if your campaign is running in a web browser environment where the user's wallet is already connected via SDK (Software Development Kit). This is particularly relevant for those who operate solely within a web browser environment and handle wallet connections through their own applications.
* **How it works:** Typically, when a user encounters an NFT minting task in claimr, they are prompted to connect their wallet before proceeding with the minting process. However, in cases where the client's application has already facilitated the wallet connection and provided claimr with the necessary wallet information via the SDK, this step becomes redundant.
* By enabling this toggle, claimr will recognize the existing wallet connection and bypass the connection prompt, directly initiating the minting process. This streamlines the user experience and avoids unnecessary steps for users who have already connected their wallets through the client's application.

\\
