> For the complete documentation index, see [llms.txt](https://werewolf-and-witch.gitbook.io/whitepaper-english/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://werewolf-and-witch.gitbook.io/whitepaper-english/werewolf-and-witch.md).

# Werewolf and Witch

We started this service with the aim of creating a game where the economy and gameplay are centered around the utilization of a decentralized financial protocol called Blockchain. 

**We will provide functionality for players to tokenize in-game assets they deem valuable within the Werewolf and Witch of all game phases through the decentralized protocol, and issue and change assets according to a pre-specified protocol to ensure fairness and transparency.**

In order to create the most sustainable web3 service, we have identified and addressed the issues with Ponzi-like tokenomics structure. We recognized the limitations of maintaining the sustainability of the service and designed the game economy system based on the universal form of modern corporate capitalism, aiming to create a war game with a decentralized economic system that can be enjoyed for a long period of time.

<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://werewolf-and-witch.gitbook.io/whitepaper-english/werewolf-and-witch.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.