You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/concepts/glossary/A.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ An Account is a structure that represents a user on a Casper network. Informatio
12
12
13
13
## Account Hash {#account-hash}
14
14
15
-
The account hash is a 32-byte hash of the public key representing the user account. Information on generating an account hash can be found [here](https://support.casperlabs.io/hc/en-gb/articles/13781616975131-How-do-I-generate-an-account-hash-).
15
+
The account hash is a 32-byte hash of the public key representing the user account. This can be generated with the casper-client-rs tool.
Copy file name to clipboardexpand all lines: docs/developers/cli/transfers/multisig-deploy-transfer.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -247,12 +247,12 @@ Towards the end of the following output, you can observe that there is an **appr
247
247
248
248
### Sending the deploy {#sending-the-transaction}
249
249
250
-
The next step is to send the deploy for processing on the network. As described in the [Prerequisites](#prerequisites) section, you need to get an active node address from the corresponding network to complete this task. The following example uses the node `https://rpc.testnet.casperlabs.io/` from the Testnet.
250
+
The next step is to send the deploy for processing on the network. As described in the [Prerequisites](#prerequisites) section, you need to get an active node address from the corresponding network to complete this task. The following example uses the node `https://node.testnet.casper.network` from the Testnet.
Copy file name to clipboardexpand all lines: docs/operators/becoming-a-validator/bonding.md
+13-3
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,16 @@ It is recommended that a bonding request be sent once the node has completed the
8
8
9
9
In the Testnet, era durations are approximately two hours. The entire process takes approximately 3 eras. Therefore, **the time for bid submission to inclusion in the validator set is a minimum of six hours**. Bonding requests (bids) are transactions like any other. Because they are generic transactions, they are more resistant to censorship.
10
10
11
+
## Minimum Bid Amount
12
+
13
+
There is a minimum defined bid amount in the `chainspec.toml`. This value is currently 100,000 CSPR as seen as the extract from `chainspec.toml` below.
14
+
15
+
```toml
16
+
# Minimum bid amount allowed in motes. Withdrawing one's bid to an amount strictly less than
17
+
# the value specified will be treated as a full unbond of a validator and their associated delegators
18
+
minimum_bid_amount = 100_000_000_000_000
19
+
```
20
+
11
21
## Method 1: Bonding with the System Auction Contract {#bonding-system-auction}
12
22
13
23
This method submits a bid using the system auction contract. Call the existing `add_bid` entry point from the system auction contract. Using this method, you do not need to build any contracts, reducing costs and complexity.
1.`node-address` - An IP address of a peer on the network. The default port of nodes' JSON-RPC servers on Mainnet and Testnet is 7777
87
87
2.`secret-key` - The file name containing the secret key of the account paying for the Deploy
88
88
3.`chain-name` - The chain-name to the network where you wish to send the Deploy. For Mainnet, use *casper*. For Testnet, use *casper-test*
89
-
4.`payment-amount` - The payment for the Deploy in motes. You must check the network's chainspec. For example, this entry point call needs 10,000 motes for node version [1.5.1](https://github.com/casper-network/casper-node/blob/release-1.5.1/resources/production/chainspec.toml)
89
+
4.`payment-amount` - The payment for the Deploy in motes. You must check the network's chainspec. For example, this entry point call needs 2,500,000,000 motes for node version [1.5.1](https://github.com/casper-network/casper-node/blob/release-1.5.1/resources/production/chainspec.toml)
90
90
5.`session-hash` - Hex-encoded hash of the stored auction contract, which depends on the network you are using. For Casper's Mainnet and Testnet, the hashes are:
Copy file name to clipboardexpand all lines: docs/operators/maintenance/archiving-and-restoring.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ This documentation describes processes for the compression and decompression of
10
10
11
11
:::note
12
12
13
-
The values presented in this document assume that the `trie-compact` tool was run on a Mainnet database for compression. Contact the [support team](https://support.casperlabs.io/hc/en-gb) if you have questions.
13
+
The values presented in this document assume that the `trie-compact` tool was run on a Mainnet database for compression.
Copy file name to clipboardexpand all lines: docs/operators/setup-network/create-private.md
-1
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,6 @@ Use the below guides to set up and manage validator nodes.
42
42
-[Set up Mainnet and Testnet validator nodes](https://docs.cspr.community/): A set of guides for Mainnet and Testnet node-operators on setting up and configuring their Casper network validator nodes.
43
43
44
44
Use these FAQ collections for tips and details for validators.
45
-
-[FAQs for a basic validator node ](https://support.casperlabs.io/hc/en-gb/sections/6960448246683-Node-Operation-FAQ)
46
45
-[External FAQs on Mainnet and Testnet validator node setup](https://docs.cspr.community/docs/faq-validator.html)
Copy file name to clipboardexpand all lines: docs/operators/setup/basic-node-configuration.md
+8-14
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ A node is usually run by executing the `casper-node-launcher`, which executes th
12
12
13
13
The `casper-node-launcher` can be installed via a Debian package, which also creates the `casper` user and directory structures and sets up a `systemd` unit and logging.
14
14
15
-
The `casper-node-launcher` Debian package can be obtained from https://repo.casperlabs.io. You only need to run the steps detailed there once.
15
+
The `casper-node-launcher` Debian package can be obtained from https://repo.casper.network. You only need to run the steps detailed there once.
16
16
17
17
Then, proceed to install the `casper-node-launcher` by running these commands:
18
18
@@ -50,9 +50,6 @@ The default location for executables from the Debian package install is `/usr/bi
50
50
51
51
This is the default location for configuration files. It can be overwritten with the `CASPER_CONFIG_DIR` environment variable. The paths in this document assume the default configuration file location of `/etc/casper`. The data is organized as follows:
52
52
53
-
-`delete_local_db.sh` - Removes `*.lmdb*` files from `/var/lib/casper/casper-node`
54
-
-`pull_casper_node_version.sh` - Pulls `bin.tar.gz` and `config.tar.gz` from [genesis.casperlabs.io](https://genesis.casperlabs.io/) for a specified protocol version and extracts them into `/var/lib/bin/<protocol_version>` and `/etc/casper/<protocol_version>`
55
-
-`config_from_example.sh` - Gets external IP to replace and create the `config.toml` from `config-example.toml`
56
53
-`node_util.py` - A script that will be replacing other scripts and is the preferred method of performing the actions of `pull_casper_node_version.sh`, `config_from_example.sh`, and `delete_local_db.sh`. Other scripts will be deprecated in future releases of `casper-node-launcher`.
57
54
-`casper-node-launcher-state.toml` - The local state for the `casper-node-launcher` which is created during the first run
58
55
-`validator_keys/` - The default folder for node keys, containing:
For `<NETWORK_CONFIG>`, we use `casper.conf` for Mainnet and `casper-test.conf` for Testnet. This will install all currently released protocols in one step.
100
97
101
-
This command will do the following:
102
-
- Create `/var/lib/casper/bin/1_0_2/` and expand the `bin.tar.gz` containing at a minimum `casper-node`
103
-
- Create `/etc/casper/1_0_2/` and expand the `config.tar.gz` containing `chainspec.toml`, `config-example.toml`, and possibly `accounts.csv` and other files
104
-
- Remove the archive files and run `/etc/casper/config_from_example.sh 1_0_2` to create a `config.toml` from the `config-example.toml`
98
+
This command will do the following for each protocol not installed with `1_5_8` as example here:
99
+
- Create `/var/lib/casper/bin/1_5_8/` and expand the `bin.tar.gz` containing at a minimum `casper-node`
100
+
- Create `/etc/casper/1_5_8/` and expand the `config.tar.gz` containing `chainspec.toml`, `config-example.toml`, and possibly `accounts.csv` and other files
101
+
- Remove the archive files
102
+
- Run the equivalent of `/etc/casper/node_util.py config_from_example 1_5_8` to create a `config.toml` from the `config-example.toml`
105
103
106
104
Release versions are invoked using the underscore format, such as:
This page has an example of using [sed to automatically update the trusted hash](https://docs.casper.network/operators/setup/install-node#getting-a-trusted-hash)
Copy file name to clipboardexpand all lines: docs/operators/setup/install-node.md
+17-15
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ Of these `35000` is the only port required to be open for your node to function,
20
20
## Operating System Requirements
21
21
The recommended OS version is Ubuntu 20.04.
22
22
23
-
### Using Ubuntu 22.04
23
+
### Using Ubuntu 22.04 or 24.04
24
24
25
-
Installing using Ubuntu 22.04 follows the same instructions as 20.04 with one exception:
25
+
Installing using Ubuntu 22.04 or 24.04 follows the same instructions as 20.04 with one exception:
26
26
27
27
If you try to install packages, you will receive:
28
28
@@ -33,8 +33,8 @@ casper-client : Depends: libssl1.1 (>= 1.1.0) but it is not installable
33
33
This message is due to the default `openssl` moving to 3.* with Ubuntu 22.04. You need to install OpenSSL 1.* for prior versions of Ubuntu to use the Casper binaries with the following command:
@@ -46,25 +46,27 @@ Before beginning, [update the maximum open files limit](./open-files.md) for you
46
46
If you were running a previous node on this box, this will clean up state. If packages are not installed, the `apt remove` may give errors, but this is not a problem.
echo"deb [arch=amd64 signed-by=/etc/apt/keyrings/casper-repo-pubkey.gpg] https://repo.casper.network/releases focal main"| sudo tee -a /etc/apt/sources.list.d/casper.list
66
67
sudo apt update
67
68
```
69
+
We are creating /etc/apt/keyrings if needed, so we don't have the issue with this key being trusted by all APT requests if stored in /etc/apt/trusted.gpg.d.
68
70
69
71
## Required Tools
70
72
@@ -127,25 +129,25 @@ NODE_ADDR can be set to an IP of a trusted node, or to Casper Labs' public nodes
127
129
128
130
You can find active peers at https://cspr.live/tools/peers or use the following Casper Labs public nodes:
Copy file name to clipboardexpand all lines: docs/operators/setup/node-endpoints.md
+3-18
Original file line number
Diff line number
Diff line change
@@ -189,31 +189,16 @@ If this port is closed, the requests coming to this port will not be served, but
189
189
190
190
## Setting up Firewall Rules
191
191
192
-
To limit inbound traffic to the node’s endpoints, you can set firewall rules similar to the `ufw` commands below:
192
+
To limit inbound traffic to the node’s endpoints, you can set firewall rules.
193
193
194
-
```bash
195
-
sudo apt install ufw -y
196
-
sudo ufw disable
197
-
sudo ufw reset
198
-
sudo ufw default allow outgoing
199
-
sudo ufw default deny incoming
200
-
sudo ufw limit ssh
201
-
sudo ufw limit 7777/tcp
202
-
sudo ufw limit 8888/tcp
203
-
sudo ufw limit 35000/tcp
204
-
sudo ufw enable
205
-
```
206
-
207
-
These commands will limit requests to the available ports of your node. Port 35000 should be left open, although you can limit traffic, as it is crucial for node-to-node communication.
208
-
209
-
If you have any concerns, questions, or issues, please [submit a request](https://support.casperlabs.io/hc/en-gb/requests/new) to the Casper support team.
194
+
Two example files are available: [firewall.sh](https://genesis.casper.network/firewall.sh) and more restrictive [firewall_only_node_to_node.sh](https://genesis.casper.network/firewall_only_node_to_node.sh).
210
195
196
+
Both of these include `8888` access from casper-network-monitor IP for tracking status of the network. More information is included in the comments of the files.
211
197
212
198
## Restricting Access for Private Networks
213
199
214
200
Any node can join Mainnet and Testnet and communicate with the nodes in the network. Private networks may wish to restrict access for new nodes joining the network as described [here](../setup-network/create-private.md#network-access-control).
215
201
216
-
217
202
## Summary of Related Links
218
203
219
204
Here is a summary of the links mentioned on this page:
@@ -217,7 +217,7 @@ The table below summarizes the updates.
217
217
To add an associated key to the primary account, use the `add_account.wasm` provided. This example adds two keys to the primary account (`account-hash-d89c*`): `user_1` with `account-hash-e2d0*`, and `user_2` with `account-hash-04a9*`.
@@ -421,7 +421,7 @@ Before removing a key, ensure the remaining associated keys can combine their we
421
421
Given the current setup, the primary account will add an associated key, and then remove it. In other use cases, associated keys may need to combine their signatures to send a multi-sig deploy that removes a key.
@@ -496,7 +496,7 @@ The table below summarizes the updates after calling the `add_account.wasm`.
496
496
The `remove_account.wasm` will remove the newly added account to demonstrate the possibility of removing associated keys that may have been compromised.
Copy file name to clipboardexpand all lines: docs/resources/advanced/storage-workflow.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Both the [`put_key`](https://docs.rs/casper-contract/latest/casper_contract/cont
18
18
19
19
### `storage::write` / `storage::read`
20
20
21
-
[`storage::write`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.write.html) writes a given value to a previously established URef (created using [`storage::new_uref`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.new_uref.html)). Unlike `put_key`, this value is not one of the `Key` types listed above, but rather any of the potential [`CLType`](https://docs.casperlabs.io/developers/json-rpc/types_cl/#cltype)s as outlined. [`storage::read`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.read.html) provides a method to retrieve these values from the associated URef.
21
+
[`storage::write`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.write.html) writes a given value to a previously established URef (created using [`storage::new_uref`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.new_uref.html)). Unlike `put_key`, this value is not one of the `Key` types listed above, but rather any of the potential [`CLType`](https://docs.casper.network/developers/json-rpc/types_cl)s as outlined. [`storage::read`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.read.html) provides a method to retrieve these values from the associated URef.
Copy file name to clipboardexpand all lines: versioned_docs/version-1.5.X/developers/cli/transfers/multisig-deploy-transfer.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -246,12 +246,12 @@ Towards the end of the following output, you can observe that there is an **appr
246
246
247
247
### Sending the deploy {#sending-the-deploy}
248
248
249
-
The next step is to send the deploy for processing on the network. As described in the [Prerequisites](#prerequisites) section, you need to get an active node address from the corresponding network to complete this task. The following example uses the node `https://rpc.testnet.casperlabs.io/` from the Testnet.
249
+
The next step is to send the deploy for processing on the network. As described in the [Prerequisites](#prerequisites) section, you need to get an active node address from the corresponding network to complete this task. The following example uses the node `https://node.testnet.casper.network` from the Testnet.
Copy file name to clipboardexpand all lines: versioned_docs/version-1.5.X/operators/setup-network/staging-files-for-new-network.md
+7-16
Original file line number
Diff line number
Diff line change
@@ -43,32 +43,23 @@ This is a description of Mainnet protocol version hosting (with network name: `c
43
43
44
44
At the root of the hosting server directory for a given network, a `protocol_versions` file exists. This holds the valid protocol versions for a network.
45
45
46
-
We can look at this manually on Mainnet using *curl*. As of writing this, `1.4.6` is the latest version and the contents of this file will change.
46
+
We can look at this manually on Mainnet using *curl*. As of writing this, `1_5_8` is the latest version and the contents of this file will change.
We should find `bin.tar.gz` and `config.tar.gz` in those directories under `casper`.
67
56
57
+
Since 1.5 `casper-node` version, the network syncs with `fast-sync` protocol where historical nodes are not needed. The only time multiple protocols are needed is during and upgrade staging period. However, it is typical that `protocol_versions` is updated only when a new version is staged, so usually the current and previous version are help in `protocol_versions`.
58
+
68
59
## Protocol Version
69
60
70
-
The protocol version of a network is not related to the `casper-node` version. In Mainnet, these have often been the same. However, with a new network, you would use the latest `casper-node` version for your
71
-
`1.0.0` protocol.
61
+
The protocol version of a network is not related to the `casper-node` version. In Mainnet, these have often been the same.
62
+
However, with a new network, you would use the latest `casper-node` version for your `1.0.0` protocol.
Copy file name to clipboardexpand all lines: versioned_docs/version-1.5.X/operators/setup/basic-node-configuration.md
+2-5
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ A node is usually run by executing the `casper-node-launcher`, which executes th
12
12
13
13
The `casper-node-launcher` can be installed via a Debian package, which also creates the `casper` user and directory structures and sets up a `systemd` unit and logging.
14
14
15
-
The `casper-node-launcher` Debian package can be obtained from [https://repo.casperlabs.io](https://repo.casperlabs.io). You only need to run the steps detailed there once.
15
+
The `casper-node-launcher` Debian package can be obtained from [https://repo.casper.network](https://repo.casper.network). You only need to run the steps detailed there once.
16
16
17
17
Then, proceed to install the `casper-node-launcher` by running these commands:
18
18
@@ -50,9 +50,6 @@ The default location for executables from the Debian package install is `/usr/bi
50
50
51
51
This is the default location for configuration files. It can be overwritten with the `CASPER_CONFIG_DIR` environment variable. The paths in this document assume the default configuration file location of `/etc/casper`. The data is organized as follows:
52
52
53
-
-`delete_local_db.sh` - Removes `*.lmdb*` files from `/var/lib/casper/casper-node`
54
-
-`pull_casper_node_version.sh` - Pulls `bin.tar.gz` and `config.tar.gz` from [genesis.casperlabs.io](https://genesis.casperlabs.io/) for a specified protocol version and extracts them into `/var/lib/bin/<protocol_version>` and `/etc/casper/<protocol_version>`
55
-
-`config_from_example.sh` - Gets external IP to replace and create the `config.toml` from `config-example.toml`
56
53
-`node_util.py` - A script that will be replacing other scripts and is the preferred method of performing the actions of `pull_casper_node_version.sh`, `config_from_example.sh`, and `delete_local_db.sh`. Other scripts will be deprecated in future releases of `casper-node-launcher`.
57
54
-`casper-node-launcher-state.toml` - The local state for the `casper-node-launcher` which is created during the first run
58
55
-`validator_keys/` - The default folder for node keys, containing:
@@ -129,7 +126,7 @@ When joining the network, the system will start from the hash of a recent block
129
126
Here is an example command for obtaining a trusted hash. Replace the node address with an updated address from a node on the network.
echo"deb [arch=amd64 signed-by=/etc/apt/keyrings/casper-repo-pubkey.gpg] https://repo.casper.network/releases focal main"| sudo tee -a /etc/apt/sources.list.d/casper.list
66
66
sudo apt update
67
67
```
68
68
@@ -127,7 +127,7 @@ NODE_ADDR can be set to an IP of a trusted node, or to Casper Labs' public nodes
127
127
128
128
You can find active peers at https://cspr.live/tools/peers or use the following Casper Labs public nodes:
@@ -217,7 +217,7 @@ The table below summarizes the updates.
217
217
To add an associated key to the primary account, use the `add_account.wasm` provided. This example adds two keys to the primary account (`account-hash-d89c*`): `user_1` with `account-hash-e2d0*`, and `user_2` with `account-hash-04a9*`.
@@ -421,7 +421,7 @@ Before removing a key, ensure the remaining associated keys can combine their we
421
421
Given the current setup, the primary account will add an associated key, and then remove it. In other use cases, associated keys may need to combine their signatures to send a multi-sig deploy that removes a key.
@@ -496,7 +496,7 @@ The table below summarizes the updates after calling the `add_account.wasm`.
496
496
The `remove_account.wasm` will remove the newly added account to demonstrate the possibility of removing associated keys that may have been compromised.
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/concepts/glossary/A.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ An Account is a structure that represents a user on a Casper network. Informatio
12
12
13
13
## Account Hash {#account-hash}
14
14
15
-
The account hash is a 32-byte hash of the public key representing the user account. Information on generating an account hash can be found [here](https://support.casperlabs.io/hc/en-gb/articles/13781616975131-How-do-I-generate-an-account-hash-).
15
+
The account hash is a 32-byte hash of the public key representing the user account. This can be generated with the casper-client-rs tool.
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/developers/cli/transfers/multisig-deploy-transfer.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -247,12 +247,12 @@ Towards the end of the following output, you can observe that there is an **appr
247
247
248
248
### Sending the deploy {#sending-the-transaction}
249
249
250
-
The next step is to send the deploy for processing on the network. As described in the [Prerequisites](#prerequisites) section, you need to get an active node address from the corresponding network to complete this task. The following example uses the node `https://rpc.testnet.casperlabs.io/` from the Testnet.
250
+
The next step is to send the deploy for processing on the network. As described in the [Prerequisites](#prerequisites) section, you need to get an active node address from the corresponding network to complete this task. The following example uses the node `https://node.testnet.casper.network` from the Testnet.
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/operators/maintenance/archiving-and-restoring.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ This documentation describes processes for the compression and decompression of
10
10
11
11
:::note
12
12
13
-
The values presented in this document assume that the `trie-compact` tool was run on a Mainnet database for compression. Contact the [support team](https://support.casperlabs.io/hc/en-gb) if you have questions.
13
+
The values presented in this document assume that the `trie-compact` tool was run on a Mainnet database for compression.
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/operators/setup-network/create-private.md
-1
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,6 @@ Use the below guides to set up and manage validator nodes.
42
42
-[Set up Mainnet and Testnet validator nodes](https://docs.cspr.community/): A set of guides for Mainnet and Testnet node-operators on setting up and configuring their Casper network validator nodes.
43
43
44
44
Use these FAQ collections for tips and details for validators.
45
-
-[FAQs for a basic validator node ](https://support.casperlabs.io/hc/en-gb/sections/6960448246683-Node-Operation-FAQ)
46
45
-[External FAQs on Mainnet and Testnet validator node setup](https://docs.cspr.community/docs/faq-validator.html)
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/operators/setup/basic-node-configuration.md
+13-61
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ A node is usually run by executing the `casper-node-launcher`, which executes th
12
12
13
13
The `casper-node-launcher` can be installed via a Debian package, which also creates the `casper` user and directory structures and sets up a `systemd` unit and logging.
14
14
15
-
The `casper-node-launcher` Debian package can be obtained from https://repo.casperlabs.io. You only need to run the steps detailed there once.
15
+
The `casper-node-launcher` Debian package can be obtained from https://repo.casper.network. You only need to run the steps detailed there once.
16
16
17
17
Then, proceed to install the `casper-node-launcher` by running these commands:
18
18
@@ -50,9 +50,6 @@ The default location for executables from the Debian package install is `/usr/bi
50
50
51
51
This is the default location for configuration files. It can be overwritten with the `CASPER_CONFIG_DIR` environment variable. The paths in this document assume the default configuration file location of `/etc/casper`. The data is organized as follows:
52
52
53
-
-`delete_local_db.sh` - Removes `*.lmdb*` files from `/var/lib/casper/casper-node`
54
-
-`pull_casper_node_version.sh` - Pulls `bin.tar.gz` and `config.tar.gz` from [genesis.casperlabs.io](https://genesis.casperlabs.io/) for a specified protocol version and extracts them into `/var/lib/bin/<protocol_version>` and `/etc/casper/<protocol_version>`
55
-
-`config_from_example.sh` - Gets external IP to replace and create the `config.toml` from `config-example.toml`
56
53
-`node_util.py` - A script that will be replacing other scripts and is the preferred method of performing the actions of `pull_casper_node_version.sh`, `config_from_example.sh`, and `delete_local_db.sh`. Other scripts will be deprecated in future releases of `casper-node-launcher`.
57
54
-`casper-node-launcher-state.toml` - The local state for the `casper-node-launcher` which is created during the first run
58
55
-`validator_keys/` - The default folder for node keys, containing:
For `<NETWORK_CONFIG>`, we use `casper.conf` for Mainnet and `casper-test.conf` for Testnet. This will install all currently released protocols in one step.
100
97
101
-
This command will do the following:
102
-
- Create `/var/lib/casper/bin/1_0_2/` and expand the `bin.tar.gz` containing at a minimum `casper-node`
103
-
- Create `/etc/casper/1_0_2/` and expand the `config.tar.gz` containing `chainspec.toml`, `config-example.toml`, and possibly `accounts.csv` and other files
104
-
- Remove the archive files and run `/etc/casper/config_from_example.sh 1_0_2` to create a `config.toml` from the `config-example.toml`
98
+
This command will do the following for each protocol not installed with `1_5_8` as example here:
99
+
- Create `/var/lib/casper/bin/1_5_8/` and expand the `bin.tar.gz` containing at a minimum `casper-node`
100
+
- Create `/etc/casper/1_5_8/` and expand the `config.tar.gz` containing `chainspec.toml`, `config-example.toml`, and possibly `accounts.csv` and other files
101
+
- Remove the archive files
102
+
- Run the equivalent of `/etc/casper/node_util.py config_from_example 1_5_8` to create a `config.toml` from the `config-example.toml`
105
103
106
104
Release versions are invoked using the underscore format, such as:
This page has an example of using [sed to automatically update the trusted hash](https://docs.casper.network/operators/setup/install-node#getting-a-trusted-hash)
134
128
135
129
### Known Addresses {#known-addresses}
136
130
@@ -156,58 +150,16 @@ Provide the path to the secret keys for the node. This path is set to `etc/caspe
156
150
157
151
### Networking and Gossiping {#networking--gossiping}
158
152
159
-
The node requires a publicly accessible IP address. The `config_from_example.sh` and `node_util.py` both allow IP for network address translation (NAT) setup. Specify the public IP address of the node. If you use the `config_from_example.sh` external services are called to find your IP and this is inserted into the `config.toml` created.
153
+
The node requires a publicly accessible IP address. `node_util.py` allows IP for network address translation (NAT) setup.
154
+
Specify the public IP address of the node with the `/etc/casper/node_util.py stage_protocols [config file] --ip 'my.ip.goes.here'`.
155
+
This will use the IP given rather than query for the external IP automatically.
156
+
160
157
161
158
The following default values are specified in the file if you want to change them:
162
159
163
160
- The port that will be used for status and transactions
164
161
- The port used for networking
165
-
- Known_addresses - these are the bootstrap nodes (there is no need to change these)
166
-
167
-
### Enabling Speculative Execution
168
-
169
-
The `speculative_exec` endpoint provides a method to execute a transaction without committing its execution effects to global state. This can be used by developers to roughly estimate the gas costs of sending the transaction in question. By default, `speculative_exec` is disabled on a node.
170
-
171
-
`speculative_exec` can be enabled within *config.toml* by changing `enable_server` to `true` under the configuration options for the speculative execution JSON-RPC HTTP server.
172
-
173
-
Node operators may also change the incoming request port for speculative execution, which defaults to `7778`. Further, you can choose to alter the `qps_limit` and `max_body_bytes`, which limit the amount and size of requests to the speculative execution server.
174
-
175
-
#### Example Config.toml configuration with speculative execution enabled
# Flag which enables the speculative execution JSON-RPC HTTP server.
184
-
enable_server = true
185
-
186
-
# Listening address for speculative execution JSON-RPC HTTP server. If the port
187
-
# is set to 0, a random port will be used.
188
-
#
189
-
# If the specified port cannot be bound to, a random port will be tried instead.
190
-
# If binding fails, the speculative execution JSON-RPC HTTP server will not run,
191
-
# but the node will be otherwise unaffected.
192
-
#
193
-
# The actual bound address will be reported via a log line if logging is enabled.
194
-
address = '0.0.0.0:7778'
195
-
196
-
# The global max rate of requests (per second) before they are limited.
197
-
# Request will be delayed to the next 1 second bucket once limited.
198
-
qps_limit = 1
199
-
200
-
# Maximum number of bytes to accept in a single request body.
201
-
max_body_bytes = 2_621_440
202
-
203
-
# Specifies which origin will be reported as allowed by speculative execution server.
204
-
#
205
-
# If left empty, CORS will be disabled.
206
-
# If set to '*', any origin is allowed.
207
-
# Otherwise, only a specified origin is allowed. The given string must conform to the [origin scheme](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin).
208
-
cors_origin = ''
209
-
210
-
```
162
+
- Known_addresses - these are the bootstrap nodes you will build peers from
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/operators/setup/install-node.md
+17-15
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ Of these `35000` is the only port required to be open for your node to function,
20
20
## Operating System Requirements
21
21
The recommended OS version is Ubuntu 20.04.
22
22
23
-
### Using Ubuntu 22.04
23
+
### Using Ubuntu 22.04 or 24.04
24
24
25
-
Installing using Ubuntu 22.04 follows the same instructions as 20.04 with one exception:
25
+
Installing using Ubuntu 22.04 or 24.04 follows the same instructions as 20.04 with one exception:
26
26
27
27
If you try to install packages, you will receive:
28
28
@@ -33,8 +33,8 @@ casper-client : Depends: libssl1.1 (>= 1.1.0) but it is not installable
33
33
This message is due to the default `openssl` moving to 3.* with Ubuntu 22.04. You need to install OpenSSL 1.* for prior versions of Ubuntu to use the Casper binaries with the following command:
@@ -46,25 +46,27 @@ Before beginning, [update the maximum open files limit](./open-files.md) for you
46
46
If you were running a previous node on this box, this will clean up state. If packages are not installed, the `apt remove` may give errors, but this is not a problem.
echo"deb [arch=amd64 signed-by=/etc/apt/keyrings/casper-repo-pubkey.gpg] https://repo.casper.network/releases focal main"| sudo tee -a /etc/apt/sources.list.d/casper.list
66
67
sudo apt update
67
68
```
69
+
We are creating /etc/apt/keyrings if needed, so we don't have the issue with this key being trusted by all APT requests if stored in /etc/apt/trusted.gpg.d.
68
70
69
71
## Required Tools
70
72
@@ -127,25 +129,25 @@ NODE_ADDR can be set to an IP of a trusted node, or to Casper Labs' public nodes
127
129
128
130
You can find active peers at https://cspr.live/tools/peers or use the following Casper Labs public nodes:
@@ -217,7 +217,7 @@ The table below summarizes the updates.
217
217
To add an associated key to the primary account, use the `add_account.wasm` provided. This example adds two keys to the primary account (`account-hash-d89c*`): `user_1` with `account-hash-e2d0*`, and `user_2` with `account-hash-04a9*`.
@@ -421,7 +421,7 @@ Before removing a key, ensure the remaining associated keys can combine their we
421
421
Given the current setup, the primary account will add an associated key, and then remove it. In other use cases, associated keys may need to combine their signatures to send a multi-sig deploy that removes a key.
@@ -496,7 +496,7 @@ The table below summarizes the updates after calling the `add_account.wasm`.
496
496
The `remove_account.wasm` will remove the newly added account to demonstrate the possibility of removing associated keys that may have been compromised.
Copy file name to clipboardexpand all lines: versioned_docs/version-2.0.0/resources/advanced/storage-workflow.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Both the [`put_key`](https://docs.rs/casper-contract/latest/casper_contract/cont
18
18
19
19
### `storage::write` / `storage::read`
20
20
21
-
[`storage::write`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.write.html) writes a given value to a previously established URef (created using [`storage::new_uref`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.new_uref.html)). Unlike `put_key`, this value is not one of the `Key` types listed above, but rather any of the potential [`CLType`](https://docs.casperlabs.io/developers/json-rpc/types_cl/#cltype)s as outlined. [`storage::read`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.read.html) provides a method to retrieve these values from the associated URef.
21
+
[`storage::write`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.write.html) writes a given value to a previously established URef (created using [`storage::new_uref`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.new_uref.html)). Unlike `put_key`, this value is not one of the `Key` types listed above, but rather any of the potential [`CLType`](https://docs.casper.network/developers/json-rpc/types_cl)s as outlined. [`storage::read`](https://docs.rs/casper-contract/latest/casper_contract/contract_api/storage/fn.read.html) provides a method to retrieve these values from the associated URef.
0 commit comments