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

# Tournaments and Esports

Due to its skill-based, competitive nature, the Axie battle system is a good fit for competitive play and Esports. We believe this is a critical aspect for future growth and we have seen how engaged the players become when there is money on the line.&#x20;

Axie players have already earned thousands of dollars worth of cryptocurrency through numerous tournaments hosted by the core team or 3rd party sponsors.

LSL hosts tournaments to encourage players to compete with each other but at the same time, raise funds for the community-paying homage to the PlayToEarn ecosystem which has helped uplift the lives of many scholars.

![Lunacian Scholarship League](/files/-MlANX-ECZQhJ8o44uRJ)


---

# 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://blockchainspace.gitbook.io/blockchainspace/bspc-community/tournaments-and-esports.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.
