Migrate an IntegrationNet Node to MainNet

Quick Start Guide to migrate a node from IntegrationNet to MainNet

Table of Contents

Sections
Prepare Node
Migrate Node
Optional Post Migration

---

✨Prepare Node

1

Validate VPS Specifications

Ensure your VPS meets the minimum specifications for a MainNet Hybrid node.

IntegrationNet nodes often already meet these specs, but this is a good time to confirm before migrating.

Node Specifications

2

SSH Into Your VPS

Connect to your node via SSH:

ssh -i /path/to/ssh/private/key nodeadmin@<vps_ip_address>

3

Document Your Current .p12 Details

Run the following command to retrieve current .p12 configuration details:

sudo nodectl view_config --section global_p12

🔐 Important:

If your passphrase is encrypted, it will not be visible. Ensure you have the passphrase securely stored before proceeding.

4

Check Auto Restart Status

sudo nodectl auto_restart status

• If you see SERVICE PROCESS FOUND (PID), continue to the next step.

• If disabled, skip to Update OS Packages step.

5

Disable Auto Restart

sudo nodectl configure -e -cb -d

• Choose r → Disable all three options:

  • auto_restart

  • auto_upgrade

  • on boot

• Choose q to exit.

6

Upgrade VPS - OS Packages

sudo nodectl upgrade_vps

If you encounter a purple TUI (text interface), use Tab to move between options and Enter to accept defaults.

7

Reboot VPS

Whether you are requested to reboot after the completion of the upgrade or not, it is a good idea to give your VPS a warm boot ( restart ) to obtain a fresh starting point.

sudo nodectl reboot

Answer y if asked to leave clusters. Wait one minute, then SSH back into the node.

8

Validate Latest nodectl Version

sudo nodectl check_versions

If you obtain a True you should skip the upgrade_nodectl step.

NODECTL VERSION MATCH: True

If you obtain a False you should upgrade nodectl.

9

Upgrade nodectl

sudo nodectl upgrade_nodectl

Upgrade nodectl Version

• If prompted to migrate your node configuration, select:

  • y to confirm migration

  • n if asked to upgrade nodectl again immediately after migration

10

Leave and Stop IntegrationNet Cluster

sudo nodectl stop -p intnet-l0 --leave
sudo nodectl stop -p intnet-l1 --leave

---

🦌Migrate Node

1

Enter Configurator

sudo nodectl configure -n -cb -d

2

Choose Scenario 3

• Press 3 to select Scenario 3

• Read the warning → press any key to continue

• If prompted to stop profiles → choose n

3

Select Predefined Configuration

Choose 1 for MainNet (Hypergraph)

4

Set Global .p12 Details

• Set all profiles to global: y

• Preserve global .p12 details: y

5

Clean Up Old Configuration

• Remove old profiles: y

• Remove old service files: y

🏗️ The nodectl utility will automatically build your new service files for you.

6

Review Config (Optional)

• You may choose to skip reviewing: n

Press q to return to the terminal.

7

Collateralize Your Node

Follow the official collateralization guide to complete the staking process. Once complete, return to this guide.

Collateralize Your Node

8

Starchiver

Optionally, you may utiltize the community owned and maintained Starchiver Utility.

sudo nodectl execute_starchiver -p dag-l0 --restart

9

Upgrade You Node

Perform a full upgrade to make sure everything if properly setup and configured.

For an interactive experience, ommit the --ni .

sudo nodectl upgrade --ni

---

🔘 Optional Post Migration Steps

Enable Auto RestartDelegated Staking