From 8bf8206fbc15daef21a1d54cc24ad5647d50c85c Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Thu, 17 Jul 2025 15:34:28 +0300 Subject: [PATCH 1/5] Fix the CA rpc endpoint URLs Signed-off-by: Muhammet Kara --- docs/operators/setup/install-node.md | 4 ++-- versioned_docs/version-2.0.0/operators/setup/install-node.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/operators/setup/install-node.md b/docs/operators/setup/install-node.md index f8385f0b..1744c8d1 100644 --- a/docs/operators/setup/install-node.md +++ b/docs/operators/setup/install-node.md @@ -129,9 +129,9 @@ NODE_ADDR can be set to an IP of a trusted node, or to Casper Association's publ You can find active peers at https://cspr.live/tools/peers or use the following Casper Association public nodes: -* Testnet - NODE_ADDR=https://node.testnet.casper.network +* Testnet - NODE_ADDR=https://node.testnet.casper.network/rpc -* Mainnet - NODE_ADDR=https://node.mainnet.casper.network +* Mainnet - NODE_ADDR=https://node.mainnet.casper.network/rpc ### Protocol Version diff --git a/versioned_docs/version-2.0.0/operators/setup/install-node.md b/versioned_docs/version-2.0.0/operators/setup/install-node.md index 5e733758..2cf084c7 100644 --- a/versioned_docs/version-2.0.0/operators/setup/install-node.md +++ b/versioned_docs/version-2.0.0/operators/setup/install-node.md @@ -129,9 +129,9 @@ NODE_ADDR can be set to an IP of a trusted node, or to Casper Association public You can find active peers at https://cspr.live/tools/peers or use the following Casper Association's public nodes: -* Testnet - NODE_ADDR=https://node.testnet.casper.network +* Testnet - NODE_ADDR=https://node.testnet.casper.network/rpc -* Mainnet - NODE_ADDR=https://node.mainnet.casper.network +* Mainnet - NODE_ADDR=https://node.mainnet.casper.network/rpc ### Protocol Version From bdff07abb7300036a76acd9193015e56caff2469 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Thu, 17 Jul 2025 15:36:32 +0300 Subject: [PATCH 2/5] Add casper-sidecar to the node setup instructions Signed-off-by: Muhammet Kara --- docs/operators/setup/install-node.md | 2 +- versioned_docs/version-2.0.0/operators/setup/install-node.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/operators/setup/install-node.md b/docs/operators/setup/install-node.md index 1744c8d1..f81a2d2e 100644 --- a/docs/operators/setup/install-node.md +++ b/docs/operators/setup/install-node.md @@ -71,7 +71,7 @@ We are creating /etc/apt/keyrings if needed, so we don't have the issue with thi ## Required Tools ```bash -sudo apt install -y casper-client casper-node-launcher jq +sudo apt install -y casper-client casper-node-launcher casper-sidecar jq ``` ## Enable Bash Auto-Completion for `casper-client` (Optional) diff --git a/versioned_docs/version-2.0.0/operators/setup/install-node.md b/versioned_docs/version-2.0.0/operators/setup/install-node.md index 2cf084c7..a33fa365 100644 --- a/versioned_docs/version-2.0.0/operators/setup/install-node.md +++ b/versioned_docs/version-2.0.0/operators/setup/install-node.md @@ -71,7 +71,7 @@ We are creating /etc/apt/keyrings if needed, so we don't have the issue with thi ## Required Tools ```bash -sudo apt install -y casper-client casper-node-launcher jq +sudo apt install -y casper-client casper-node-launcher casper-sidecar jq ``` ## Enable Bash Auto-Completion for `casper-client` (Optional) From afc489e344d5c4930c6d20689d274ba6fd717ae7 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Thu, 17 Jul 2025 15:39:30 +0300 Subject: [PATCH 3/5] Bump the current node version to 2_0_0 Signed-off-by: Muhammet Kara --- docs/operators/setup/install-node.md | 8 ++++---- .../version-2.0.0/operators/setup/install-node.md | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/operators/setup/install-node.md b/docs/operators/setup/install-node.md index f81a2d2e..0b8ce96e 100644 --- a/docs/operators/setup/install-node.md +++ b/docs/operators/setup/install-node.md @@ -135,10 +135,10 @@ You can find active peers at https://cspr.live/tools/peers or use the following ### Protocol Version -Protocol version should be set to the largest available protocol version you see in `ls /etc/casper`. As of writing this, it was 1_5_8: +Protocol version should be set to the largest available protocol version you see in `ls /etc/casper`. As of writing this, it was 2_0_0: ```bash -PROTOCOL=1_5_8 +PROTOCOL=2_0_0 ``` ### Load `trusted_hash` in Config.toml of the Protocol Version @@ -146,8 +146,8 @@ PROTOCOL=1_5_8 The following command uses the previously established NODE_ADDR and PROTOCOL to load the `trusted_hash`: ```bash -NODE_ADDR=https://node.mainnet.casper.network -PROTOCOL=1_5_8 +NODE_ADDR=https://node.mainnet.casper.network/rpc +PROTOCOL=2_0_0 sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml ``` diff --git a/versioned_docs/version-2.0.0/operators/setup/install-node.md b/versioned_docs/version-2.0.0/operators/setup/install-node.md index a33fa365..28f95617 100644 --- a/versioned_docs/version-2.0.0/operators/setup/install-node.md +++ b/versioned_docs/version-2.0.0/operators/setup/install-node.md @@ -135,10 +135,10 @@ You can find active peers at https://cspr.live/tools/peers or use the following ### Protocol Version -Protocol version should be set to the largest available protocol version you see in `ls /etc/casper`. As of writing this, it was 1_5_8: +Protocol version should be set to the largest available protocol version you see in `ls /etc/casper`. As of writing this, it was 2_0_0: ```bash -PROTOCOL=1_5_8 +PROTOCOL=2_0_0 ``` ### Load `trusted_hash` in Config.toml of the Protocol Version @@ -146,8 +146,8 @@ PROTOCOL=1_5_8 The following command uses the previously established NODE_ADDR and PROTOCOL to load the `trusted_hash`: ```bash -NODE_ADDR=https://node.mainnet.casper.network -PROTOCOL=1_5_8 +NODE_ADDR=https://node.mainnet.casper.network/rpc +PROTOCOL=2_0_0 sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml ``` From 6d13edf01610228e30d83fa84180c728fb7c4196 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Thu, 17 Jul 2025 15:43:15 +0300 Subject: [PATCH 4/5] Fix the trusted_hash command to work with the new block structure Signed-off-by: Muhammet Kara --- docs/operators/setup/install-node.md | 2 +- versioned_docs/version-2.0.0/operators/setup/install-node.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/operators/setup/install-node.md b/docs/operators/setup/install-node.md index 0b8ce96e..aed1d038 100644 --- a/docs/operators/setup/install-node.md +++ b/docs/operators/setup/install-node.md @@ -148,7 +148,7 @@ The following command uses the previously established NODE_ADDR and PROTOCOL to ```bash NODE_ADDR=https://node.mainnet.casper.network/rpc PROTOCOL=2_0_0 -sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml +sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block_with_signatures.block.Version2.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml ``` ## Syncing to Genesis diff --git a/versioned_docs/version-2.0.0/operators/setup/install-node.md b/versioned_docs/version-2.0.0/operators/setup/install-node.md index 28f95617..448339e3 100644 --- a/versioned_docs/version-2.0.0/operators/setup/install-node.md +++ b/versioned_docs/version-2.0.0/operators/setup/install-node.md @@ -148,7 +148,7 @@ The following command uses the previously established NODE_ADDR and PROTOCOL to ```bash NODE_ADDR=https://node.mainnet.casper.network/rpc PROTOCOL=2_0_0 -sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml +sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block_with_signatures.block.Version2.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml ``` ## Syncing to Genesis From 9ab98d37a25fd7429b429b01cf9292c603b18f00 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Thu, 17 Jul 2025 15:52:00 +0300 Subject: [PATCH 5/5] Fix the sync_handling section to be compatible with the current version Signed-off-by: Muhammet Kara --- docs/operators/setup/install-node.md | 9 +++++---- .../version-2.0.0/operators/setup/install-node.md | 9 +++++---- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/operators/setup/install-node.md b/docs/operators/setup/install-node.md index aed1d038..28910246 100644 --- a/docs/operators/setup/install-node.md +++ b/docs/operators/setup/install-node.md @@ -153,14 +153,15 @@ sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node- ## Syncing to Genesis -In the latest protocol version's *Config.toml*, you will find the option `sync_to_genesis`. By default, this value will be set to `true`. +In the latest protocol version's *Config.toml*, you will find the option `sync_handling`. By default, this value will be set to `ttl`, which means the node will attempt to acquire all block data to comply with time to live enforcement, but will not attempt to sync all the way back to genesis. -If you are planning to run a validator node, it is better to not sync your node to genesis. This will increase node performance. In this case, the option should be changed to: +**If you are planning to run a validator node, leave this option at the default value of `ttl`**; this will increase node performance. + +If you are using the node for historical data and want to query back to genesis, then this option should be changed to: ```bash -sync_to_genesis = false +sync_handling = genesis ``` -If you are using the node for historical data and want to query back to genesis, you can leave the default value in place. ## Starting the Node diff --git a/versioned_docs/version-2.0.0/operators/setup/install-node.md b/versioned_docs/version-2.0.0/operators/setup/install-node.md index 448339e3..66fcc065 100644 --- a/versioned_docs/version-2.0.0/operators/setup/install-node.md +++ b/versioned_docs/version-2.0.0/operators/setup/install-node.md @@ -153,14 +153,15 @@ sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node- ## Syncing to Genesis -In the latest protocol version's *Config.toml*, you will find the option `sync_to_genesis`. By default, this value will be set to `true`. +In the latest protocol version's *Config.toml*, you will find the option `sync_handling`. By default, this value will be set to `ttl`, which means the node will attempt to acquire all block data to comply with time to live enforcement, but will not attempt to sync all the way back to genesis. -If you are planning to run a validator node, it is better to not sync your node to genesis. This will increase node performance. In this case, the option should be changed to: +**If you are planning to run a validator node, leave this option at the default value of `ttl`**; this will increase node performance. + +If you are using the node for historical data and want to query back to genesis, then this option should be changed to: ```bash -sync_to_genesis = false +sync_handling = genesis ``` -If you are using the node for historical data and want to query back to genesis, you can leave the default value in place. ## Starting the Node