> 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/getting-started/mainnet-node-setup/validator-migration.md).

# Validator Migration

## Safe Migration: Moving Your Validator to a New Server (Qubetics Chain)

1. Prepare the New Server (Node B)\
   Set up Node B and fully sync it to the latest block height using:

[https://github.com/Qubetics/qubetics-mainnetnode-script  <br>](https://github.com/Qubetics/qubetics-mainnetnode-script)      \
Confirm that Node B is fully synced and responsive.<br>

2. Stop the Old Validator (Node A)\
   On Node A, run:

```
sudo systemctl stop qubeticschain.service 
```

* Confirm the validator process has completely stopped.
* sudo systemctl status qubeticschain.service

{% hint style="info" %}
**Note: If, while shifting the validator, Node A is still running and we copy the same priv\_validator\_key.json file to Node B and start it, both nodes will attempt to propose blocks at the same time. This results in double-signing, and the validator will be tombstoned. Once tombstoned, the validator cannot recover — the only option is to unstake the remaining amount and create a new validator. The penalty for being tombstoned is a 5% slash. The tombstoned validator itself is dead forever.**\
**It's crucial to stop Node A before proceeding.**
{% endhint %}

3. Transfer Validator Key\
   Locate and display the key on Node A

```
sudo cat /data/.tmp-qubeticsd/config/priv_validator_key.json
```

Copy the file securely from Node A.<br>

4. Deploy the Key on Node B

Replace it into the same path on Node B:

```
sudo nano /data/.tmp-qubeticsd/config/priv_validator_key.json
```

* Save your changes.<br>

5. Start Validator on Node B\
   Launch the validator:

```
sudo systemctl restart qubeticschain.service
```

* Use the Qubetics explorer (e.g., \[[TICSScan](https://native.ticsscan.com/qubetics/uptime) uptime page]) to confirm that the validator is signing blocks again.<br>

6. Decommission Old Node\
   Once Node B is live and stable, safely shut down or repurpose Node A.

{% hint style="info" %}
**Warning: When a validator gets tombstoned (because of double-signing):**

* You cannot un-jail the validator ever again—it’s permanently banned.
* The validator is slashed (5% by default for double-signing).
* The remaining stake/delegations are not locked forever—you (and your delegators) can still unbond (or unstake) the remaining tokens after the 14-day unbonding period.
* To continue validating, you must create a new validator with a fresh key.<br>
  {% endhint %}

\
\ <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/getting-started/mainnet-node-setup/validator-migration.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.