> For the complete documentation index, see [llms.txt](https://docs.vires.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vires.finance/faq/w-governance.md).
# ⓥ Governance
*The two critical ingredients to successful tokenomics are protocol governance and harvesting the results of the decisions made by the voters.*
### Why lock VIRES?
*VIRES locking reflects your commitment to the protocol governance*. Therefore, it grants you the ability to make decisions and **directly earn your share of the protocol’s income**. This share exists in the form of *gVires*.
### What is gVires?
**gVires**(g is for ‘governance’) is a unit of measure of your commitment to the protocol’s future. The more Vires you lock, the more you are committed; therefore, the more voting power and the larger share of the protocol’s revenue stream you receive.
### Deprecation of Vires Staking
Vires staking is not a commitment: users can always unstake and sell their tokens, leaving the community behind the decisions made. Therefore, simply staking doesn’t provide any part of the revenue stream of the protocol.
---
# 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://docs.vires.finance/faq/w-governance.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.