> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund10-docs/voting/how-to-register-as-a-voter/wallet-registration-guide/check-voting-power-and-rewards-eligibility.md).
# Check Voting Power & Rewards Eligibility
In Fund10, users will need to wait until voting starts to view voting power in the Catalyst mobile application.
The Snapshot Module tool linked below allows users to connect a Catalyst registration in order to check voting power *before* voting begins, allowing users to validate and troubleshoot registration status before registration closes.
Users will also get feedback on whether their registration is eligible to recieve voter rewards in Fund10. Remember - registrations submitted before Fund10 will be eligible to vote but not recieve rewards. Be sure to update registration and verify using the Snapshot Module!
{% embed url="" %}
---
# 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.projectcatalyst.io/previous-funds/fund10-docs/voting/how-to-register-as-a-voter/wallet-registration-guide/check-voting-power-and-rewards-eligibility.md?ask=&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.
