Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Signed-off-by: Ashutosh Tripathi <39340292+ashucoder9@users.noreply.github.com>
  • Loading branch information
ashucoder9 authored Nov 28, 2024
1 parent fa08045 commit b53303f
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -356,9 +356,9 @@ To get your new Avalanche L1 information, visit the [Avalanche L1 Explorer](http
Add a Validator[​](#add-a-validator "Direct link to heading")
-------------------------------------------------------------

Before proceeding to add a validator to our Avalanche L1, we will need to have the validator's NodeID, BLS public key and proof of possession. These can be obtained by ssh into the node itself and run the `getNodeID` API specified [here](https://docs.avax.network/api-reference/info-api#infogetnodeid)
Before proceeding to add a validator to our Avalanche L1, we will need to have the validator's NodeID, BLS public key and proof of possession. These can be obtained by ssh into the node itself and run the `getNodeID` API specified [here](/api-reference/info-api#infogetnodeid).

To add a validator to an Avalanche L1, the owner of the key that acts as the controller of ValidatorManager contract specified in `avalanche blockchain create` command above run:
To add a validator to an Avalanche L1, the owner of the key that acts as the controller of `ValidatorManager` contract specified in `avalanche blockchain create` command above run:

```bash
avalanche blockchain addValidator testblockchain
Expand Down Expand Up @@ -415,7 +415,7 @@ Next, select a key that can remove the validator:
▸ mytestkey
```

By the end of the command, you would have successfully added a new validator on the given Avalanche L1 on `Fuji`!
By the end of the command, you would have successfully added a new validator to the Avalanche L1 on Fuji Testnet!

Appendix[​](#appendix "Direct link to heading")
-----------------------------------------------
Expand Down

0 comments on commit b53303f

Please sign in to comment.