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 Confirm that Node B is fully synced and responsive.

1. 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

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.

1. 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.

1. 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.

1. Start Validator on Node B Launch the validator:

sudo systemctl restart qubeticschain.service

• Use the Qubetics explorer (e.g., [TICSScan uptime page]) to confirm that the validator is signing blocks again.

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

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.