> For the complete documentation index, see [llms.txt](https://hello.kodadot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello.kodadot.xyz/nft-standard/smart-contracts/gnft-erc-721.md).

# GNFT (ERC-721)

Learn about Gear Non-Fungible Tokens (GNFTs), their operation, unique features, and how they are integrated into the KodaDot platform on the Vara network.

### **What is GNFT?** 

Gear Non-Fungible Tokens (GNFTs) are unique cryptographic tokens on the Gear smart contract platform. They represent ownership of a unique digital asset. Each GNFT consists of a unique token identifier, commonly known as a token ID, mapped to an owner identifier stored within an NFT smart contract.

### **How does GNFT operate?** 

GNFTs function by utilizing the Gear smart contract platform. Advanced features such as transferring ownership, approval permissions, minting new tokens and burning existing ones are embedded within the smart contract. 

### **Unique features of GNFT** 

GNFTs distinguish themselves by possessing unique features made possible by the Gear smart contract platform. These include customizing the mint function, extending the default NFTCore trait, and tailoring the handle function to suit your NFT contract needs.

### **Conclusion** 

Enjoy the flexibility and control that GNFTs offer on the KodaDot platform within the Vara network. More info on GNFTs by Gear can be found [here](https://wiki.gear-tech.io/docs/examples/gnft-721).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hello.kodadot.xyz/nft-standard/smart-contracts/gnft-erc-721.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.