> For the complete documentation index, see [llms.txt](https://mtt-network.gitbook.io/mtt-network-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mtt-network.gitbook.io/mtt-network-1/introduction/c.-validator-nodes/5-.-validator-governance-participation.md).

# 5). Validator Governance Participation

Validator nodes are not just maintainers of technology and consensus; they also play an important role in the governance process of MTT Network. Validators can participate in the following matters through governance voting:

* **Network Upgrades**: Validators can participate in deciding network protocol upgrades and improvements, including the addition of new features, performance optimizations, and security vulnerability patches.
* **Parameter Adjustments**: Some key network parameters (such as block rewards, transaction fee rates, etc.) may need periodic adjustments, and validators can vote to decide on these parameter changes.
* **Community Proposals**: Community members can submit proposals for new features or improvement suggestions. Validators can vote to decide whether to adopt these proposals.


---

# 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://mtt-network.gitbook.io/mtt-network-1/introduction/c.-validator-nodes/5-.-validator-governance-participation.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.