> 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)

### **What is GNFT?**&#x20;

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?**&#x20;

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.&#x20;

### **Unique features of GNFT**&#x20;

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**&#x20;

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 dynamically by asking a question.

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

```
GET https://hello.kodadot.xyz/nft-standard/smart-contracts/gnft-erc-721.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.
