> For the complete documentation index, see [llms.txt](https://elindos-phar.gitbook.io/exode-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elindos-phar.gitbook.io/exode-white-paper/white-paper/trust.md).

# Trust

EXODE acts as an authority to **recognize validity of assets** which participate in its game interface.\
\
This enables trusted accounts and NFT assets to be used ingame and **protects players against many kinds of unfair abuse** such as pirated assets.\
\
The blockchain itself guarantee lifetime ownership of EXODE assets, but ownership alone does not make the interactivity and reliability of a game entertainment.\
\
The game also has [**a strong policy against bots and multiaccounts**](/exode-white-paper/white-paper/10-designs-against-bots-and-multiaccounts-our-nbp.md), detailed further in the valuation and player ownership policy and insured both in technicity and design.\
\
EXODE also regularly publishes broadcasts along with public information on its broadcasted contents, which in turn, also allows for **Blockchain Replay**.\
\
Blockchain Replay is the process by which you can decide to read the blockchain from a point up to another, and replay it up until that point, guaranteeing safety of ownerships in the trusted environment. Sharing information about Blockchain Replay means that any developer can have enough clarity to restore EXODE services, if inclined to do so and felt acceptable by EXODE owners.\
\
The trusted environment, the easiness to make a blockchain replay and repair any situation, and the valuation policy, **are strong elements to guarantee longterm success of a blockchain game** and which also protect the game and players **from all kinds of harmful actions.**\ <br>


---

# 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://elindos-phar.gitbook.io/exode-white-paper/white-paper/trust.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.