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

# Abstract

Hotbet is a groundbreaking synthetic DeFi project that introduces a twist to the ordinary betting ecosystem.

Most betting “casinos” based on or funded by a ERC-20 token fail to garner enough betting volume to be considered legitimate or profitable to holders (by way of revenue share).

Instead of requiring that users gamble extra money, the Hotbet concept recognizes that investors are already “gamblers” by definition, when they purchased the token itself. The Hotbet concept rewards investors appropriately, whilst giving them an opportunity to bet in a fun and engaging manner that requires no spending, and most importantly, isn’t hampered by jurisdictional laws. Betting can take place from and is permitted anywhere in the world.

This whitepaper provides an overview of Hotbet Token's innovative features, which include an intricate backend system, a connected database, reward mechanisms for user engagement, and the provision of race passes for betting activities.


---

# 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:

```
GET https://hotbetgg.gitbook.io/whitepaper/abstract.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
