> For the complete documentation index, see [llms.txt](https://reactors.gitbook.io/reactor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reactors.gitbook.io/reactor/reactor-intro/basic-overview.md).
# Basic Overview
**Reactor drives positive-sum interactions to maximise rewards for ecosystem participants; liquidity providers (LPs), protocols and veRCT voters.**
Every epoch (1 week), veRCT holders vote to decide which pools will receive RCT emissions. The amount of emissions received by each pool is proportional to the amount of votes the pool receives.
* This generates RCT rewards for LPs, which builds liquidity for protocol and core ecosystem pools.
To vote with veRCT, you must lock RCT up to a maximum of 2 years. Voters are rewarded (proportional to locked amount) with trading fees and voting incentives generated by the pool/s they vote for.
* Protocols deposit voting incentives to gain votes to their pools and to attract LPs to build liquidity through RCT emissions, and ultimately enables traders to swap their tokens.
This ensures that RCT emissions are constantly being utilised to build liquidity for pools that generate the most rewards for veRCT voters of time.
---
# 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://reactors.gitbook.io/reactor/reactor-intro/basic-overview.md?ask=&goal=
```
`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.