From 332563e386b761ccf1c8cd9dc820e9e4a3a142be Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 09:43:28 +0300 Subject: [PATCH 01/17] Create validator.md --- docs/nodes/validator.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 docs/nodes/validator.md diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md new file mode 100644 index 0000000000..8b13789179 --- /dev/null +++ b/docs/nodes/validator.md @@ -0,0 +1 @@ + From 1f8838bb885cc4d37a765881b513f8e62318a1aa Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 09:45:02 +0300 Subject: [PATCH 02/17] Update validator.md --- docs/nodes/validator.md | 137 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 137 insertions(+) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 8b13789179..75430510a9 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -1 +1,138 @@ +--- +sidebar_position: 6 +--- + +# Create a validator + +This is a simple step-by-step guide for setting up a validator on Chiado testnet. It's not a guide on validator architecture or security features. + +:::tip +We've sunsetted [Buenavista](buenavista-testnet/join-buenavista). Please join our new and improved testnet, [Chiado](chiado-testnet/join-chiado). +::: + +## Prerequisites + +The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Join Chiado](chiado-testnet/join-chiado) instructions. + +## 1. Create/restore a key pair + +The first step is to create a new key pair for your validator. Replace `my-key-name` with a key name of your choice and run the following: + +```bash +wardend keys add my-key-name +``` + +:::warning +After creating a new key, you'll see its information and its seed phrase. It's essential to write down this seed phrase and keep it in a safe place. The seed phrase is the only way to restore your keys. Losing it can result in the irrecoverable loss of WARD tokens. +::: + +Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `my-key-name` with a key name of your choice and run the following: + +```bash +wardend keys add my-key-name --recover +``` + +Then get your public address: + +```bash +wardend keys show my-key-name --address +``` + +## 2. Get testnet WARD + +In the next steps, you'll register your new validator by submitting a `create-validator` transaction. Transactions consume gas, so you need to fund your newly created address from the first step. + +You can obtain testnet **WARD** in one of our faucet: + +- [Chiado faucet](https://faucet.chiado.wardenprotocol.org) +- [Discord faucet](https://discord.com/channels/1199357852666560654/1288141727701536818) + +To verify your balance, use this command: + +```bash +wardend query bank balances my-key-name +``` + +## 3. Create a validator + +Once the node is synced and you have the required WARD, you can become a validator. + +To create a validator and initialize it with a self-delegation, you need to create a `validator.json` file and submit a create-validator transaction: + +1. Obtain your validator public key by running the following command: + + ```bash + wardend comet show-validator + ``` + + The output will be similar to this (with a different key): + + ```bash + {"@type":"/cosmos.crypto.ed25519.PubKey","key":"lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I="} + ``` + +2. Create a file named `validator.json` with the following contents: + + ```json + { + "pubkey": { + "@type": "/cosmos.crypto.ed25519.PubKey", + "key": "lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I=" + }, + "amount": "1000000000000000000award", + "moniker": "your validator human-readable name (moniker)", + "identity": "your validator identity signature", + "website": "(optional) your validator website", + "security": "(optional) your validator security contact", + "details": "(optional) your validator details", + "commission-rate": "0.1", + "commission-max-rate": "0.2", + "commission-max-change-rate": "0.01", + "min-self-delegation": "1" + } + ``` + + Here you have the chance to set your validator’s commission rate, maximum rate, and maximum change rate. You can also make the initial self-delegation (`amount`). Remember to replace the `pubkey` field with your own key obtained in the previous step. + + :::warning + When you specify commission parameters, the `commission-max-change-rate` is measured as a percentage point change of the `commission-rate`. For example, a change from 1% to 2% is a 100% rate increase, but the `commission-max-change-rate` is measured as 1%. + ::: + +3. Finally, you're ready to submit the transaction to create the validator: + ```bash + wardend tx staking create-validator validator.json \ + --from=my-key-name \ + --chain-id=chiado_10010-1 \ + --fees=250000000000000award \ + --gas auto \ + --gas-adjustment 1.6 + ``` + :::tip + This transaction is just an example. If you want to see an explanation of the parameters values or see all the available flags that can be set to customize your validators you can enter this command: `wardend tx staking create-validator --help` + ::: + +## 3. Back up critical files + +There are certain files you need to back up to be able to restore your validator if, for some reason, it’s damaged or lost. Please make a secure, encrypted backup of the following files: + +- `priv_validator_key.json` +- `node_key.json` + +## 4. Check your validator + +Check if your validator is in the active set by running this command: + +```bash +wardend query comet-validator-set | grep "$(wardend comet show-address)" +``` + +If the output is empty, your validator isn't in the active set. + +## Next steps + +You're now all set to start validating! You can take these next steps: + +- To learn how to operate an oracle service, see [Operate Skip:Connect](operate-skip-connect). +- To learn more about `wardend` commands for interacting with the node, see [Node commands](node-commands). +- Don't forget to join our community in [Discord](https://discord.com/invite/wardenprotocol). From 3491d59c0e93697e5a6b25fe29ea51a546d4328b Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 09:46:46 +0300 Subject: [PATCH 03/17] Update validator.md --- docs/nodes/validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 75430510a9..30d96a0bc4 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -12,7 +12,7 @@ We've sunsetted [Buenavista](buenavista-testnet/join-buenavista). Please join ou ## Prerequisites -The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Join Chiado](chiado-testnet/join-chiado) instructions. +The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Node Installation Guide](chiado-testnet/join-chiado) instructions. ## 1. Create/restore a key pair From 98f60ce54a7294c4c136870762749bd8c2e375f0 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 09:49:28 +0300 Subject: [PATCH 04/17] Update validator.md --- docs/nodes/validator.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 30d96a0bc4..4d9e3afeab 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -4,15 +4,9 @@ sidebar_position: 6 # Create a validator -This is a simple step-by-step guide for setting up a validator on Chiado testnet. It's not a guide on validator architecture or security features. - -:::tip -We've sunsetted [Buenavista](buenavista-testnet/join-buenavista). Please join our new and improved testnet, [Chiado](chiado-testnet/join-chiado). -::: - ## Prerequisites -The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Node Installation Guide](chiado-testnet/join-chiado) instructions. +The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Node Installation Guide](installation) instructions. ## 1. Create/restore a key pair From db81b545bdfadd5627a5d7d04c4fe92739fca9c2 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 11:19:52 +0300 Subject: [PATCH 05/17] Update installation.md --- docs/nodes/installation.md | 173 ++++++++++++++++++------------------- 1 file changed, 83 insertions(+), 90 deletions(-) diff --git a/docs/nodes/installation.md b/docs/nodes/installation.md index 8a10716617..be1001448a 100644 --- a/docs/nodes/installation.md +++ b/docs/nodes/installation.md @@ -1,138 +1,131 @@ --- -sidebar_position: 1 +sidebar_position: 6 --- -# Node Installation Guide +# Create a validator -## Install Go and Cosmovisor +## Prerequisites -:::tip +The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Node Installation Guide](installation) instructions. -If you already have Go and Cosmovisor, you can skip this step! +## 1. Create/restore a key pair -::: - -### Install Go - -We will use Go `v1.23.4` as example here. The code below also cleanly removes any previous Go installation. +The first step is to create a new key pair for your validator. Replace `my-key-name` with a key name of your choice and run the following: ```bash -sudo rm -rvf /usr/local/go/ -wget https://golang.org/dl/go1.23.4.linux-amd64.tar.gz -sudo tar -C /usr/local -xzf go1.23.4.linux-amd64.tar.gz -rm go1.23.4.linux-amd64.tar.gz +wardend keys add my-key-name ``` -### Configure Go +:::warning +After creating a new key, you'll see its information and its seed phrase. It's essential to write down this seed phrase and keep it in a safe place. The seed phrase is the only way to restore your keys. Losing it can result in the irrecoverable loss of WARD tokens. +::: -Unless you want to configure in a non-standard way, then set these in the `~/.profile` file. +Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `my-key-name` with a key name of your choice and run the following: ```bash -export GOROOT=/usr/local/go -export GOPATH=$HOME/go -export GO111MODULE=on -export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin +wardend keys add my-key-name --recover ``` -### Install Cosmovisor - -We will use Cosmovisor `v1.0.0` as example here. +Then get your public address: ```bash -go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0 +wardend keys show my-key-name --address ``` -## Install Node +## 2. Get testnet WARD -Install the current version of node binary. +In the next steps, you'll register your new validator by submitting a `create-validator` transaction. Transactions consume gas, so you need to fund your newly created address from the first step. -```bash -git clone https://github.com/axone-protocol/axoned axone -cd axone -git checkout v10.0.0 -make install -``` - -## Configure Node +You can obtain testnet **WARD** in one of our faucet: -### Initialize Node +- [Chiado faucet](https://faucet.chiado.wardenprotocol.org) +- [Discord faucet](https://discord.com/channels/1199357852666560654/1288141727701536818) -Please replace `YOUR_MONIKER` with your own moniker. +To verify your balance, use this command: ```bash -axoned init YOUR_MONIKER --chain-id axone-dentrite-1 +wardend query bank balances my-key-name ``` -### Download Genesis +## 3. Create a validator -The genesis file link below is the official genesis download link. +Once the node is synced and you have the required WARD, you can become a validator. -```bash -wget -O genesis.json https://raw.githubusercontent.com/axone-protocol/networks/911b2d34631ac242e9ef3be577163653ed644726/chains/dentrite-1/genesis.json --inet4-only -mv genesis.json ~/.axoned/config -``` +To create a validator and initialize it with a self-delegation, you need to create a `validator.json` file and submit a create-validator transaction: -### Configure Seed +1. Obtain your validator public key by running the following command: -Using a seed node to bootstrap is the best practice. + ```bash + wardend comet show-validator + ``` -```bash -sed -i 's/seeds = ""/seeds = "ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@testnet-seeds.polkachu.com:17656"/' ~/.axoned/config/config.toml -``` + The output will be similar to this (with a different key): -## Launch Node + ```bash + {"@type":"/cosmos.crypto.ed25519.PubKey","key":"lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I="} + ``` -### Configure Cosmovisor Folder +2. Create a file named `validator.json` with the following contents: -Create Cosmovisor folders and load the node binary. + ```json + { + "pubkey": { + "@type": "/cosmos.crypto.ed25519.PubKey", + "key": "lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I=" + }, + "amount": "1000000000000000000award", + "moniker": "your validator human-readable name (moniker)", + "identity": "your validator identity signature", + "website": "(optional) your validator website", + "security": "(optional) your validator security contact", + "details": "(optional) your validator details", + "commission-rate": "0.1", + "commission-max-rate": "0.2", + "commission-max-change-rate": "0.01", + "min-self-delegation": "1" + } + ``` -```bash -# Create Cosmovisor Folders -mkdir -p ~/.axoned/cosmovisor/genesis/bin -mkdir -p ~/.axoned/cosmovisor/upgrades + Here you have the chance to set your validator’s commission rate, maximum rate, and maximum change rate. You can also make the initial self-delegation (`amount`). Remember to replace the `pubkey` field with your own key obtained in the previous step. -# Load Node Binary into Cosmovisor Folder -cp ~/go/bin/axoned ~/.axoned/cosmovisor/genesis/bin -``` + :::warning + When you specify commission parameters, the `commission-max-change-rate` is measured as a percentage point change of the `commission-rate`. For example, a change from 1% to 2% is a 100% rate increase, but the `commission-max-change-rate` is measured as 1%. + ::: -### Create Service Files +3. Finally, you're ready to submit the transaction to create the validator: + ```bash + wardend tx staking create-validator validator.json \ + --from=my-key-name \ + --chain-id=chiado_10010-1 \ + --fees=250000000000000award \ + --gas auto \ + --gas-adjustment 1.6 + ``` + :::tip + This transaction is just an example. If you want to see an explanation of the parameters values or see all the available flags that can be set to customize your validators you can enter this command: `wardend tx staking create-validator --help` + ::: -Create a `axone.service` file in the `/etc/systemd/system` folder with the following code snippet. Make sure to replace `USER` with your Linux user name. You need sudo privilege to do this step. +## 3. Back up critical files -```bash -[Unit] -Description="axone node" -After=network-online.target - -[Service] -User=USER -ExecStart=/home/USER/go/bin/cosmovisor start -Restart=always -RestartSec=3 -LimitNOFILE=4096 -Environment="DAEMON_NAME=axoned" -Environment="DAEMON_HOME=/home/USER/.axoned" -Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=false" -Environment="DAEMON_RESTART_AFTER_UPGRADE=true" -Environment="UNSAFE_SKIP_BACKUP=true" - -[Install] -WantedBy=multi-user.target -``` +There are certain files you need to back up to be able to restore your validator if, for some reason, it’s damaged or lost. Please make a secure, encrypted backup of the following files: -### Download Snapshot +- `priv_validator_key.json` +- `node_key.json` -Use this popular download service to download and extract Axone snapshot. +## 4. Check your validator -### Start Node Service +Check if your validator is in the active set by running this command: ```bash -# Enable service -sudo systemctl enable axone.service +wardend query comet-validator-set | grep "$(wardend comet show-address)" +``` -# Start service -sudo service axone start +If the output is empty, your validator isn't in the active set. -# Check logs -sudo journalctl -fu axone -``` +## Next steps + +You're now all set to start validating! You can take these next steps: + +- To learn how to operate an oracle service, see [Operate Skip:Connect](operate-skip-connect). +- To learn more about `wardend` commands for interacting with the node, see [Node commands](node-commands). +- Don't forget to join our community in [Discord](https://discord.com/invite/wardenprotocol). From 82edd57b3065ec7671961836a13682e2ae539436 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 11:20:41 +0300 Subject: [PATCH 06/17] Update installation.md --- docs/nodes/installation.md | 173 +++++++++++++++++++------------------ 1 file changed, 90 insertions(+), 83 deletions(-) diff --git a/docs/nodes/installation.md b/docs/nodes/installation.md index be1001448a..8a10716617 100644 --- a/docs/nodes/installation.md +++ b/docs/nodes/installation.md @@ -1,131 +1,138 @@ --- -sidebar_position: 6 +sidebar_position: 1 --- -# Create a validator +# Node Installation Guide -## Prerequisites +## Install Go and Cosmovisor -The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Node Installation Guide](installation) instructions. +:::tip -## 1. Create/restore a key pair +If you already have Go and Cosmovisor, you can skip this step! -The first step is to create a new key pair for your validator. Replace `my-key-name` with a key name of your choice and run the following: - -```bash -wardend keys add my-key-name -``` - -:::warning -After creating a new key, you'll see its information and its seed phrase. It's essential to write down this seed phrase and keep it in a safe place. The seed phrase is the only way to restore your keys. Losing it can result in the irrecoverable loss of WARD tokens. ::: -Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `my-key-name` with a key name of your choice and run the following: +### Install Go + +We will use Go `v1.23.4` as example here. The code below also cleanly removes any previous Go installation. ```bash -wardend keys add my-key-name --recover +sudo rm -rvf /usr/local/go/ +wget https://golang.org/dl/go1.23.4.linux-amd64.tar.gz +sudo tar -C /usr/local -xzf go1.23.4.linux-amd64.tar.gz +rm go1.23.4.linux-amd64.tar.gz ``` -Then get your public address: +### Configure Go + +Unless you want to configure in a non-standard way, then set these in the `~/.profile` file. ```bash -wardend keys show my-key-name --address +export GOROOT=/usr/local/go +export GOPATH=$HOME/go +export GO111MODULE=on +export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin ``` -## 2. Get testnet WARD +### Install Cosmovisor -In the next steps, you'll register your new validator by submitting a `create-validator` transaction. Transactions consume gas, so you need to fund your newly created address from the first step. +We will use Cosmovisor `v1.0.0` as example here. -You can obtain testnet **WARD** in one of our faucet: +```bash +go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0 +``` -- [Chiado faucet](https://faucet.chiado.wardenprotocol.org) -- [Discord faucet](https://discord.com/channels/1199357852666560654/1288141727701536818) +## Install Node -To verify your balance, use this command: +Install the current version of node binary. ```bash -wardend query bank balances my-key-name +git clone https://github.com/axone-protocol/axoned axone +cd axone +git checkout v10.0.0 +make install ``` -## 3. Create a validator +## Configure Node -Once the node is synced and you have the required WARD, you can become a validator. +### Initialize Node -To create a validator and initialize it with a self-delegation, you need to create a `validator.json` file and submit a create-validator transaction: +Please replace `YOUR_MONIKER` with your own moniker. -1. Obtain your validator public key by running the following command: +```bash +axoned init YOUR_MONIKER --chain-id axone-dentrite-1 +``` - ```bash - wardend comet show-validator - ``` +### Download Genesis - The output will be similar to this (with a different key): +The genesis file link below is the official genesis download link. - ```bash - {"@type":"/cosmos.crypto.ed25519.PubKey","key":"lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I="} - ``` +```bash +wget -O genesis.json https://raw.githubusercontent.com/axone-protocol/networks/911b2d34631ac242e9ef3be577163653ed644726/chains/dentrite-1/genesis.json --inet4-only +mv genesis.json ~/.axoned/config +``` -2. Create a file named `validator.json` with the following contents: +### Configure Seed - ```json - { - "pubkey": { - "@type": "/cosmos.crypto.ed25519.PubKey", - "key": "lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I=" - }, - "amount": "1000000000000000000award", - "moniker": "your validator human-readable name (moniker)", - "identity": "your validator identity signature", - "website": "(optional) your validator website", - "security": "(optional) your validator security contact", - "details": "(optional) your validator details", - "commission-rate": "0.1", - "commission-max-rate": "0.2", - "commission-max-change-rate": "0.01", - "min-self-delegation": "1" - } - ``` +Using a seed node to bootstrap is the best practice. - Here you have the chance to set your validator’s commission rate, maximum rate, and maximum change rate. You can also make the initial self-delegation (`amount`). Remember to replace the `pubkey` field with your own key obtained in the previous step. +```bash +sed -i 's/seeds = ""/seeds = "ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@testnet-seeds.polkachu.com:17656"/' ~/.axoned/config/config.toml +``` - :::warning - When you specify commission parameters, the `commission-max-change-rate` is measured as a percentage point change of the `commission-rate`. For example, a change from 1% to 2% is a 100% rate increase, but the `commission-max-change-rate` is measured as 1%. - ::: +## Launch Node -3. Finally, you're ready to submit the transaction to create the validator: - ```bash - wardend tx staking create-validator validator.json \ - --from=my-key-name \ - --chain-id=chiado_10010-1 \ - --fees=250000000000000award \ - --gas auto \ - --gas-adjustment 1.6 - ``` - :::tip - This transaction is just an example. If you want to see an explanation of the parameters values or see all the available flags that can be set to customize your validators you can enter this command: `wardend tx staking create-validator --help` - ::: +### Configure Cosmovisor Folder -## 3. Back up critical files +Create Cosmovisor folders and load the node binary. -There are certain files you need to back up to be able to restore your validator if, for some reason, it’s damaged or lost. Please make a secure, encrypted backup of the following files: +```bash +# Create Cosmovisor Folders +mkdir -p ~/.axoned/cosmovisor/genesis/bin +mkdir -p ~/.axoned/cosmovisor/upgrades -- `priv_validator_key.json` -- `node_key.json` +# Load Node Binary into Cosmovisor Folder +cp ~/go/bin/axoned ~/.axoned/cosmovisor/genesis/bin +``` -## 4. Check your validator +### Create Service Files -Check if your validator is in the active set by running this command: +Create a `axone.service` file in the `/etc/systemd/system` folder with the following code snippet. Make sure to replace `USER` with your Linux user name. You need sudo privilege to do this step. ```bash -wardend query comet-validator-set | grep "$(wardend comet show-address)" +[Unit] +Description="axone node" +After=network-online.target + +[Service] +User=USER +ExecStart=/home/USER/go/bin/cosmovisor start +Restart=always +RestartSec=3 +LimitNOFILE=4096 +Environment="DAEMON_NAME=axoned" +Environment="DAEMON_HOME=/home/USER/.axoned" +Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=false" +Environment="DAEMON_RESTART_AFTER_UPGRADE=true" +Environment="UNSAFE_SKIP_BACKUP=true" + +[Install] +WantedBy=multi-user.target ``` -If the output is empty, your validator isn't in the active set. +### Download Snapshot + +Use this popular download service to download and extract Axone snapshot. -## Next steps +### Start Node Service -You're now all set to start validating! You can take these next steps: +```bash +# Enable service +sudo systemctl enable axone.service -- To learn how to operate an oracle service, see [Operate Skip:Connect](operate-skip-connect). -- To learn more about `wardend` commands for interacting with the node, see [Node commands](node-commands). -- Don't forget to join our community in [Discord](https://discord.com/invite/wardenprotocol). +# Start service +sudo service axone start + +# Check logs +sudo journalctl -fu axone +``` From 21da15910377f184e8c6444709b04e2276bad5da Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 11:20:53 +0300 Subject: [PATCH 07/17] Update validator.md --- docs/nodes/validator.md | 172 +++++++++++++++++++++------------------- 1 file changed, 89 insertions(+), 83 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 4d9e3afeab..8a10716617 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -1,132 +1,138 @@ --- -sidebar_position: 6 +sidebar_position: 1 --- -# Create a validator +# Node Installation Guide -## Prerequisites +## Install Go and Cosmovisor -The following instructions assume you have already set up a full node and are synchronized to the latest block height. If you haven’t done so, please follow the [Node Installation Guide](installation) instructions. +:::tip -## 1. Create/restore a key pair +If you already have Go and Cosmovisor, you can skip this step! -The first step is to create a new key pair for your validator. Replace `my-key-name` with a key name of your choice and run the following: - -```bash -wardend keys add my-key-name -``` - -:::warning -After creating a new key, you'll see its information and its seed phrase. It's essential to write down this seed phrase and keep it in a safe place. The seed phrase is the only way to restore your keys. Losing it can result in the irrecoverable loss of WARD tokens. ::: -Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `my-key-name` with a key name of your choice and run the following: +### Install Go + +We will use Go `v1.23.4` as example here. The code below also cleanly removes any previous Go installation. ```bash -wardend keys add my-key-name --recover +sudo rm -rvf /usr/local/go/ +wget https://golang.org/dl/go1.23.4.linux-amd64.tar.gz +sudo tar -C /usr/local -xzf go1.23.4.linux-amd64.tar.gz +rm go1.23.4.linux-amd64.tar.gz ``` -Then get your public address: +### Configure Go + +Unless you want to configure in a non-standard way, then set these in the `~/.profile` file. ```bash -wardend keys show my-key-name --address +export GOROOT=/usr/local/go +export GOPATH=$HOME/go +export GO111MODULE=on +export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin ``` -## 2. Get testnet WARD +### Install Cosmovisor -In the next steps, you'll register your new validator by submitting a `create-validator` transaction. Transactions consume gas, so you need to fund your newly created address from the first step. +We will use Cosmovisor `v1.0.0` as example here. -You can obtain testnet **WARD** in one of our faucet: +```bash +go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0 +``` -- [Chiado faucet](https://faucet.chiado.wardenprotocol.org) -- [Discord faucet](https://discord.com/channels/1199357852666560654/1288141727701536818) +## Install Node -To verify your balance, use this command: +Install the current version of node binary. ```bash -wardend query bank balances my-key-name +git clone https://github.com/axone-protocol/axoned axone +cd axone +git checkout v10.0.0 +make install ``` -## 3. Create a validator +## Configure Node -Once the node is synced and you have the required WARD, you can become a validator. +### Initialize Node -To create a validator and initialize it with a self-delegation, you need to create a `validator.json` file and submit a create-validator transaction: +Please replace `YOUR_MONIKER` with your own moniker. -1. Obtain your validator public key by running the following command: +```bash +axoned init YOUR_MONIKER --chain-id axone-dentrite-1 +``` - ```bash - wardend comet show-validator - ``` +### Download Genesis - The output will be similar to this (with a different key): +The genesis file link below is the official genesis download link. - ```bash - {"@type":"/cosmos.crypto.ed25519.PubKey","key":"lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I="} - ``` +```bash +wget -O genesis.json https://raw.githubusercontent.com/axone-protocol/networks/911b2d34631ac242e9ef3be577163653ed644726/chains/dentrite-1/genesis.json --inet4-only +mv genesis.json ~/.axoned/config +``` -2. Create a file named `validator.json` with the following contents: +### Configure Seed - ```json - { - "pubkey": { - "@type": "/cosmos.crypto.ed25519.PubKey", - "key": "lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I=" - }, - "amount": "1000000000000000000award", - "moniker": "your validator human-readable name (moniker)", - "identity": "your validator identity signature", - "website": "(optional) your validator website", - "security": "(optional) your validator security contact", - "details": "(optional) your validator details", - "commission-rate": "0.1", - "commission-max-rate": "0.2", - "commission-max-change-rate": "0.01", - "min-self-delegation": "1" - } - ``` +Using a seed node to bootstrap is the best practice. - Here you have the chance to set your validator’s commission rate, maximum rate, and maximum change rate. You can also make the initial self-delegation (`amount`). Remember to replace the `pubkey` field with your own key obtained in the previous step. +```bash +sed -i 's/seeds = ""/seeds = "ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@testnet-seeds.polkachu.com:17656"/' ~/.axoned/config/config.toml +``` - :::warning - When you specify commission parameters, the `commission-max-change-rate` is measured as a percentage point change of the `commission-rate`. For example, a change from 1% to 2% is a 100% rate increase, but the `commission-max-change-rate` is measured as 1%. - ::: +## Launch Node -3. Finally, you're ready to submit the transaction to create the validator: - ```bash - wardend tx staking create-validator validator.json \ - --from=my-key-name \ - --chain-id=chiado_10010-1 \ - --fees=250000000000000award \ - --gas auto \ - --gas-adjustment 1.6 - ``` - :::tip - This transaction is just an example. If you want to see an explanation of the parameters values or see all the available flags that can be set to customize your validators you can enter this command: `wardend tx staking create-validator --help` - ::: +### Configure Cosmovisor Folder -## 3. Back up critical files +Create Cosmovisor folders and load the node binary. -There are certain files you need to back up to be able to restore your validator if, for some reason, it’s damaged or lost. Please make a secure, encrypted backup of the following files: +```bash +# Create Cosmovisor Folders +mkdir -p ~/.axoned/cosmovisor/genesis/bin +mkdir -p ~/.axoned/cosmovisor/upgrades -- `priv_validator_key.json` -- `node_key.json` +# Load Node Binary into Cosmovisor Folder +cp ~/go/bin/axoned ~/.axoned/cosmovisor/genesis/bin +``` -## 4. Check your validator +### Create Service Files -Check if your validator is in the active set by running this command: +Create a `axone.service` file in the `/etc/systemd/system` folder with the following code snippet. Make sure to replace `USER` with your Linux user name. You need sudo privilege to do this step. ```bash -wardend query comet-validator-set | grep "$(wardend comet show-address)" +[Unit] +Description="axone node" +After=network-online.target + +[Service] +User=USER +ExecStart=/home/USER/go/bin/cosmovisor start +Restart=always +RestartSec=3 +LimitNOFILE=4096 +Environment="DAEMON_NAME=axoned" +Environment="DAEMON_HOME=/home/USER/.axoned" +Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=false" +Environment="DAEMON_RESTART_AFTER_UPGRADE=true" +Environment="UNSAFE_SKIP_BACKUP=true" + +[Install] +WantedBy=multi-user.target ``` -If the output is empty, your validator isn't in the active set. +### Download Snapshot + +Use this popular download service to download and extract Axone snapshot. -## Next steps +### Start Node Service -You're now all set to start validating! You can take these next steps: +```bash +# Enable service +sudo systemctl enable axone.service -- To learn how to operate an oracle service, see [Operate Skip:Connect](operate-skip-connect). -- To learn more about `wardend` commands for interacting with the node, see [Node commands](node-commands). -- Don't forget to join our community in [Discord](https://discord.com/invite/wardenprotocol). +# Start service +sudo service axone start +# Check logs +sudo journalctl -fu axone +``` From 100374afa8ec4532aadafa078962bbe9f15a78a7 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 11:24:21 +0300 Subject: [PATCH 08/17] Update validator.md --- docs/nodes/validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 8a10716617..4cab54c3f6 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -2,7 +2,7 @@ sidebar_position: 1 --- -# Node Installation Guide +# Create a validator ## Install Go and Cosmovisor From 7743fb2ff69cb0b9edcfa2f3ec75656293ab805e Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 11:26:10 +0300 Subject: [PATCH 09/17] Update validator.md --- docs/nodes/validator.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 4cab54c3f6..88e7e0ad23 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -4,6 +4,8 @@ sidebar_position: 1 # Create a validator +This guide walks you through the basic steps to set up a validator on the Axone testnet. It focuses on the setup process and does not discuss validator architecture or security measures. + ## Install Go and Cosmovisor :::tip From 651466a1d4690ee124c29d45ba4aaf2002803052 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 11:51:08 +0300 Subject: [PATCH 10/17] Update validator.md --- docs/nodes/validator.md | 170 +++++++++++++++++++--------------------- 1 file changed, 81 insertions(+), 89 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 88e7e0ad23..720eb82797 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -2,139 +2,131 @@ sidebar_position: 1 --- -# Create a validator +# Create a Validator This guide walks you through the basic steps to set up a validator on the Axone testnet. It focuses on the setup process and does not discuss validator architecture or security measures. -## Install Go and Cosmovisor +## Prerequisites -:::tip +Before following these steps, ensure you have a fully synchronized full node running. If you haven’t set one up yet, refer to the [Node Installation Guide](installation) instructions. -If you already have Go and Cosmovisor, you can skip this step! +## 1. Create or restore a key pair -::: - -### Install Go - -We will use Go `v1.23.4` as example here. The code below also cleanly removes any previous Go installation. +The first step is to create a new key pair for your validator. Replace `Wallet name` with a key name of your choice and run the following: ```bash -sudo rm -rvf /usr/local/go/ -wget https://golang.org/dl/go1.23.4.linux-amd64.tar.gz -sudo tar -C /usr/local -xzf go1.23.4.linux-amd64.tar.gz -rm go1.23.4.linux-amd64.tar.gz +axoned keys add ``` -### Configure Go +:::warning +After generating a new key, you’ll receive its information along with a seed phrase. This phrase is critical: store it in a safe place, as it’s the sole backup for restoring your keys. Losing it means losing access to your $AXONE tokens forever. +::: -Unless you want to configure in a non-standard way, then set these in the `~/.profile` file. +Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `Wallet name` with a key name of your choice and run the following: ```bash -export GOROOT=/usr/local/go -export GOPATH=$HOME/go -export GO111MODULE=on -export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin +axoned keys add --recover ``` -### Install Cosmovisor - -We will use Cosmovisor `v1.0.0` as example here. +Then get your public address: ```bash -go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0 +axoned keys show --address ``` -## Install Node +## 2. Get testnet $AXONE -Install the current version of node binary. +The validator registration process involves sending a create-validator transaction, which requires gas fees. Before proceeding, make sure to send funds to the address you generated earlier. + +You can get testnet $AXONE tokens from faucet: + +- [Axone testnet faucet](https://faucet.axone.xyz) +- +To verify your balance, use this command: ```bash -git clone https://github.com/axone-protocol/axoned axone -cd axone -git checkout v10.0.0 -make install +axoned query bank balances ``` -## Configure Node +## 3. Create a validator -### Initialize Node +Once your node is fully synchronized and you've acquired the necessary $AXONE tokens, you can proceed with validator registration. -Please replace `YOUR_MONIKER` with your own moniker. +To establish a validator with an initial self-delegation, prepare a `validator.json` configuration file and execute the create-validator transaction. -```bash -axoned init YOUR_MONIKER --chain-id axone-dentrite-1 -``` +1. Obtain your validator public key by running the following command: -### Download Genesis + ```bash + axoned comet show-validator + ``` -The genesis file link below is the official genesis download link. + The command output will resemble the following example (with a different validator key): -```bash -wget -O genesis.json https://raw.githubusercontent.com/axone-protocol/networks/911b2d34631ac242e9ef3be577163653ed644726/chains/dentrite-1/genesis.json --inet4-only -mv genesis.json ~/.axoned/config -``` + ```bash + {"@type":"/cosmos.crypto.ed25519.PubKey","key":"lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I="} + ``` -### Configure Seed +2. Create a file named `validator.json` with the following contents: -Using a seed node to bootstrap is the best practice. + ```json + { + "pubkey": { + "@type": "/cosmos.crypto.ed25519.PubKey", + "key": "lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I=" + }, + "amount": "1000000000000000000award", + "moniker": "your validator human-readable name (moniker)", + "identity": "your validator identity signature", + "website": "(optional) your validator website", + "security": "(optional) your validator security contact", + "details": "(optional) your validator details", + "commission-rate": "0.1", + "commission-max-rate": "0.2", + "commission-max-change-rate": "0.01", + "min-self-delegation": "1" + } + ``` -```bash -sed -i 's/seeds = ""/seeds = "ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@testnet-seeds.polkachu.com:17656"/' ~/.axoned/config/config.toml -``` + Here you have the chance to set your validator’s commission rate, maximum rate, and maximum change rate. You can also make the initial self-delegation (`amount`). Remember to replace the `pubkey` field with your own key obtained in the previous step. -## Launch Node + :::warning + When you specify commission parameters, the `commission-max-change-rate` is measured as a percentage point change of the `commission-rate`. For example, a change from 1% to 2% is a 100% rate increase, but the `commission-max-change-rate` is measured as 1%. + ::: -### Configure Cosmovisor Folder +3. Finally, you're ready to submit the transaction to create the validator: + ```bash + wardend tx staking create-validator validator.json \ + --from=my-key-name \ + --chain-id=chiado_10010-1 \ + --fees=250000000000000award \ + --gas auto \ + --gas-adjustment 1.6 + ``` + :::tip + This transaction is just an example. If you want to see an explanation of the parameters values or see all the available flags that can be set to customize your validators you can enter this command: `wardend tx staking create-validator --help` + ::: -Create Cosmovisor folders and load the node binary. +## 3. Back up critical files -```bash -# Create Cosmovisor Folders -mkdir -p ~/.axoned/cosmovisor/genesis/bin -mkdir -p ~/.axoned/cosmovisor/upgrades +There are certain files you need to back up to be able to restore your validator if, for some reason, it’s damaged or lost. Please make a secure, encrypted backup of the following files: -# Load Node Binary into Cosmovisor Folder -cp ~/go/bin/axoned ~/.axoned/cosmovisor/genesis/bin -``` +- `priv_validator_key.json` +- `node_key.json` -### Create Service Files +## 4. Check your validator -Create a `axone.service` file in the `/etc/systemd/system` folder with the following code snippet. Make sure to replace `USER` with your Linux user name. You need sudo privilege to do this step. +Check if your validator is in the active set by running this command: ```bash -[Unit] -Description="axone node" -After=network-online.target - -[Service] -User=USER -ExecStart=/home/USER/go/bin/cosmovisor start -Restart=always -RestartSec=3 -LimitNOFILE=4096 -Environment="DAEMON_NAME=axoned" -Environment="DAEMON_HOME=/home/USER/.axoned" -Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=false" -Environment="DAEMON_RESTART_AFTER_UPGRADE=true" -Environment="UNSAFE_SKIP_BACKUP=true" - -[Install] -WantedBy=multi-user.target +wardend query comet-validator-set | grep "$(wardend comet show-address)" ``` -### Download Snapshot +If the output is empty, your validator isn't in the active set. -Use this popular download service to download and extract Axone snapshot. +## Next steps -### Start Node Service +You're now all set to start validating! You can take these next steps: -```bash -# Enable service -sudo systemctl enable axone.service - -# Start service -sudo service axone start - -# Check logs -sudo journalctl -fu axone -``` +- To learn how to operate an oracle service, see [Operate Skip:Connect](operate-skip-connect). +- To learn more about `wardend` commands for interacting with the node, see [Node commands](node-commands). +- Don't forget to join our community in [Discord](https://discord.com/invite/wardenprotocol). From ecbdc1ec5e789cc13479c6bcbce64173db9be8b0 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 12:29:25 +0300 Subject: [PATCH 11/17] Update validator.md --- docs/nodes/validator.md | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 720eb82797..a01aef5068 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -118,15 +118,7 @@ There are certain files you need to back up to be able to restore your validator Check if your validator is in the active set by running this command: ```bash -wardend query comet-validator-set | grep "$(wardend comet show-address)" +axoned query comet-validator-set | grep "$(axonedd comet show-address)" ``` If the output is empty, your validator isn't in the active set. - -## Next steps - -You're now all set to start validating! You can take these next steps: - -- To learn how to operate an oracle service, see [Operate Skip:Connect](operate-skip-connect). -- To learn more about `wardend` commands for interacting with the node, see [Node commands](node-commands). -- Don't forget to join our community in [Discord](https://discord.com/invite/wardenprotocol). From 11ddf3cadbc4156ce06d67a2bbe5c2b90131d68c Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 12:31:15 +0300 Subject: [PATCH 12/17] Update validator.md --- docs/nodes/validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index a01aef5068..1b881ad55f 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -41,7 +41,7 @@ The validator registration process involves sending a create-validator transacti You can get testnet $AXONE tokens from faucet: - [Axone testnet faucet](https://faucet.axone.xyz) -- + To verify your balance, use this command: ```bash From e9b28b089fb1b5dbdecf7f73ddf717bdbf2180ab Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 12:46:02 +0300 Subject: [PATCH 13/17] Update validator.md --- docs/nodes/validator.md | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 1b881ad55f..62f48c5017 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -12,26 +12,26 @@ Before following these steps, ensure you have a fully synchronized full node run ## 1. Create or restore a key pair -The first step is to create a new key pair for your validator. Replace `Wallet name` with a key name of your choice and run the following: +The first step is to create a new key pair for your validator. Replace `WALLET_NAME` with a key name of your choice and run the following: ```bash -axoned keys add +axoned keys add WALLET_NAME ``` :::warning After generating a new key, you’ll receive its information along with a seed phrase. This phrase is critical: store it in a safe place, as it’s the sole backup for restoring your keys. Losing it means losing access to your $AXONE tokens forever. ::: -Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `Wallet name` with a key name of your choice and run the following: +Alternatively, you can restore an existing wallet with a mnemonic seed phrase. Replace `WALLET_NAME` with a key name of your choice and run the following: ```bash -axoned keys add --recover +axoned keys add WALLET_NAME --recover ``` Then get your public address: ```bash -axoned keys show --address +axoned keys show WALLET_NAME --address ``` ## 2. Get testnet $AXONE @@ -45,7 +45,7 @@ You can get testnet $AXONE tokens from faucet: To verify your balance, use this command: ```bash -axoned query bank balances +axoned query bank balances WALLET_NAME ``` ## 3. Create a validator @@ -63,7 +63,7 @@ To establish a validator with an initial self-delegation, prepare a `validator.j The command output will resemble the following example (with a different validator key): ```bash - {"@type":"/cosmos.crypto.ed25519.PubKey","key":"lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I="} + {"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A/iJGMhwsd5J4y0weGxmSqT2q1G9g0nFo6GgCHBopwc0"} ``` 2. Create a file named `validator.json` with the following contents: @@ -72,9 +72,9 @@ To establish a validator with an initial self-delegation, prepare a `validator.j { "pubkey": { "@type": "/cosmos.crypto.ed25519.PubKey", - "key": "lR1d7YBVK5jYijOfWVKRFoWCsS4dg3kagT7LB9GnG8I=" + "key": "A/iJGMhwsd5J4y0weGxmSqT2q1G9g0nFo6GgCHBopwc0" }, - "amount": "1000000000000000000award", + "amount": "1000000uaxone", "moniker": "your validator human-readable name (moniker)", "identity": "your validator identity signature", "website": "(optional) your validator website", @@ -87,16 +87,19 @@ To establish a validator with an initial self-delegation, prepare a `validator.j } ``` - Here you have the chance to set your validator’s commission rate, maximum rate, and maximum change rate. You can also make the initial self-delegation (`amount`). Remember to replace the `pubkey` field with your own key obtained in the previous step. + Max-change-rate, set the initial self-delegation (`amount`), and must replace the key field with your own validator `key` from earlier. + + :::warning + When setting commission parameters, the `commission-max-change-rate` is measured **in percentage points** of the `commission-rate`. + For example: changing from `1%` to `2%` represents a `100%` relative increase, + but the `commission-max-change-rate` value would be `0.01` (1 percentage point). + ::: - :::warning - When you specify commission parameters, the `commission-max-change-rate` is measured as a percentage point change of the `commission-rate`. For example, a change from 1% to 2% is a 100% rate increase, but the `commission-max-change-rate` is measured as 1%. - ::: -3. Finally, you're ready to submit the transaction to create the validator: +4. Finally, you're ready to submit the transaction to create the validator: ```bash wardend tx staking create-validator validator.json \ - --from=my-key-name \ + --from=WALLET_NAME \ --chain-id=chiado_10010-1 \ --fees=250000000000000award \ --gas auto \ From 02c888823bdfce57637241069e4943f88b7fa77d Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 14:06:45 +0300 Subject: [PATCH 14/17] Update validator.md --- docs/nodes/validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 62f48c5017..f1014aa01a 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -87,7 +87,7 @@ To establish a validator with an initial self-delegation, prepare a `validator.j } ``` - Max-change-rate, set the initial self-delegation (`amount`), and must replace the key field with your own validator `key` from earlier. + Max-change-rate, set the initial self-delegation `amount`, and must replace the key field with your own validator `key` from earlier. :::warning When setting commission parameters, the `commission-max-change-rate` is measured **in percentage points** of the `commission-rate`. From f9137d08322a8b33710f0ce612688c2dea71f0da Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Sun, 27 Apr 2025 14:17:22 +0300 Subject: [PATCH 15/17] Update validator.md --- docs/nodes/validator.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index f1014aa01a..f0e0516f2e 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -96,22 +96,22 @@ To establish a validator with an initial self-delegation, prepare a `validator.j ::: -4. Finally, you're ready to submit the transaction to create the validator: +4. You're now ready to submit the transaction and create your validator ```bash - wardend tx staking create-validator validator.json \ + axoned tx staking create-validator validator.json \ --from=WALLET_NAME \ - --chain-id=chiado_10010-1 \ - --fees=250000000000000award \ + --chain-id=axone-dentrite-1 \ + --fees=900000uaxone \ --gas auto \ --gas-adjustment 1.6 ``` :::tip - This transaction is just an example. If you want to see an explanation of the parameters values or see all the available flags that can be set to customize your validators you can enter this command: `wardend tx staking create-validator --help` + This is just a sample transaction. To explore all available parameters and customization flags for your validator, run: `axoned tx staking create-validator --help` ::: -## 3. Back up critical files +## 3. Make sure to create backups of all important files before proceeding -There are certain files you need to back up to be able to restore your validator if, for some reason, it’s damaged or lost. Please make a secure, encrypted backup of the following files: +To ensure validator recovery in case of failure or data loss, you must create encrypted backups of these critical files: - `priv_validator_key.json` - `node_key.json` @@ -121,7 +121,7 @@ There are certain files you need to back up to be able to restore your validator Check if your validator is in the active set by running this command: ```bash -axoned query comet-validator-set | grep "$(axonedd comet show-address)" +axoned query comet-validator-set | grep "$(axoned comet show-address)" ``` -If the output is empty, your validator isn't in the active set. +An empty output indicates your validator is not currently in the active set. From e065d22437f642d1084d83450cbb0050ca61d2bb Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Tue, 29 Apr 2025 07:15:41 +0300 Subject: [PATCH 16/17] Update validator.md Co-authored-by: Chris --- docs/nodes/validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index f0e0516f2e..9e7c6e7947 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -121,7 +121,7 @@ To ensure validator recovery in case of failure or data loss, you must create en Check if your validator is in the active set by running this command: ```bash -axoned query comet-validator-set | grep "$(axoned comet show-address)" +axoned query consensus comet validator-set | grep "$(axoned comet show-address)" ``` An empty output indicates your validator is not currently in the active set. From 6707d3bae286a1116c93a5ab891c1fb174558e87 Mon Sep 17 00:00:00 2001 From: BITNODES <135651866+opsmanager1@users.noreply.github.com> Date: Tue, 29 Apr 2025 21:54:38 +0300 Subject: [PATCH 17/17] Update docs/nodes/validator.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- docs/nodes/validator.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/nodes/validator.md b/docs/nodes/validator.md index 9e7c6e7947..2dd599b621 100644 --- a/docs/nodes/validator.md +++ b/docs/nodes/validator.md @@ -109,14 +109,14 @@ To establish a validator with an initial self-delegation, prepare a `validator.j This is just a sample transaction. To explore all available parameters and customization flags for your validator, run: `axoned tx staking create-validator --help` ::: -## 3. Make sure to create backups of all important files before proceeding +## 4. Make sure to create backups of all important files before proceeding To ensure validator recovery in case of failure or data loss, you must create encrypted backups of these critical files: - `priv_validator_key.json` - `node_key.json` -## 4. Check your validator +## 5. Check your validator Check if your validator is in the active set by running this command: