> 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

<br>


---

# 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://qubetics.gitbook.io/qubetics-docs/solvers-dashboard-user-guide.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.
