> For the complete documentation index, see [llms.txt](https://arcane-studios.gitbook.io/sentinel-whitepaper-v1.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arcane-studios.gitbook.io/sentinel-whitepaper-v1.0/introduction/eternis-death-match-introduction.md).

# Eternis Death Match Introduction

## A picture is worth a thousand words

One of the primary functions of the Sentinel token is to drive the economy of the Eternis Metaverse. As a dynamic fighting game, Eternis benefits significantly from the integration of a Web3 infrastructure. This allows for a robust digital asset management system that supports a dual-token setup, enhancing the gaming experience. The inclusion of Web3 technology enables seamless transactions and interactions within Eternis, making Sentinel essential for a vibrant, interactive Metaverse economy.

{% embed url="<https://www.youtube.com/watch?t=2s&v=yna0wCFVtpg>" %}

{% embed url="<https://www.youtube.com/watch?v=nQzSUkOTu2A>" %}


---

# 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://arcane-studios.gitbook.io/sentinel-whitepaper-v1.0/introduction/eternis-death-match-introduction.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.