> For the complete documentation index, see [llms.txt](https://whitepaper.cadenverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.cadenverse.com/blockchain-nft.md).

# Blockchain / NFT

In Cadenverse, blockchain and NFT will be used for 3 purposes:

* First, musicians, incarnated by the players, are unique and will grow with their owner. We will use NFT (Non-Fungible Token) technology to provide full ownership of the characters, abilities and associated collectibles to the players.
* Second, the music: the songs and sound mixes created on our platform will be NFT collectibles marked with immuable records of their history for their creators. As such, players can freely decide to exchange, give or sell those creations.
* Finally, tracking and paying for music rights: music usage has been a major issue of the music industry over the past 30 years. Especially in a digital environment with complex licensing rules and tracking systems. To reward our content artists, we will use a blockchain infrastructure to provide transparency and tracking of created contents.


---

# 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, and the optional `goal` query parameter:

```
GET https://whitepaper.cadenverse.com/blockchain-nft.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.