> For the complete documentation index, see [llms.txt](https://qubetics.gitbook.io/qubetics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qubetics.gitbook.io/qubetics-docs/solvers-dashboard-user-guide.md).
# Solvers Dashboard: User Guide
### Overview
The Qubetics Chain Abstraction Protocol runs a decentralized solver network. Solvers participate by operating Multi-Party Computation (MPC) nodes. These nodes process cross-chain transactions and help secure the protocol.
The Qubetics Solver Dashboard is a dedicated onboarding and management platform for solvers in the Qubetics Chain Abstraction protocol. A solver operator first runs a solver node, then uses the dashboard to register the solver by submitting the required node and identity details and adding the required liquidity. After onboarding, the dashboard acts as the solver’s control panel to manage and monitor liquidity positions and track solver rewards over time.
What you will do in this guide:
* Connect your wallet on the Qubetics Solver Dashboard
* Register your solver
* Add liquidity and verify your status
* Monitor and claim rewards
* Withdraw liquidity when needed
---
# 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://qubetics.gitbook.io/qubetics-docs/solvers-dashboard-user-guide.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.