docs: update dkg injection guide

Author: jannikluhn

dkg_injection/dappnode-keypers-dkg-injection-guide.md

@@ -1,55 +1,64 @@
-# Dappnode Keypers: How to use DKG injection script
+# How to use the DKG injection script to restore the time capsule key shares into an existing DAppNode instance
 
-This guide describes the process for how **Dappnode** keypers can use the DKG injection script in the **shutter-api-1002** deployment.
+This guide describes the process to inject the Ethereum Time Capsule Key shares generated under the initial deployment of the Shutter API Keyper set and backed up under [the initial DAppNode deployment](https://github.com/shutter-network/DAppnodePackage-shutter-api/releases/tag/chiado%400.1.0_gnosis%400.1.5) ([DAppNode Explorer link](https://dappnode.github.io/explorer/#/repo/0x8928c414c10d5eeaf2eea30702b3a0c03d52ff6f/0.1.5))
 
-## Purpose
+This is needed to generate the time capsule decryption keys when the decryption timestamp is reached.
 
-To restore key material generated during previous deployment, necessary to fulfill pending decryption tasks.
-
----
-
-**Initial Keypers**: Keypers who were active during **eon 11**. Timestamp range: Mar-24-2025 01:03:45 PM UTC (1742821425) - Dec-01-2025 11:25:35 AM UTC (1764588335).
-
----
+Initial Keypers refer to the Keypers who were active during eon 11 of the initial API Keyper deployment. Timestamp range: Mar-24-2025 01:03:45 PM UTC (1742821425) - Dec-01-2025 11:25:35 AM UTC (1764588335).
 
 ## Prerequisites
 
-- Fully synced keyper running the shutter-api-1002 deployment version on Dappnode
-- The same signing keys used for initial keyper deployment
-- Dappnode backup from the initial keyper
-- Access to Dappnode instance via shell
-
----
+- Fully synced Keyper running the latest Shutter API 1002 DAppNode deployment version. [Release](https://github.com/shutter-network/DAppnodePackage-shutter-api/compare/chiado@v0.1.0_gnosis@v0.1.9...chiado@v0.1.0_gnosis@v0.1.10) | [DAppNode Explorer link](https://dappnode.github.io/explorer/#/repo/0x8928c414c10d5eeaf2eea30702b3a0c03d52ff6f/0.1.10)
+- The same Ethereum signing key used during the time capsule key collection.
+- DAppNode backup of the initial Keyper keys requested in November 2025.
+- Access to the DAppNode instance via shell.
 
 ## Process Steps
 
-### 1. Run Keypers with Same Signing Keys
+### 1. Start a Keyper instance with the correct Ethereum key
 
-In the **shutter-api-1002** deployment, run the keypers with the **same signing keys** that were used previously for the initial keypers deployment and wait for them to sync with the network.
+All Keypers have already been requested to start a new instance with the Ethereum signing key they used during the time capsule key generation.
 
-Sync can be confirmed by this log line:
+This step has already been performed, and all Keypers are running the latest Shutter API 1002 DAppNode deployment with the Ethereum signing key used during the time capsule collection.
+
+### 2. Check that your Keyper Gnosis chain is sufficiently synced
+
+The syncing status can be confirmed if you see the below logs:
 
 ```
-synced registry contract end-block=20044460 num-discarded-events=0 num-inserted-events=0 start-block=20044460
+synced registry contract end-block=46640633 num-discarded-events=0 num-inserted-events=0 start-block=46640633
 ```
 
-The **end-block** should be (or greater than) the current head of the chain in the explorer.
+The **end-block** should be greater than block 44980000, which corresponds to Mar 4, 2026.
+
+Note: Some Keypers have been running into rate-limiting issues and are not able to sync fully. This is currently not an issue as long as they are synced past the required activation block number, which they already are.
 
-### 2. Ensure the backup is copied to the same instance
+## 3. SSH into DAppNode
 
-Copy the backup to the same instance where the keyper is running.
+SSH into the DAppNode machine as described in the DAppNode docs:
 
-### 3. Run DKG Injection Script (Dappnode)
+`ssh dappnode@<DAPPNODE_LOCAL_IP_ADDRESS>`
 
-After a keyperset transition is done, run the Dappnode DKG injection script with the backup path:
+from the same network. Use the password set during onboarding.
 
-```bash
+Source:
+https://docs.dappnode.io/docs/user/access-your-dappnode/terminal/
+
+### 4. Ensure the backup is copied to your DAppNode machine
+
+Copy the November Time Capsule DAppNode backup to your DAppNode machine, under a designated folder `<path_to_dappnode_backup>.`
+
+### 5. Run the DAppNode DKG injection script
+
+Run the DAppNode DKG injection script and provide the correct time capsule backup path:
+
+```shell
 curl -fsSL https://raw.githubusercontent.com/shutter-network/DAppnodePackage-shutter-api/dkg-injection/dkg_injection/inject_dkg_result_dappnode.sh | bash -s -- <path_to_dappnode_backup>
 ```
 
-Replace `<path_to_dappnode_backup>` with the actual path to your Dappnode backup archive.
+Replace `<path_to_dappnode_backup>` with the actual path to your DAppNode time capsule backup archive.
 
-Check if there is no error in running the script. The output should look something like this:
+Check that there is no error when running the script. The output should look something like this:
 
 ```
 ==> Checking shuttermint sync block number >= 349800
@@ -61,20 +70,14 @@ Check if there is no error in running the script. The output should look somethi
 ==> Checking if backup tables already exist
 ==> Backing up tables
 ==> Injecting DKG result
+==> Verifying injected data
 ==> Done
 ==> Stopping backup container
 ==> Restarting keyper service (was running before)
 ==> Keeping db service running (was running before)
 ==> Removing temporary directory /tmp/tmp.7l26Tilq40
 ```
 
----
-
-## Summary Checklist
-
-| Step | Action |
-|------|--------|
-| 1 | Run keypers in shutter-api-1002 with same signing keys as initial keypers and wait for keypers to sync |
-| 2 | Ensure the Dappnode backup archive is copied to the same instance |
-| 3 | Run the Dappnode DKG injection script with the backup archive path |
+### 6. Report the result of the script
 
+Please report the result of the script to the Shutter team under your individual Keyper group.