From abc16cfc6669f5d8bc80f5ce46df602ca0edfc78 Mon Sep 17 00:00:00 2001 From: richard Date: Mon, 21 Jul 2025 15:40:41 +0800 Subject: [PATCH 1/5] feat: add migration guide for legacy Reth-Lighthouse to EthPillar --- docs/Announcement/pectra-upgrade.md | 67 +++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+) diff --git a/docs/Announcement/pectra-upgrade.md b/docs/Announcement/pectra-upgrade.md index 0aed135..35430b4 100644 --- a/docs/Announcement/pectra-upgrade.md +++ b/docs/Announcement/pectra-upgrade.md @@ -248,6 +248,73 @@ journalctl -u execution --since today | grep 'Prague' Jul 16 08:06:22 dev reth[3417514]: - Prague @1755669600 ``` +### For Legacy Reth-Lighthouse Node migrate to EthPillar + +below is the process for migrating an existing validator from a legacy Reth-Lighthouse setup to the EthPillar way. Follow these steps carefully to ensure a smooth and safe transition. + + +#### 1. Safely Shut Down Your Legacy Node + +The first step is to locate your validator keys and securely stop your old node. This prevents any risk of double-signing, which can lead to slashing penalties. + +First, find the absolute path to your `validator_keys` directory. You will need this exact path later to import your keys into EthPillar. + +```bash +# Replace /path/to/your/setup with the actual location of your node files. +find /path/to/your/setup/mainnet-reth-lighthouse/validator_keys +``` + +Once you have recorded the `validator_keys` path, navigate to your node's directory and execute the shutdown script. + +```bash +cd mainnet-reth-lighthouse +./down.sh +``` + +> **CRITICAL:** To prevent double-signing penalties (slashing), it is crucial to wait for at least **two full epochs (approximately 13 minutes)** after shutting down your old node before your new validator comes online. This waiting period ensures your old validator is fully offline from the network's perspective. + +--- + +#### 2. Set Up Your New EthPillar Node + +Next, install and configure your new node using the EthPillar. + +Follow the official EthPillar documentation to **[Setup Validator for Endurance](https://openfusionist.github.io/staking-docs/getting-started/ethpillar/)**. This instructional **[video guide](https://www.youtube.com/watch?v=YLuZPUW9Q9Q)** can also be a helpful reference. + +> **IMPORTANT:** Since you are migrating existing validator keys, you can **skip** the step titled `Generate Validator Key & Send Deposit`. You will be importing your keys directly in the next step, not creating new ones. + +--- + +#### 3. Import Your Validator Keys into EthPillar + +With your EthPillar node running, you can now import your existing validator keys. + +1. In the EthPillar Terminal, navigate to the **Validator** section. +2. Choose the option: **Generate/Import Validator Keys**. +3. Click on **Import Validator Keys from Offline key generation or Backup**. +4. In the input field, provide the `validator_keys` path that you recorded in Step 1. +5. Click **Import**. +6. You will be prompted to enter the password for decrypting the keystore files. Enter your validator key password and continue to the next step. + +> **NOTE:** You will **not** need to upload a `deposit-data.json` file, as your validator is already active on the Beacon Chain. You can safely omit or skip this part of the import process. + +--- + +#### 4. Verify the Import and Monitor Your Validator + +After importing the keys, it's essential to check the logs to confirm that your validator client has successfully recognized and loaded them. + +Check the logs of your new validator client. You are looking for a log entry that confirms the number of validators being managed. + +For example, if your logs show `validators=1` (or whatever number of validators you imported), the import was successful. + +```bash +# Example log from a Nimbus validator client managed by EthPillar +Jul 21 09:16:24 dev nimbus_validator_client[200349]: INF 2025-07-21 09:16:24.000+02:00 Slot start slot=3629182 epoch=113411 attestationIn= blockIn= validators=1 node_status=synced delay=1ms682us998ns +``` + +If the `validators=` value matches the number of keys you imported, your migration is complete. Your validator is now successfully running on EthPillar. + ## 3. Technical Support If you have any questions about upgrade, feel free to ask: - [Discord](https://discord.com/channels/926691694680870982/1212701304787566592) \ No newline at end of file From e98f1aa8d5040b0f212c5cab4a822d043ed52e9c Mon Sep 17 00:00:00 2001 From: richard Date: Mon, 21 Jul 2025 15:58:13 +0800 Subject: [PATCH 2/5] refactor: streamline migration instructions for legacy Reth-Lighthouse to EthPillar --- docs/Announcement/pectra-upgrade.md | 65 +---------------- .../legacy-way/mirgate-to-ethpillar.md | 70 +++++++++++++++++++ 2 files changed, 71 insertions(+), 64 deletions(-) create mode 100644 docs/getting-started/legacy-way/mirgate-to-ethpillar.md diff --git a/docs/Announcement/pectra-upgrade.md b/docs/Announcement/pectra-upgrade.md index 35430b4..a9845d9 100644 --- a/docs/Announcement/pectra-upgrade.md +++ b/docs/Announcement/pectra-upgrade.md @@ -250,70 +250,7 @@ Jul 16 08:06:22 dev reth[3417514]: - Prague @175566960 ### For Legacy Reth-Lighthouse Node migrate to EthPillar -below is the process for migrating an existing validator from a legacy Reth-Lighthouse setup to the EthPillar way. Follow these steps carefully to ensure a smooth and safe transition. - - -#### 1. Safely Shut Down Your Legacy Node - -The first step is to locate your validator keys and securely stop your old node. This prevents any risk of double-signing, which can lead to slashing penalties. - -First, find the absolute path to your `validator_keys` directory. You will need this exact path later to import your keys into EthPillar. - -```bash -# Replace /path/to/your/setup with the actual location of your node files. -find /path/to/your/setup/mainnet-reth-lighthouse/validator_keys -``` - -Once you have recorded the `validator_keys` path, navigate to your node's directory and execute the shutdown script. - -```bash -cd mainnet-reth-lighthouse -./down.sh -``` - -> **CRITICAL:** To prevent double-signing penalties (slashing), it is crucial to wait for at least **two full epochs (approximately 13 minutes)** after shutting down your old node before your new validator comes online. This waiting period ensures your old validator is fully offline from the network's perspective. - ---- - -#### 2. Set Up Your New EthPillar Node - -Next, install and configure your new node using the EthPillar. - -Follow the official EthPillar documentation to **[Setup Validator for Endurance](https://openfusionist.github.io/staking-docs/getting-started/ethpillar/)**. This instructional **[video guide](https://www.youtube.com/watch?v=YLuZPUW9Q9Q)** can also be a helpful reference. - -> **IMPORTANT:** Since you are migrating existing validator keys, you can **skip** the step titled `Generate Validator Key & Send Deposit`. You will be importing your keys directly in the next step, not creating new ones. - ---- - -#### 3. Import Your Validator Keys into EthPillar - -With your EthPillar node running, you can now import your existing validator keys. - -1. In the EthPillar Terminal, navigate to the **Validator** section. -2. Choose the option: **Generate/Import Validator Keys**. -3. Click on **Import Validator Keys from Offline key generation or Backup**. -4. In the input field, provide the `validator_keys` path that you recorded in Step 1. -5. Click **Import**. -6. You will be prompted to enter the password for decrypting the keystore files. Enter your validator key password and continue to the next step. - -> **NOTE:** You will **not** need to upload a `deposit-data.json` file, as your validator is already active on the Beacon Chain. You can safely omit or skip this part of the import process. - ---- - -#### 4. Verify the Import and Monitor Your Validator - -After importing the keys, it's essential to check the logs to confirm that your validator client has successfully recognized and loaded them. - -Check the logs of your new validator client. You are looking for a log entry that confirms the number of validators being managed. - -For example, if your logs show `validators=1` (or whatever number of validators you imported), the import was successful. - -```bash -# Example log from a Nimbus validator client managed by EthPillar -Jul 21 09:16:24 dev nimbus_validator_client[200349]: INF 2025-07-21 09:16:24.000+02:00 Slot start slot=3629182 epoch=113411 attestationIn= blockIn= validators=1 node_status=synced delay=1ms682us998ns -``` - -If the `validators=` value matches the number of keys you imported, your migration is complete. Your validator is now successfully running on EthPillar. +Please refer to [Migration Guide](../getting-started/legacy-way/mirgate-to-ethpillar) ## 3. Technical Support If you have any questions about upgrade, feel free to ask: diff --git a/docs/getting-started/legacy-way/mirgate-to-ethpillar.md b/docs/getting-started/legacy-way/mirgate-to-ethpillar.md new file mode 100644 index 0000000..934cd9e --- /dev/null +++ b/docs/getting-started/legacy-way/mirgate-to-ethpillar.md @@ -0,0 +1,70 @@ +--- +sidebar_position: 0 +--- + +### For Legacy Reth-Lighthouse Node migrate to EthPillar + +below is the process for migrating an existing validator from a legacy Reth-Lighthouse setup to the EthPillar way. Follow these steps carefully to ensure a smooth and safe transition. + + +#### 1. Safely Shut Down Your Legacy Node + +The first step is to locate your validator keys and securely stop your old node. This prevents any risk of double-signing, which can lead to slashing penalties. + +First, find the absolute path to your `validator_keys` directory. You will need this exact path later to import your keys into EthPillar. + +```bash +# Replace /path/to/your/setup with the actual location of your node files. +find /path/to/your/setup/mainnet-reth-lighthouse/validator_keys +``` + +Once you have recorded the `validator_keys` path, navigate to your node's directory and execute the shutdown script. + +```bash +cd mainnet-reth-lighthouse +./down.sh +``` + +> **CRITICAL:** To prevent double-signing penalties (slashing), it is crucial to wait for at least **two full epochs (approximately 13 minutes)** after shutting down your old node before your new validator comes online. This waiting period ensures your old validator is fully offline from the network's perspective. + +--- + +#### 2. Set Up Your New EthPillar Node + +Next, install and configure your new node using the EthPillar. + +Follow the official EthPillar documentation to **[Setup Validator for Endurance](https://openfusionist.github.io/staking-docs/getting-started/ethpillar/)**. This instructional **[video guide](https://www.youtube.com/watch?v=YLuZPUW9Q9Q)** can also be a helpful reference. + +> **IMPORTANT:** Since you are migrating existing validator keys, you can **skip** the step titled `Generate Validator Key & Send Deposit`. You will be importing your keys directly in the next step, not creating new ones. + +--- + +#### 3. Import Your Validator Keys into EthPillar + +With your EthPillar node running, you can now import your existing validator keys. + +1. In the EthPillar Terminal, navigate to the **Validator** section. +2. Choose the option: **Generate/Import Validator Keys**. +3. Click on **Import Validator Keys from Offline key generation or Backup**. +4. In the input field, provide the `validator_keys` path that you recorded in Step 1. +5. Click **Import**. +6. You will be prompted to enter the password for decrypting the keystore files. Enter your validator key password and continue to the next step. + +> **NOTE:** You will **not** need to upload a `deposit-data.json` file, as your validator is already active on the Beacon Chain. You can safely omit or skip this part of the import process. + +--- + +#### 4. Verify the Import and Monitor Your Validator + +After importing the keys, it's essential to check the logs to confirm that your validator client has successfully recognized and loaded them. + +Check the logs of your new validator client. You are looking for a log entry that confirms the number of validators being managed. + +For example, if your logs show `validators=1` (or whatever number of validators you imported), the import was successful. + +```bash +# Example log from a Nimbus validator client managed by EthPillar +Jul 21 09:16:24 dev nimbus_validator_client[200349]: INF 2025-07-21 09:16:24.000+02:00 Slot start slot=3629182 epoch=113411 attestationIn= blockIn= validators=1 node_status=synced delay=1ms682us998ns +``` + +If the `validators=` value matches the number of keys you imported, your migration is complete. Your validator is now successfully running on EthPillar. From ea69628afd54a232170f8f1fccf0db35c4eb3a1f Mon Sep 17 00:00:00 2001 From: richard Date: Mon, 21 Jul 2025 16:00:15 +0800 Subject: [PATCH 3/5] fix --- docs/Announcement/pectra-upgrade.md | 2 +- .../{mirgate-to-ethpillar.md => Migrate-to-ethpillar.md} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename docs/getting-started/legacy-way/{mirgate-to-ethpillar.md => Migrate-to-ethpillar.md} (100%) diff --git a/docs/Announcement/pectra-upgrade.md b/docs/Announcement/pectra-upgrade.md index a9845d9..6f75866 100644 --- a/docs/Announcement/pectra-upgrade.md +++ b/docs/Announcement/pectra-upgrade.md @@ -250,7 +250,7 @@ Jul 16 08:06:22 dev reth[3417514]: - Prague @175566960 ### For Legacy Reth-Lighthouse Node migrate to EthPillar -Please refer to [Migration Guide](../getting-started/legacy-way/mirgate-to-ethpillar) +Please refer to [Migration Guide](../getting-started/legacy-way/Migrate-to-ethpillar) ## 3. Technical Support If you have any questions about upgrade, feel free to ask: diff --git a/docs/getting-started/legacy-way/mirgate-to-ethpillar.md b/docs/getting-started/legacy-way/Migrate-to-ethpillar.md similarity index 100% rename from docs/getting-started/legacy-way/mirgate-to-ethpillar.md rename to docs/getting-started/legacy-way/Migrate-to-ethpillar.md From 365c527cbb888a8784a37e3bedad955f43772ac4 Mon Sep 17 00:00:00 2001 From: richard Date: Tue, 22 Jul 2025 14:39:20 +0800 Subject: [PATCH 4/5] add Legacy Reth-Lighthouse Node --- docs/Announcement/pectra-upgrade.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/Announcement/pectra-upgrade.md b/docs/Announcement/pectra-upgrade.md index 6f75866..e157f6b 100644 --- a/docs/Announcement/pectra-upgrade.md +++ b/docs/Announcement/pectra-upgrade.md @@ -248,9 +248,15 @@ journalctl -u execution --since today | grep 'Prague' Jul 16 08:06:22 dev reth[3417514]: - Prague @1755669600 ``` -### For Legacy Reth-Lighthouse Node migrate to EthPillar +### For Legacy Reth-Lighthouse Node + +We recommend migrating to EthPillar. See the [Migration Guide](../getting-started/legacy-way/Migrate-to-ethpillar). + +If you prefer to keep the legacy workflow, you can still upgrade your node to the Pectra Hardfork by following the [Legacy Upgrade Guide](https://github.com/OpenFusionist/mainnet-reth-lighthouse#upgrade-for-pectra-hardfork). + +> **IMPORTANT:** The legacy scripts only support the Pectra Hardfork and will not be maintained for future upgrades. + -Please refer to [Migration Guide](../getting-started/legacy-way/Migrate-to-ethpillar) ## 3. Technical Support If you have any questions about upgrade, feel free to ask: From be71531cb40d7fcf1d20850d4b87c1cf43e26848 Mon Sep 17 00:00:00 2001 From: richard Date: Tue, 22 Jul 2025 15:34:04 +0800 Subject: [PATCH 5/5] update --- .../legacy-way/Migrate-to-ethpillar.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/getting-started/legacy-way/Migrate-to-ethpillar.md b/docs/getting-started/legacy-way/Migrate-to-ethpillar.md index 934cd9e..07b03c9 100644 --- a/docs/getting-started/legacy-way/Migrate-to-ethpillar.md +++ b/docs/getting-started/legacy-way/Migrate-to-ethpillar.md @@ -25,7 +25,7 @@ cd mainnet-reth-lighthouse ./down.sh ``` -> **CRITICAL:** To prevent double-signing penalties (slashing), it is crucial to wait for at least **two full epochs (approximately 13 minutes)** after shutting down your old node before your new validator comes online. This waiting period ensures your old validator is fully offline from the network's perspective. +> **CRITICAL:** To prevent double-signing penalties (slashing), it is crucial to wait for at least **two full epochs (approximately 13 minutes)** after shutting down your old node before your new validator comes online. This waiting period ensures your old validator is fully offline from the network's perspective. Also do not manually restart the old reth-lighthouse node. For safety's sake, completely delete the old directory after the migration is completed. --- @@ -68,3 +68,13 @@ Jul 21 09:16:24 dev nimbus_validator_client[200349]: INF 2025-07-21 09:16:24.000 ``` If the `validators=` value matches the number of keys you imported, your migration is complete. Your validator is now successfully running on EthPillar. + + +#### 5. Clean up your old node + +After successfully running EthPillar, you can delete the old node file directory to avoid accidentally restarting the old node, which could lead to slashing. + +```bash +rm -rf mainnet-reth-lighthouse +``` +