Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add validator migration guide and networks list table #1854

Merged
merged 3 commits into from
Jan 27, 2025
+72 −0
Merged

docs: add validator migration guide and networks list table #1854

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ef502eb
docs: add validator migration guide and networks list table
redwest88 Jan 9, 2025
236da43
use constants for chain IDs and relative links
redwest88 Jan 11, 2025
12c5ba9
Apply suggestions from code review
jcstein Jan 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Apply suggestions from code review 
Co-authored-by: Rootul P <rootulp@gmail.com>
@jcstein @rootulp
jcstein and rootulp authored Jan 27, 2025
commit 12c5ba9ca141b2bd5ef04d55fbe703fba3951b40
4 changes: 2 additions & 2 deletions how-to-guides/validator-node.md
View file
Original file line number Diff line number Diff line change
@@ -254,7 +254,7 @@ Moving a validator to a new machine is a sensitive process that needs to be done

### Step 1: Set up a new full consensus node

First, set up a new [full consensus node](./consensus-node.md) on the new server and make sure the node is fully synced with the chain. To check whether your node is synced, you can check the `catching_up` status using:
First, set up a new [consensus node](./consensus-node.md) on the new server and make sure the node is fully synced with the chain. To check whether your node is synced, you can check the `catching_up` status using:

```bash
celestia-appd status | jq '{ "catching_up": .SyncInfo.catching_up }'
@@ -270,7 +270,7 @@ If the node is synced, the output will look like this:

### Step 2: Stop the old validator

After your new full consensus node is synced, proceed to stop the current validator on the old machine. If you’re running it with [SystemD](./systemd.md), use the following command:
After your new consensus node is synced, proceed to stop the current validator on the old machine. If you’re running it with [SystemD](./systemd.md), use the following command:

```bash
sudo systemctl stop <SERVICE_NAME>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add explanation for the SERVICE_NAME placeholder

The <SERVICE_NAME> placeholder needs clarification for users:

-sudo systemctl stop <SERVICE_NAME>
+sudo systemctl stop celestia-appd.service  # Replace with your actual service name if different
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
sudo systemctl stop <SERVICE_NAME>
sudo systemctl stop celestia-appd.service # Replace with your actual service name if different