> For the complete documentation index, see [llms.txt](https://docs.oceanpoint.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanpoint.fi/community/regional-hubs/quarterly-competitions.md).

# Quarterly competitions

At Blocksquare we are committed to fostering a dynamic and collaborative professional network. We value the efforts of all Regional Hub members in growing the network and organizing meet-ups and events. To further incentivize and promote the teamwork aspect we are introducing a gamification element to our network.

By working together, ambassadors will have the opportunity to compete for quarterly pools of BST tokens. These tokens serve as an additional incentive, on top of the existing referral agreement, rewarding their dedication and effort in growing the network and promoting the Blocksquare ecosystem.

The quarterly competitions will start as soon as at least three Regional Hubs have been formed globally. These competitions will involve scoring each Hub based on predefined metrics. At the end of the quarter, the scores will be tallied, and BST tokens distributed to all participating Hubs.

{% hint style="warning" %}
Quarterly competitions will commence once a minimum of three Regional Hubs are established worldwide.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oceanpoint.fi/community/regional-hubs/quarterly-competitions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.