Skip to content

Commit 75f2841

Browse files
Update validator onboarding images and documentation (#979)
* Update validator onboarding images and documentation * fix: typo * fix: llms * docs: Update validator activation instructions in onboarding guide * fix: llms * docs: Update validator activation steps to include bond amount requirement * fix: llms * fix: start validating page * fix: last image * fix: llms * fix * fix: llms * fresh llms * llms check * fresh llms --------- Co-authored-by: DAWN KELLY <[email protected]>
1 parent d954fc7 commit 75f2841

File tree

11 files changed

+51
-88
lines changed

11 files changed

+51
-88
lines changed
166 KB
Loading
10.7 KB
Loading
7.89 KB
Loading
-138 KB
Loading
109 KB
Loading

infrastructure/running-a-validator/onboarding-and-offboarding/start-validating.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -100,35 +100,36 @@ Once your validator node is fully synced and ready, the next step is to ensure i
100100
101101
To confirm that your validator is live and synchronized with the Polkadot network, visit the [Telemetry](https://telemetry.polkadot.io/#list/Polkadot%20CC1){target=\_blank} page. Telemetry provides real-time information on node performance and can help you check if your validator is connected properly. Search for your node by name. You can search all nodes currently active on the network, which is why you should use a unique name for easy recognition. Now, confirm that your node is fully synced by comparing the block height of your node with the network's latest block. Nodes that are fully synced will appear white in the list, while nodes that are not yet fully synced will appear gray.
102102

103-
In the following example, a node named `techedtest` is successfully located and synchronized, ensuring it's prepared to participate in the network:
104-
105-
![Polkadot telemetry dashboard](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-01.webp)
106103

107104
### Activate using Polkadot.js Apps
108105

109106
Follow these steps to use Polkadot.js Apps to activate your validator:
110107

111-
1. Go to the **Validator** tab in the Polkadot.js Apps UI and locate the section where you input the keys generated from `rotateKeys`. Paste the output from `author_rotateKeys`, which is a hex-encoded key that links your validator with its session keys:
108+
1. In Polkadot.js Apps, navigate to **Network** and select **Staking**:
112109

113-
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-02.webp)
110+
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-01.webp)
114111

115-
2. Set a reward commission percentage if desired. You can set a percentage of the rewards to pay to your validator and the remainder pays to your nominators. A 100% commission rate indicates the validator intends to keep all rewards and is seen as a signal the validator is not seeking nominators.
112+
2. Open the **Accounts** tab and click on **+ Validator**:
116113

117-
3. Toggle the **allows new nominations** option if your validator is open to more nominations from DOT holders.
114+
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-02.webp)
118115

119-
4. Once everything is configured, select **Bond & Validate** to activate your validator status.
116+
3. Set a bond amount in the **value bonded** field and then click **next**:
120117

121118
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-03.webp)
122119

123-
5. Edit the **commission** and the **blocked** option via `staking.validate` extrinsic. By default, the blocked option is set to FALSE (i.e., the validator accepts nominations).
120+
4. **Set session keys**. Paste the output from `author_rotateKeys` (hex-encoded) to link your validator with its session keys. Then click **Bond & Validate** to continue:
124121

125122
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-04.webp)
126123

124+
You can set the **commission** and the **blocked** option via `staking.validate` extrinsic. By default, the blocked option is set to FALSE (i.e., the validator accepts nominations):
125+
126+
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-05.webp)
127+
127128
### Monitor Validation Status and Slots
128129

129130
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:
130131

131-
![staking queue](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-05.webp)
132+
![staking queue](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-06.webp)
132133

133134
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.
134135

llms-files/llms-dapps.txt

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -512,7 +512,7 @@ categories: Tooling, Dapps
512512

513513
Polkadart is the most comprehensive Dart/Flutter SDK for interacting with Polkadot, Substrate, and other compatible blockchain networks. Designed with a Dart-first approach and type-safe APIs, it provides everything developers need to build powerful decentralized applications.
514514

515-
This page will outline some of the core components of Polkadart. Fore more details, refer to the [official documentation](https://polkadart.dev){target=\_blank}.
515+
This page will outline some of the core components of Polkadart. For more details, refer to the [official documentation](https://polkadart.dev){target=\_blank}.
516516

517517
## Installation
518518

@@ -532,7 +532,7 @@ Add Polkadart to your `pubspec.yaml`:
532532

533533
For type-safe API generation, add the following to your `pubspec.yaml`:
534534

535-
```yaml
535+
```yaml title="pubspec.yaml"
536536
polkadart:
537537
output_dir: lib/generated
538538
chains:
@@ -543,7 +543,7 @@ polkadart:
543543

544544
## Get Started
545545

546-
## Type Generation
546+
### Type Generation
547547

548548
Polkadart provides a CLI tool to generate type definitions from any Polkadot-SDK compatible blockchain network. This allows you to build type-safe Dart applications without dealing with the low-level details of the blockchain.
549549

@@ -575,7 +575,6 @@ print('Balance: ${accountInfo.data.free}')
575575

576576
An API instance is required to interact with the blockchain. Polkadart provides a `Provider` class that allows you to connect to any network.
577577

578-
#### Polkadot
579578
```dart
580579
import 'package:demo/generated/polkadot/polkadot.dart';
581580
import 'package:polkadart/provider.dart';
@@ -588,7 +587,7 @@ Future<void> main(List<String> arguments) async {
588587

589588
### Reading Chain Data
590589

591-
Besides querying the data using the `query` from the generated API, you can also use the State API for querying storage data, metadata, runtime information, and others.
590+
Besides querying the data using the `query` from the generated API, you can also use the State API for querying storage data, metadata, runtime information, and other chain information.
592591

593592
```dart
594593
final stateApi = StateApi(provider);
@@ -616,7 +615,7 @@ subscription.stream.forEach((response) {
616615

617616
### Send a Transaction
618617

619-
Perhaps the most common operation done in any blockchain is transferring funds. Here you can see how that can be done using Polkadart.
618+
Perhaps the most common operation done in any blockchain is transferring funds. Here you can see how that can be done using Polkadart:
620619

621620
```dart
622621
final wallet = await KeyPair.sr25519.fromUri("//Alice");
@@ -667,7 +666,7 @@ await author.submitAndWatchExtrinsic(extrinsic, (data) {
667666

668667
## Where to Go Next
669668

670-
To dive deeper into Polkadart refer to the [official Polkadart documentation](https://polkadart.dev){target=\_blank}. They provide comprehensive guides for common use-cases and advanced usage.
669+
To dive deeper into Polkadart, refer to the [official Polkadart documentation](https://polkadart.dev/){target=\_blank}, where you can find comprehensive guides for common use cases and advanced usage.
671670
--- END CONTENT ---
672671

673672
Doc-Content: https://docs.polkadot.com/develop/toolkit/api-libraries/polkadot-js-api/

llms-files/llms-infrastructure.txt

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1140,35 +1140,36 @@ Once your validator node is fully synced and ready, the next step is to ensure i
11401140

11411141
To confirm that your validator is live and synchronized with the Polkadot network, visit the [Telemetry](https://telemetry.polkadot.io/#list/Polkadot%20CC1){target=\_blank} page. Telemetry provides real-time information on node performance and can help you check if your validator is connected properly. Search for your node by name. You can search all nodes currently active on the network, which is why you should use a unique name for easy recognition. Now, confirm that your node is fully synced by comparing the block height of your node with the network's latest block. Nodes that are fully synced will appear white in the list, while nodes that are not yet fully synced will appear gray.
11421142

1143-
In the following example, a node named `techedtest` is successfully located and synchronized, ensuring it's prepared to participate in the network:
1144-
1145-
![Polkadot telemetry dashboard](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-01.webp)
11461143

11471144
### Activate using Polkadot.js Apps
11481145

11491146
Follow these steps to use Polkadot.js Apps to activate your validator:
11501147

1151-
1. Go to the **Validator** tab in the Polkadot.js Apps UI and locate the section where you input the keys generated from `rotateKeys`. Paste the output from `author_rotateKeys`, which is a hex-encoded key that links your validator with its session keys:
1148+
1. In Polkadot.js Apps, navigate to **Network** and select **Staking**:
11521149

1153-
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-02.webp)
1150+
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-01.webp)
11541151

1155-
2. Set a reward commission percentage if desired. You can set a percentage of the rewards to pay to your validator and the remainder pays to your nominators. A 100% commission rate indicates the validator intends to keep all rewards and is seen as a signal the validator is not seeking nominators.
1152+
2. Open the **Accounts** tab and click on **+ Validator**:
11561153

1157-
3. Toggle the **allows new nominations** option if your validator is open to more nominations from DOT holders.
1154+
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-02.webp)
11581155

1159-
4. Once everything is configured, select **Bond & Validate** to activate your validator status.
1156+
3. Set a bond amount in the **value bonded** field and then click **next**:
11601157

11611158
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-03.webp)
11621159

1163-
5. Edit the **commission** and the **blocked** option via `staking.validate` extrinsic. By default, the blocked option is set to FALSE (i.e., the validator accepts nominations).
1160+
4. **Set session keys**. Paste the output from `author_rotateKeys` (hex-encoded) to link your validator with its session keys. Then click **Bond & Validate** to continue:
11641161

11651162
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-04.webp)
11661163

1164+
You can set the **commission** and the **blocked** option via `staking.validate` extrinsic. By default, the blocked option is set to FALSE (i.e., the validator accepts nominations):
1165+
1166+
![](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-05.webp)
1167+
11671168
### Monitor Validation Status and Slots
11681169

11691170
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:
11701171

1171-
![staking queue](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-05.webp)
1172+
![staking queue](/images/infrastructure/running-a-validator/onboarding-and-offboarding/start-validating/start-validating-06.webp)
11721173

11731174
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.
11741175

llms-files/llms-tooling.txt

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4223,7 +4223,7 @@ categories: Tooling, Dapps
42234223

42244224
Polkadart is the most comprehensive Dart/Flutter SDK for interacting with Polkadot, Substrate, and other compatible blockchain networks. Designed with a Dart-first approach and type-safe APIs, it provides everything developers need to build powerful decentralized applications.
42254225

4226-
This page will outline some of the core components of Polkadart. Fore more details, refer to the [official documentation](https://polkadart.dev){target=\_blank}.
4226+
This page will outline some of the core components of Polkadart. For more details, refer to the [official documentation](https://polkadart.dev){target=\_blank}.
42274227

42284228
## Installation
42294229

@@ -4243,7 +4243,7 @@ Add Polkadart to your `pubspec.yaml`:
42434243

42444244
For type-safe API generation, add the following to your `pubspec.yaml`:
42454245

4246-
```yaml
4246+
```yaml title="pubspec.yaml"
42474247
polkadart:
42484248
output_dir: lib/generated
42494249
chains:
@@ -4254,7 +4254,7 @@ polkadart:
42544254

42554255
## Get Started
42564256

4257-
## Type Generation
4257+
### Type Generation
42584258

42594259
Polkadart provides a CLI tool to generate type definitions from any Polkadot-SDK compatible blockchain network. This allows you to build type-safe Dart applications without dealing with the low-level details of the blockchain.
42604260

@@ -4286,7 +4286,6 @@ print('Balance: ${accountInfo.data.free}')
42864286

42874287
An API instance is required to interact with the blockchain. Polkadart provides a `Provider` class that allows you to connect to any network.
42884288

4289-
#### Polkadot
42904289
```dart
42914290
import 'package:demo/generated/polkadot/polkadot.dart';
42924291
import 'package:polkadart/provider.dart';
@@ -4299,7 +4298,7 @@ Future<void> main(List<String> arguments) async {
42994298

43004299
### Reading Chain Data
43014300

4302-
Besides querying the data using the `query` from the generated API, you can also use the State API for querying storage data, metadata, runtime information, and others.
4301+
Besides querying the data using the `query` from the generated API, you can also use the State API for querying storage data, metadata, runtime information, and other chain information.
43034302

43044303
```dart
43054304
final stateApi = StateApi(provider);
@@ -4327,7 +4326,7 @@ subscription.stream.forEach((response) {
43274326

43284327
### Send a Transaction
43294328

4330-
Perhaps the most common operation done in any blockchain is transferring funds. Here you can see how that can be done using Polkadart.
4329+
Perhaps the most common operation done in any blockchain is transferring funds. Here you can see how that can be done using Polkadart:
43314330

43324331
```dart
43334332
final wallet = await KeyPair.sr25519.fromUri("//Alice");
@@ -4378,7 +4377,7 @@ await author.submitAndWatchExtrinsic(extrinsic, (data) {
43784377

43794378
## Where to Go Next
43804379

4381-
To dive deeper into Polkadart refer to the [official Polkadart documentation](https://polkadart.dev){target=\_blank}. They provide comprehensive guides for common use-cases and advanced usage.
4380+
To dive deeper into Polkadart, refer to the [official Polkadart documentation](https://polkadart.dev/){target=\_blank}, where you can find comprehensive guides for common use cases and advanced usage.
43824381
--- END CONTENT ---
43834382

43844383
Doc-Content: https://docs.polkadot.com/develop/toolkit/api-libraries/polkadot-js-api/

0 commit comments

Comments
 (0)