> For the complete documentation index, see [llms.txt](https://document.sunprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://document.sunprotocol.io/en/smart-contracts/node-nft-contract.md).

# Node Nft Contract

Maximum supply: `500`

### Read the current supply

Call `totalSupply()` for the number already minted. `MAX_SUPPLY()` returns the cap of `500`; current supply does not necessarily equal the cap.

### Find your token IDs

Call `getUserID(user)` with a wallet address to return every Token ID currently held by that wallet. `getUserNFTNum(user)` and the standard `balanceOf(user)` return the number held.

### Query by Token ID

| Function                          | Result                                |
| --------------------------------- | ------------------------------------- |
| `ownerOf(tokenId)`                | Current owner                         |
| `tokenURI(tokenId)`               | Metadata URI                          |
| `tokenByIndex(index)`             | Token ID at a global zero-based index |
| `tokenOfOwnerByIndex(user,index)` | Token ID at a user's zero-based index |

A nonexistent Token ID or out-of-range index reverts. IDs are minted sequentially from `1` in the published implementation.

`getAllHolders()` returns aligned `holders` and `balances` arrays. It iterates over the full collection and is best used as an off-chain read.


---

# 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://document.sunprotocol.io/en/smart-contracts/node-nft-contract.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.