> 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/solver-node-setup-guide/for-ubuntu.md).

# For Ubuntu

**1.) Open Terminal**

**2.) Download the binary:** Get the binary from the official Qubetics repository:

You can view the release details here: [v0.0.1 Release](https://github.com/Qubetics/solver-network-binary/releases/tag/v0.0.1)

Use `wget` to download the binary 

```
wget https://github.com/Qubetics/solver-network-binary/releases/download/v0.0.1/mpc-node
```

```
chmod +x mpc-node
```

<mark style="color:$warning;">**Note: Ensure you run the chmod command to make the binary executable**</mark>

**3) Generate Solver(Peer) ID:** Each solver node needs a unique Solver(peer) ID to identify itself on the network. Generate one using:

```
./mpc-node --generate
```

Save the generated solver (peer) ID - you'll need it for the onboarding step.

<mark style="color:$warning;">**Note: The node will run on the default RPC port. If you want to change the RPC port, create a .env file and add the port there like this:**</mark>

```
export RPC_PORT="your_port"
```

**4.) Onboard & Add Liquidity as a Solver**

Once your Solver(Peer) ID is generated, it needs to be **onboarded** (registered) on the network. Use the onboarding portal to register:

👉 Solver Onboarding Platform: [**Onboarding Portal**](https://ticssolver.com/)

After onboarding, fund your node with the minimum required liquidity:

Minimum Liquidity for Node Solver

| Asset    | Minimum Required |
| -------- | ---------------- |
| **TICS** | 90000 TICS       |
| **BTC**  | 0.005 BTC        |

> *These amounts are examples and subject to change. Refer to the latest network parameters for confirmed values.*

{% hint style="info" %} <mark style="color:$danger;">Both balances must be met before the node connects. If the minimum requirements are not met, the node will be</mark> <mark style="color:$danger;"></mark><mark style="color:$danger;">**banned from the network for 1 hour**</mark><mark style="color:$danger;">.</mark>
{% endhint %}

**5.) Connect to solver network:**

After running the node, enter the following command to connect with the solver network and other interconnected nodes.

```
./mpc-node
```

<figure><img src="/files/DV6fq6sIZk0D0WwuBKcf" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If everything is funded and onboarded correctly, your node will join the network and start participating in DKG rounds, threshold signing, and intent resolution.
{% endhint %}

{% hint style="info" %} <mark style="color:$warning;">**If you want to run the node in the background:**</mark> [Follow This Guide](/qubetics-docs/solver-node-setup-guide/run-mpc-node-in-the-background.md)
{% endhint %}

**6.) Verify connection and node address**

The terminal will provide a unique node address in the Peer ID field.&#x20;

<figure><img src="/files/L8qLMm2CRWpFiKEW1PpM" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
***Note:*** Node address will be utilised to onboard as a solver in the Qubetics solvers onboarding platform.
{% endhint %}


---

# 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/solver-node-setup-guide/for-ubuntu.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.