Solana Testnet Restart - 29 April 2022

Important: Instruction is valid only during restart. Please use your common service file if network already started.

Testnet 1.10.11 Restart
(If you are running Solana v1.10.10 or earlier, please upgrade to current recommended version 1.10.11 https://github.com/solana-labs/solana/releases/tag/v1.10.11)

The restart will start from the highest finalized slot.

$ solana slot -ul --commitment finalized
130461975

Note: If your last finalized slot is lower than that the one listed below, this is likely your node crashed before it was able to observe the latest supermajority. Follow the instructions in the appendix

The known validator arguments provided below are validators who have the last finalized slot and are providing snapshots for it, don’t keep them in your list as known validators after the restart as these are community validators not Solana Foundation nodes.

Important: DO NOT delete your ledger directory

## Step 0: Stop the validator service

**IMPORTANT:** ⚠️MAKE SURE TO STOP YOUR VALIDATOR BEFORE DOING ANYTHING ELSE.⚠️

**IMPORTANT:** ⚠️DO NOT delete your ledger directory.⚠️

**NOTE:** *Upgrade to v1.10.11 if you are running older Solana version* 

## Step 1: 

Step 1: Create a snapshot at slot 130461975
This document assumes your ledger directory is called ledger/.  If not then adjust the following commands accordingly.

Use the ledger tool to create a new snapshot at slot 130461975, replacing the two instances of <ledger path> to your actual ledger path:

$ solana-ledger-tool --ledger <ledger path> create-snapshot 130461975 <ledger path> --hard-fork 130461975

Or else, if you use separate directory for snapshots:

$ solana-ledger-tool --ledger <ledger path> create-snapshot 130461975 <snapshots path> --hard-fork 130461975 --snapshot-archive-path <snapshots path>

Add --snapshot-archive-path before “create-snapshot” if you have a separate snapshot dir, and --accounts after “create-snapshot” if you have a separate accounts dir
 
The final line of output should be “Shred version: 33548”, and this snapshot file should now exist: 
ledger/snapshot-130461975-3ewJMR3wnyKcn6PrH3CY4knxexquEZ6ru6kYiHxB6Hqj.tar.zst

Check your ledger/ directory to ensure that you have no snapshot newer than ledger/snapshot-130461975-..... This is very unlikely, but if found should be removed. Snapshots older than ledger/snapshot-130461975-.. should not be removed.

NOTE: If you receive “Error: Slot 130461975 is not available”, please see appendix

Step 2: Adjust your validator command-line arguments, temporarily for this restart to include:

--wait-for-supermajority 130461975 \
--no-snapshot-fetch \
--no-genesis-fetch \
--expected-bank-hash EpPRJFjY11rds94kDoivi86sEW3sUiSLbSaSZdRqRsBz \
--expected-shred-version 33548 \
--entrypoint 5.9.35.85:8001 \
--entrypoint entrypoint.testnet.solana.com:8001 \
--entrypoint entrypoint2.testnet.solana.com:8001 \
--entrypoint entrypoint3.testnet.solana.com:8001 \
--known-validator eoKpUABi59aT4rR9HGS3LcMecfut9x7zJyodWWP43YQ \
--known-validator 82k4RGZAJxtXvW3hzgmHB2q4oDHzgwMR2cGXup324gsJ \
--known-validator Bszp6hDL19ymPZ8efp9venQYb4ae2rRmEtVp4aG6k8nx \
--known-validator 376e8QLx9qSkjFn7mK2kp3wBwvziKuMqiB3iAbK5Payx \
--known-validator 8Apz17FY7vts5PUEP28apzqQBVgg6McbetFJqb45ew8F \

(Remove the previous value of “--expected-shred-version“ if present)

Once the cluster restarts and normal operation resumes, remember to remove these arguments. They are only required for the restart. 

Step 3: Start your validator
As it boots, it will load the snapshot for slot 130461975 and wait for 80% of the stake to come online before producing/validating new blocks. 

To confirm your restarted validator is correctly waiting for 80% stake, look for this periodic log message to confirm it is waiting:
INFO  solana_core::validator] Waiting for 80% of activated stake at slot 130461975 to be in gossip...

And if you have RPC enabled, ask it repeated for the current slot:
$ solana --url http://127.0.0.1:8899 slot

Any number other than 130461975 means you did not complete the steps correctly.



Appendix: Resolution if you did not preserve your ledger or your last optimistically confirmed slot is below 130461975

NOT RECOMMENDED - this resolution should only be attempted if your ledger/ directory is unavailable. 

If your ledger history is corrupt or otherwise unavailable, delete your ledger/ directory instead of Steps 1 & 2, then complete Steps 3.

OBS: remove --no-snapshot-fetch  if set

Add these arguments to restart:


--wait-for-supermajority 130461975 \
--expected-shred-version 33548 \
--entrypoint 5.9.35.85:8001 \
--entrypoint entrypoint.testnet.solana.com:8001 \
--entrypoint entrypoint2.testnet.solana.com:8001 \
--entrypoint entrypoint3.testnet.solana.com:8001 \
--expected-bank-hash EpPRJFjY11rds94kDoivi86sEW3sUiSLbSaSZdRqRsBz \
--known-validator eoKpUABi59aT4rR9HGS3LcMecfut9x7zJyodWWP43YQ \
--known-validator 82k4RGZAJxtXvW3hzgmHB2q4oDHzgwMR2cGXup324gsJ \
--known-validator Bszp6hDL19ymPZ8efp9venQYb4ae2rRmEtVp4aG6k8nx \
--known-validator 376e8QLx9qSkjFn7mK2kp3wBwvziKuMqiB3iAbK5Payx \
--known-validator 8Apz17FY7vts5PUEP28apzqQBVgg6McbetFJqb45ew8F \