From c98958b86cd5d9c72746881f53df4798807f2bcd Mon Sep 17 00:00:00 2001 From: Conor Schaefer Date: Thu, 28 Mar 2024 14:18:56 -0700 Subject: [PATCH] docs: fixes another typo in upgrade docs Refs #4087, #4131. --- docs/guide/src/pd/chain-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/src/pd/chain-upgrade.md b/docs/guide/src/pd/chain-upgrade.md index 71fbe07436..94d6c21eff 100644 --- a/docs/guide/src/pd/chain-upgrade.md +++ b/docs/guide/src/pd/chain-upgrade.md @@ -66,7 +66,7 @@ and provide that value in the documentation. Or should we just pick a genesis st You must use that precise genesis time, otherwise your node will not be able to reach consensus with the rest of the network. 6. Move the migrated state into place: `mkdir ~/.penumbra/testnet_data/node0/pd && mv ~/.penumbra/testnet_data/node0/pd-exported-state/rocksdb ~/.penumbra/testnet_data/node0/pd/` 7. Move the upgrade cometbft state into place: `cp ~/.penumbra/testnet_data/node0/pd-exported-state/genesis.json ~/.penumbra/testnet_data/node0/cometbft/config/genesis.json - && cp ~/.penumbra/testnet_data/pd-exported-state/priv_validator_state.json ~/.penumbra/testnet_data/node0/cometbft/data/priv_validator_state.json` + && cp ~/.penumbra/testnet_data/node0/pd-exported-state/priv_validator_state.json ~/.penumbra/testnet_data/node0/cometbft/data/priv_validator_state.json` 8. Then we clean up the old CometBFT state: `find ~/.penumbra/testnet_data/node0/cometbft/data/ -mindepth 1 -maxdepth 1 -type d -exec rm -r {} +` Finally, restart the node, e.g. `sudo systemctl restart penumbra cometbft`. Check the logs, and you should see the chain progressing