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

# I. Abstract

GateGameFi - The first gaming platform built on the Runes Protocol & Ethereum Virtual Machine (EVM), designed to bring the exciting Web3 gaming world directly to the #Bitcoin community.

GateGamefi is revolutionizing gaming through the Rune Protocol. Currently, GateGameFi has integrated over 50 Web3 games along with a fair and unique reward system, seamlessly connecting them within the Bitcoin ecosystem. We will provide comprehensive support for community, ensuring:

1. Targeted customer acquisition. 
2. Comprehensive airdrop campaign analysis.
3. Fair distribution tied to significant milestones. Ready to enhance gamers' gaming experience.


---

# 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://gategamefi.gitbook.io/gate-gamefi-white-paper/i.-abstract.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.