At the Permissionless IV hackathon?
Check the hackathon handbook!
LogoLogo
SupraScan ExplorerStarKey WalletDiscord
Node Operator
  • Network
  • Oracles
  • Automation
  • SupraNova
  • AI Agents
  • Overview
  • Node Operator FAQ
  • Node Upgrade Guide - Mainnet
    • Upgrade Checklist (Pre-Upgrade Verification)
    • Download the Node Management Scripts for Validator
    • Download the Node Management Scripts for RPC
    • Starting the Supra Nodes
    • Monitor Node Synchronization
    • CLI Improvements
    • Recovery Guide
  • Node Upgrade Guide - Testnet
    • Upgrade Checklist (Pre-Upgrade Verification)
    • Download the Node Management Scripts
    • Update the Supra Node Docker Image
    • Validator Migration to 9.x.x
    • RPC Migration to 9.x.x
    • Starting the Supra Node
    • Monitor Node Synchronization
    • CLI Improvements
    • Recovery Guide
  • Node Relocation Guide
    • Summary
    • Step 1
    • Step 2
    • Step 3
    • Step 4
    • Step 5
    • Step 6
    • Step 7
    • Step 8
  • Creating SupraDesk Tickets via Email
Powered by GitBook
On this page
Edit on GitHub

Node Relocation Guide

  1. You have an existing Supra Validator running in either Testnet or Mainnet. We will refer to the machine that is currently running this Validator as the “old instance”.

  2. You have provisioned the machine that you want to transfer your Validator to. We will refer to this machine as the “new instance”

PreviousRecovery GuideNextSummary

Links

  • Whitepapers
  • Bug Bounty
  • Security Audits

‎

  • Supra Dev Hub
  • Supra Labs Github
  • Entropy Foundation Github