From 3998a8a6c41e6e47ff2438960022de9a9a09cbe9 Mon Sep 17 00:00:00 2001 From: zramsay Date: Mon, 2 Dec 2024 20:08:32 -0500 Subject: [PATCH] edit instructions --- testnet-onboarding-validator.md | 46 ++++++++++++--------------------- 1 file changed, 16 insertions(+), 30 deletions(-) diff --git a/testnet-onboarding-validator.md b/testnet-onboarding-validator.md index 3d1c65b..2e49471 100644 --- a/testnet-onboarding-validator.md +++ b/testnet-onboarding-validator.md @@ -291,15 +291,11 @@ laconic-so deployment --dir testnet-laconicd-deployment start ### Prerequisites -* SAPO testnet (testnet2) [genesis file](./ops/stage2/genesis.json) and peer node address (`f062dcfcbd5413c7446447812d0f22a67af93d18@laconicd-sapo.laconic.com:36656`) - -* A testnet stage1 node - - * For setting up a fresh testnet2 node, follow [Join as a validator](#join-as-a-validator-on-stage1) instead, but use testnet2 chain id (`laconic-testnet-2`) +* SAPO testnet (testnet2) [genesis file](./ops/stage2/genesis.json) and peers (see below) ### Setup -* Stop the stage1 node: +* If running, stop the stage1 node: ```bash # In dir where stage1 node deployment (`testnet-laconicd-deployment`) exists @@ -315,6 +311,8 @@ laconic-so deployment --dir testnet-laconicd-deployment start laconic-so fetch-stack git.vdb.to/cerc-io/testnet-laconicd-stack --pull ``` +* Ensure you are on tag v0.1.10 + * Clone / pull the required repositories: ```bash @@ -337,49 +335,37 @@ laconic-so deployment --dir testnet-laconicd-deployment start ### Create a deployment -* The existing stage1 deployment can be used for testnet2 +* Create a deployment from spec file: -* Copy over the published testnet2 genesis file (`.json`) to data directory in deployment (`testnet-laconicd-deployment/data/laconicd-data/tmp-testnet2`): +``` +laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd deploy create --spec-file testnet-laconicd-spec.yml --deployment-dir stage-2-testnet-laconicd-deployment +``` + +* Copy over the published testnet2 genesis file (`.json`) to data directory in deployment (`stage-2-testnet-laconicd-deployment/data/laconicd-data/tmp-testnet2`): ```bash # Example - mkdir -p $TESTNET_DEPLOYMENT/data/laconicd-data/tmp-testnet2 - cp genesis.json $TESTNET_DEPLOYMENT/data/laconicd-data/tmp-testnet2/genesis.json - ``` - -* Run script to reset node data and upgrade for testnet2: - - ```bash - cd ~/cerc/testnet-laconicd-stack - - docker run -it \ - -v $TESTNET_DEPLOYMENT/data/laconicd-data:/root/.laconicd \ - -v ./ops/stage2:/scripts \ - cerc/laconicd:local bash -c "/scripts/upgrade-node-to-testnet2.sh" - - cd - + mkdir -p stage-2-testnet-laconicd-deployment/data/laconicd-data/tmp-testnet2 + cp genesis.json stage-2-testnet-laconicd-deployment/data/laconicd-data/tmp-testnet2/genesis.json ``` ### Configuration -* Inside the `testnet-laconicd-deployment` deployment directory, open `config.env` file and set following env variables: +* Inside the `stage-2-testnet-laconicd-deployment` deployment directory, open `config.env` file and set following env variables: ```bash CERC_CHAIN_ID=laconic-testnet-2 - # Comma separated list of nodes to keep persistent connections to - # Example: "node-1-id@laconicd-sapo.laconic.com:36656" - # Use the provided node id - CERC_PEERS="f062dcfcbd5413c7446447812d0f22a67af93d18@laconicd-sapo.laconic.com:36656" + CERC_PEERS="bd56622c525a4dfce1e388a7b8c0cb072200797b@5.9.80.214:26103,289f10e94156f47c67bc26a8af747a58e8014f15@148.251.49.108:26656,72cd2f50dff154408cc2c7650a94c2141624b657@65.21.237.194:26656,21322e4fa90c485ff3cb9617438deec4acfa1f0b@143.198.37.25:26656" # A custom human readable name for this node - CERC_MONIKER= + CERC_MONIKER="my-node" ``` ### Start the deployment ```bash -laconic-so deployment --dir testnet-laconicd-deployment start +laconic-so deployment --dir stage-2-testnet-laconicd-deployment start ``` See [Check status](#check-status) to follow sync status of your node