§ Wiki · Wiki entryView source ·.md

Moving a Node Between Data Centers

The six-step sequence for relocating a node machine to a new data center while keeping operator allowances and reward configurations consistent.

·May 4, 2026·2 min read

Relocating a node between data centers touches three things at once: allowance on two operator records, the registry record for the node itself, and the reward configuration on both ends. The order matters — doing the registry and allowance steps in the wrong sequence leaves the operator record blocked from onboarding the node at its new home.

[!WARNING] Before starting, confirm that the destination data center supports the network's decentralization objectives. Movements that concentrate the network in a single jurisdiction will not be approved.

Procedure

Increase node allowance at the destination data center. The receiving operator record needs spare allowance to accept the incoming machine. Submit the NNS proposal that raises its allowance by one. Use Adding Additional Node Machines to an Existing Allowance for the validation evidence and proposal pattern.
Physically move the node machine. Ship or transport the server to the destination data center. Apply the same physical security controls there as at the origin site.
Remove the previous node record. Once the machine is offline, follow Removing a Node From the Registry to clear the old node ID. This frees the allowance slot on the origin operator record.
Re-onboard the node at the new data center. Follow the standard deployment flow: Gen-2 Node Deployment Guide or Gen-1. The node comes up with a fresh node ID under the destination operator record.
Reduce the previous operator's reward configuration by one. Submit a reward configuration change so the origin record stops being paid for the moved node. See the Reward Configuration Guide.
Increase the new operator's reward configuration by one. Submit the matching reward configuration change at the destination so the moved node is paid under its new home.

[!NOTE] Steps 5 and 6 should land in the same minting period to avoid double-paying or under-paying the move. Check the next minting date at next-rewards-gnj.caffeine.xyz before submitting.

Node Provider Maintenance Guide — the parent runbook.
Adding Additional Node Machines to an Existing Allowance — the allowance step.
Removing a Node From the Registry — the registry step.
Reward Configuration Guide — the reward steps on both ends.

Node Provider Maintenance Guide
Day-to-day responsibilities for keeping node machines healthy on the Internet Computer — monitoring, common maintenance tasks, scheduled outages, and peer support.
Adding Additional Node Machines to an Existing Allowance
How an existing node provider with unused allowance brings additional node machines onto the network without going through the full onboarding flow.
Removing a Node From the Registry
How to remove a node's record from the registry when its allowance is full and the underlying machine has been hardware-replaced or retired.
Reward Configuration Guide
How a node provider submits the reward configuration proposal that registers their nodes with the Network Nervous System and starts the reward stream.

For agents

The plain-markdown source is available at /wiki/moving-node-between-data-centers/source.md. Agents should read that rather than parse this page.

Procedure

Related