Skip to content

Commit f7838df

Browse files
committed
update content
1 parent 979be37 commit f7838df

16 files changed

+1199
-1162
lines changed

.ai/pages/node-infrastructure-run-a-collator-collator.md

Lines changed: 0 additions & 608 deletions
This file was deleted.

.ai/pages/node-infrastructure-run-a-collator.md

Lines changed: 666 additions & 0 deletions
Large diffs are not rendered by default.

.ai/pages/node-infrastructure-run-a-node-parachain-rpc.md

Lines changed: 253 additions & 267 deletions
Large diffs are not rendered by default.

.ai/pages/node-infrastructure-run-a-node-polkadot-hub-rpc.md

Lines changed: 218 additions & 220 deletions
Large diffs are not rendered by default.

.ai/pages/node-infrastructure-run-a-node-relay-chain-full-node.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Before getting started, ensure the following prerequisites are met:
2727
- [Install the necessary dependencies for the Polkadot SDK](/parachains/install-polkadot-sdk/){target=\_blank}.
2828

2929
!!! warning
30-
This setup is not recommended for validators. If you plan to run a validator, refer to the [Running a Validator](/nodes-and-validators/run-a-validator/onboarding-and-offboarding/set-up-validator/){target=\_blank} guide for proper instructions.
30+
This setup is not recommended for validators. If you plan to run a validator, refer to the [Running a Validator](/node-infrastructure/run-a-validator/onboarding-and-offboarding/set-up-validator/){target=\_blank} guide for proper instructions.
3131

3232
### Install and Build the Polkadot Binary
3333

@@ -58,10 +58,9 @@ This section will walk you through installing and building the Polkadot binary f
5858
You should see output similar to the following:
5959

6060
<div id="termynal" data-termynal>
61-
<span data-ty="input"
62-
><span class="file-path"></span>rustup show <br />
63-
rustup +nightly show</span
64-
>
61+
<span data-ty="input"><span class="file-path"></span>rustup show</span>
62+
<span data-ty>rustup +nightly show</span>
63+
<span data-ty></span>
6564
<span data-ty>active toolchain</span>
6665
<span data-ty>----------------</span>
6766
<span data-ty></span>
@@ -143,10 +142,8 @@ This section will walk you through installing and building the Polkadot binary f
143142
You should see output similar to the following:
144143

145144
<div id="termynal" data-termynal>
146-
<span data-ty="input"
147-
><span class="file-path"></span>rustup show <br />
148-
rustup +nightly show</span
149-
>
145+
<span data-ty="input"><span class="file-path"></span>rustup show</span>
146+
<span data-ty></span>
150147
<span data-ty>active toolchain</span>
151148
<span data-ty>----------------</span>
152149
<span data-ty></span>

.ai/pages/node-infrastructure-run-a-node-relay-chain-secure-wss.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,4 +122,4 @@ Apache2 can run in various modes, including `prefork`, `worker`, and `event`. In
122122
wss://example.com:443
123123
```
124124
125-
![A sync-in-progress chain connected to Polkadot.js UI](/images/nodes-and-validators/run-a-node/secure-wss/secure-wss-01.webp)
125+
![A sync-in-progress chain connected to Polkadot.js UI](/images/node-infrastructure/run-a-node/secure-wss/secure-wss-01.webp)

.ai/pages/node-infrastructure-run-a-validator-onboarding-and-offboarding-key-management.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ url: https://docs.polkadot.com/node-infrastructure/run-a-validator/onboarding-an
99

1010
## Introduction
1111

12-
After setting up your node environment as shown in the [Setup](/nodes-and-validators/run-a-validator/onboarding-and-offboarding/set-up-validator/){target=\_blank} section, you'll need to configure multiple keys for your validator to operate properly. This includes setting up session keys, which are essential for participating in the consensus process, and configuring a node key that maintains a stable network identity. This guide walks you through the key management process, showing you how to generate, store, and register these keys.
12+
After setting up your node environment as shown in the [Setup](/node-infrastructure/run-a-validator/onboarding-and-offboarding/set-up-validator/){target=\_blank} section, you'll need to configure multiple keys for your validator to operate properly. This includes setting up session keys, which are essential for participating in the consensus process, and configuring a node key that maintains a stable network identity. This guide walks you through the key management process, showing you how to generate, store, and register these keys.
1313

1414
## Set Session Keys
1515

@@ -30,7 +30,7 @@ There are multiple ways to create the session keys. It can be done by interactin
3030
3. Click the **Submit RPC Call** button.
3131
4. Copy the hex-encoded public key from the response.
3232

33-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/key-management/key-management-01.webp)
33+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/key-management/key-management-01.webp)
3434

3535
=== "Curl"
3636

@@ -89,7 +89,7 @@ Now that you have generated your session keys, you must submit them to the chain
8989
2. Select **Set Session Key** on the bonding account you generated earlier.
9090
3. Paste the hex-encoded session key string you generated (from either the UI or CLI) into the input field and submit the transaction.
9191

92-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/key-management/key-management-02.webp)
92+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/key-management/key-management-02.webp)
9393

9494
Once the transaction is signed and submitted, your session keys will be registered on-chain.
9595

.ai/pages/node-infrastructure-run-a-validator-onboarding-and-offboarding-set-up-validator.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@ Running a validator requires a commitment to maintaining a stable, secure infras
1717

1818
To get the most from this guide, ensure you've done the following before going forward:
1919

20-
- Read [Validator Requirements](/nodes-and-validators/run-a-validator/requirements/){target=\_blank} and understand the recommended minimum skill level and hardware needs.
21-
- Read [General Management](/nodes-and-validators/run-a-validator/operational-tasks/general-management/){target=\_blank}, [Upgrade Your Node](/nodes-and-validators/run-a-validator/operational-tasks/upgrade-your-node/){target=\_blank}, and [Pause Validating](/nodes-and-validators/run-a-validator/operational-tasks/pause-validating/){target=\_blank} and understand the tasks required to keep your validator operational.
22-
- Read [Rewards Payout](/nodes-and-validators/run-a-validator/staking-mechanics/rewards/){target=\_blank} and understand how validator rewards are determined and paid out.
23-
- Read [Offenses and Slashes](/nodes-and-validators/run-a-validator/staking-mechanics/offenses-and-slashes/){target=\_blank} and understand how validator performance and security can affect tokens staked by you or your nominators.
20+
- Read [Validator Requirements](/node-infrastructure/run-a-validator/requirements/){target=\_blank} and understand the recommended minimum skill level and hardware needs.
21+
- Read [General Management](/node-infrastructure/run-a-validator/operational-tasks/general-management/){target=\_blank}, [Upgrade Your Node](/node-infrastructure/run-a-validator/operational-tasks/upgrade-your-node/){target=\_blank}, and [Pause Validating](/node-infrastructure/run-a-validator/operational-tasks/pause-validating/){target=\_blank} and understand the tasks required to keep your validator operational.
22+
- Read [Rewards Payout](/node-infrastructure/run-a-validator/staking-mechanics/rewards/){target=\_blank} and understand how validator rewards are determined and paid out.
23+
- Read [Offenses and Slashes](/node-infrastructure/run-a-validator/staking-mechanics/offenses-and-slashes/){target=\_blank} and understand how validator performance and security can affect tokens staked by you or your nominators.
2424

2525
## Initial Setup
2626

.ai/pages/node-infrastructure-run-a-validator-onboarding-and-offboarding-start-validating.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ url: https://docs.polkadot.com/node-infrastructure/run-a-validator/onboarding-an
99

1010
## Introduction
1111

12-
After configuring your node keys as shown in the [Key Management](/nodes-and-validators/run-a-validator/onboarding-and-offboarding/key-management/){target=\_blank} section and ensuring your system is set up, you're ready to begin the validator setup process. This guide will walk you through choosing a network, synchronizing your node with the blockchain, bonding your DOT tokens, and starting your validator.
12+
After configuring your node keys as shown in the [Key Management](/node-infrastructure/run-a-validator/onboarding-and-offboarding/key-management/){target=\_blank} section and ensuring your system is set up, you're ready to begin the validator setup process. This guide will walk you through choosing a network, synchronizing your node with the blockchain, bonding your DOT tokens, and starting your validator.
1313

1414
## Choose a Network
1515

@@ -99,7 +99,7 @@ If you see terminal output similar to the preceding, and you are unable to synch
9999

100100
## Bond DOT
101101

102-
Once your validator node is synced, the next step is bonding DOT. A bonded account, or stash, holds your staked tokens (DOT) that back your validator node. Bonding your DOT means locking it for a period, during which it cannot be transferred or spent but is used to secure your validator's role in the network. Visit the [Minimum Bond Requirement](/nodes-and-validators/run-a-validator/requirements/#minimum-bond-requirement) section for details on how much DOT is required.
102+
Once your validator node is synced, the next step is bonding DOT. A bonded account, or stash, holds your staked tokens (DOT) that back your validator node. Bonding your DOT means locking it for a period, during which it cannot be transferred or spent but is used to secure your validator's role in the network. Visit the [Minimum Bond Requirement](/node-infrastructure/run-a-validator/requirements/#minimum-bond-requirement) section for details on how much DOT is required.
103103

104104
The following sections will guide you through bonding DOT for your validator.
105105

@@ -131,29 +131,29 @@ Follow these steps to use Polkadot.js Apps to activate your validator:
131131

132132
1. In Polkadot.js Apps, navigate to **Network** and select **Staking**:
133133

134-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-01.webp)
134+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-01.webp)
135135

136136
2. Open the **Accounts** tab and click on **+ Validator**:
137137

138-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-02.webp)
138+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-02.webp)
139139

140140
3. Set a bond amount in the **value bonded** field and then click **next**:
141141

142-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-03.webp)
142+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-03.webp)
143143

144144
4. Paste the hex output from `author_rotateKeys`, set the commission, allow or block new nominations, then click **Bond & Validate** to link your validator with its session keys.
145145

146-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-04.webp)
146+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-04.webp)
147147

148148
You can also set the **commission** and **blocked** nominations option via `staking.validate` extrinsic. By default, the blocked option is set to FALSE (i.e., the validator accepts nominations).
149149

150-
![](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-05.webp)
150+
![](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-05.webp)
151151

152152
### Monitor Validation Status and Slots
153153

154154
On the [**Staking**](https://polkadot.js.org/apps/#/staking){target=\_blank} tab in Polkadot.js Apps, you can see your validator's status, the number of available validator slots, and the nodes that have signaled their intent to validate. Your node may initially appear in the waiting queue, especially if the validator slots are full. The following is an example view of the **Staking** tab:
155155

156-
![staking queue](/images/nodes-and-validators/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-06.webp)
156+
![staking queue](/images/node-infrastructure/run-a-validator/onboarding-and-offboarding/start-validating/start-validating-06.webp)
157157

158158
The validator set refreshes each era. If there's an available slot in the next era, your node may be selected to move from the waiting queue to the active validator set, allowing it to start validating blocks. If your validator is not selected, it remains in the waiting queue. Increasing your stake or gaining more nominators may improve your chance of being selected in future eras.
159159
@@ -165,7 +165,7 @@ This following sections will walk you through creating and managing a systemd se
165165
166166
Ensure the following requirements are met before proceeding with the systemd setup:
167167
168-
- Confirm your system meets the [requirements](/nodes-and-validators/run-a-validator/requirements/){target=\_blank} for running a validator.
168+
- Confirm your system meets the [requirements](/node-infrastructure/run-a-validator/requirements/){target=\_blank} for running a validator.
169169
- Ensure you meet the [minimum bond requirements](https://wiki.polkadot.com/general/chain-state-values/#minimum-validator-bond){target=\_blank} for validating.
170170
- Verify the Polkadot binary is [installed](#install-the-polkadot-binaries).
171171

.ai/pages/node-infrastructure-run-a-validator-onboarding-and-offboarding-stop-validating.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The following are steps to ensure a smooth stop to validation:
2525

2626
When stepping back from validating, the first step is to chill your validator status. This action stops your validator from being considered for the next era without fully unbonding your tokens, which can be useful for temporary pauses like maintenance or planned downtime.
2727

28-
Use the `staking.chill` extrinsic to initiate this. For more guidance on chilling your node, refer to the [Pause Validating](/nodes-and-validators/run-a-validator/operational-tasks/pause-validating/){target=\_blank} guide. You may also claim any pending staking rewards at this point.
28+
Use the `staking.chill` extrinsic to initiate this. For more guidance on chilling your node, refer to the [Pause Validating](/node-infrastructure/run-a-validator/operational-tasks/pause-validating/){target=\_blank} guide. You may also claim any pending staking rewards at this point.
2929

3030
## Purge Validator Session Keys
3131

0 commit comments

Comments
 (0)