> For the complete documentation index, see [llms.txt](https://docs.metacces.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metacces.com/whitepaper/metacces-general/ar-vr-game/blacxes/what-is-blacxes.md).

# What is Blacxes

<figure><img src="https://1105197726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5MxHHh5RSa4XrEiBv01y%2Fuploads%2FscHQVvELb6dfebvZoOOo%2FMinimal%20Modern%20You%20Are%20Enough%20Quote%20Desktop%20Wallpaper.png?alt=media&amp;token=37878a63-581f-4858-9eba-42250e79b394" alt=""><figcaption></figcaption></figure>

It is a new, shiny black substance, created by Metacces.**BLACXES (DNA)** is the lifeblood of the Metacces ecosystem, revolutionize the concept of NFTs by integrating real ownership and active participation. These unique tokens grant investors a Ownership rights, along with voting rights and financial dividends. Blacxes use cutting-edge blockchain technology for secure and transparent transactions, enabling fluid exchanges across various currencies. This system empowers users to create their own digital ecosystems and secure passive income, significantly impacting the future of the metaverse landscape.


---

# 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://docs.metacces.com/whitepaper/metacces-general/ar-vr-game/blacxes/what-is-blacxes.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.