diff --git a/.github/styles/config/vocabularies/Ronin/accept.txt b/.github/styles/config/vocabularies/Ronin/accept.txt
index 21f6e41..5f013c8 100644
--- a/.github/styles/config/vocabularies/Ronin/accept.txt
+++ b/.github/styles/config/vocabularies/Ronin/accept.txt
@@ -13,7 +13,6 @@ mainnet
NFT
node
node operator
-non-validator node
OIDC
OpenID Connect
RON
diff --git a/README.md b/README.md
index fad3882..e348846 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,7 @@ Install the general dependencies:
1. Clone this repository to create its copy on your local computer:
```bash
- git clone git@github.com:axieinfinity/ronin-documentation.git
+ git clone git@github.com:ronin-chain/ronin-documentation.git
```
2. Navigate to the `ronin-documentation` directory:
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index 8ee643f..a440c44 100644
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -454,7 +454,7 @@ the concepts covered in this topic.
* [Slashing rules](./validators/slashing.mdx)
* [Rewards](./basics/rewards.md)
-* [Nodes](./basics/nodes.md)
+* [Nodes](./basics/nodes.mdx)
* Explanation topics within another page: [Bailout](./validators/slashing.mdx#bailout)
#### How-to guide
@@ -522,7 +522,7 @@ this task and the concepts that it involves.
##### Examples of how-to guides
* [Stake RON](./delegators/onboarding/become-delegator.mdx)
-* [Run a validator node](./validators/setup/mainnet/run-validator.md)
+* [Run a validator node](./validators/setup/mainnet/run-validator.mdx)
* [Claim rewards](./validators/manage/claim-rewards.mdx)
* Task topics within other pages:
* [Check your credit score](./validators/slashing.mdx#check-your-credit-score)
diff --git a/docs/basics/contribute/style-guide.md b/docs/basics/contribute/style-guide.md
index 608aae9..fd0d947 100644
--- a/docs/basics/contribute/style-guide.md
+++ b/docs/basics/contribute/style-guide.md
@@ -28,13 +28,12 @@ terms and their usage.
| bridge operator | A bridge operator is a type of node used for acknowledging events on Ronin Bridge. |
| bridge node | Each validator is expected to run two nodes—a validator node and a bridge node node. |
| delegator | To become a delegator, go to **RON Staking > All validators > Delegate**. |
-| full node | Validator and non-validator are considered _full_ nodes—they store full blockchain data. |
+| full node | Validator node and RPC node are considered _full_ nodes—they store full blockchain data. |
| Governing Validator | Beside the 12 Governing Validators, top 10 Validator Candidates with the highest staked amount are selected as Standard Validators. |
| Katana | Katana, also known as the Katana DEX, is a decentralized exchange for Ronin. |
| mainnet | To run a node on the mainnet, make sure to comply with the minimum hardware requirements. |
| node | Each validator is expected to run two nodes—a validator node and a bridge node. |
| node operator | A node operator is an individual or institution that sets up and configure nodes for the validator. |
-| non-validator node | A non-validator node is also known as an RPC node. |
| RON | Deposit 50 RON to your bridge address. |
| RON Staking | RON Staking is an app where token holders can choose validators. |
| Ronin | Ronin is an EVM blockchain forged for gaming. |
diff --git a/docs/basics/key-concepts.md b/docs/basics/key-concepts.mdx
similarity index 98%
rename from docs/basics/key-concepts.md
rename to docs/basics/key-concepts.mdx
index ea3a8e3..14eb7c6 100644
--- a/docs/basics/key-concepts.md
+++ b/docs/basics/key-concepts.mdx
@@ -41,7 +41,7 @@ Boneh-Lynn-Shacham (BLS) is a digital signature method used for verifying the au
The BLS key is what the validator uses to produce finality votes. Validators who produce finality vote receive a reward. If a validator fails to produce a finality vote, no slashing penalty applies.
-To attach a BLS key to a validator, either a new validator must be created or an existing validator must be [updated](./../validators/setup/generate-keys.md) with this key.
+To attach a BLS key to a validator, either a new validator must be created or an existing validator must be [updated](./../validators/setup/generate-keys.mdx) with this key.
### Bridge
@@ -103,6 +103,10 @@ A delegator is a RON token holder—an individual or institution—who contribut
## E
+### ECDSA key
+
+An Elliptic Curve Digital Signature Algorithm (ECDSA) key is a cryptographic key used to secure transactions on the blockchain and are generated by the validator to sign blocks. You need this key to run a validator node on Ronin.
+
### Epoch
While this varies depending on the blockchain protocol, an epoch generally refers to a specific number of blocks—or a specific or approximate period of time. Generally found on blockchains that utilize Proof of Stake (PoS), different PoS protocols have different ways of defining an epoch (if they use them). Epochs are used to reach security checkpoints, distribute the staking reward, or assign a new group of blockchain validators. For example, an epoch on Ronin lasts 200 blocks, which is roughly equal to 10 minutes.
@@ -157,11 +161,11 @@ On Ronin, the node types are as follows:
* Ronin node
* Full node
* Validator node
- * Non-validator node
+ * RPC node
* Archive node
* Bridge node
-For more information about nodes, see [Nodes](nodes.md).
+For more information about nodes, see [Nodes](nodes.mdx).
## P
diff --git a/docs/basics/nodes.md b/docs/basics/nodes.mdx
similarity index 55%
rename from docs/basics/nodes.md
rename to docs/basics/nodes.mdx
index 2c6bee2..8f11d32 100644
--- a/docs/basics/nodes.md
+++ b/docs/basics/nodes.mdx
@@ -3,14 +3,17 @@ description: Learn about the different types of nodes you can run.
title: Nodes
---
+import DocCardList from '@theme/DocCardList';
+import {findSidebarItem} from '@site/src/sidebarUtils';
+
## Overview
There are two types of nodes on Ronin:
* Ronin node:
- * Non-validator node
* Validator node
* Archive node
+ * RPC node
* Bridge node
The following section describes each type in detail.
@@ -21,16 +24,42 @@ A Ronin node ([GitHub](https://github.com/axieinfinity/ronin)) is the building b
The Ronin node can be configured in three different ways depending on the purpose:
-* A *non-validator node* doesn’t conduct consensus, but simply connects to the network, synchronizes ledger state, and observes the status of the network. For example, a non-validator node can serve as a gateway for decentralized applications to query the Ronin blockchain for information, send transactions, and execute smart contracts. A non-validator Ronin
* A *validator node* is what most people think of as a node. These nodes are responsible for verifying and approving transactions
submitted by users and blockchain clients. Upon the close of a transaction block, validator nodes are randomly chosen to validate block data, thus generating the
subsequent block, and earning RON tokens as a reward. These are the nodes that are listed on the [RON Staking](https://app.roninchain.com/staking) app.
* An *archive node* retains all historical data right back to genesis and is suited for making fast queries about historical states. This data represents units of terabytes, which makes archive nodes less attractive for average users but can be handy for services like block explorers, wallet vendors, and chain analytics.
+* An *RPC node* doesn’t conduct consensus, but simply connects to the network, synchronizes ledger state, and observes the status of the network. For example, this node can serve as a gateway for dApps to query the Ronin blockchain for information, send transactions, and execute smart contracts.
-Validator and non-validator are considered *full* nodes—they store full blockchain data, which is periodically pruned so the node does not store all state data back to genesis. The archive node, on the other hand, stores all of the information that a full node does but also builds an archive of historical states all the way back to genesis.
+Validator and RPC nodes are considered *full* nodes—they store full blockchain data, which is periodically pruned so the node does not store all state data back to genesis. The archive node, on the other hand, stores all of the information that a full node does but also builds an archive of historical states all the way back to genesis.
A validator node starts its life as a full node, but has also “registered” itself to the network as a validator, which means that it may now accept RON token stake and potentially be included in the validator set that conduct network consensus.
+### Run a validator node
+
+
+
+### Run an RPC node
+
+
+
## What is a bridge node?
A *bridge node* ([GitHub](https://github.com/axieinfinity/bridge-v2)) is a type of node used for acknowledging deposit and withdrawal events on Ronin Bridge—the blockchain bridge that facilitates asset transfers between Ronin and Ethereum.
+
+### Run a bridge node
+
+
diff --git a/docs/bridge-operators/setup/overview.md b/docs/bridge-operators/setup/overview.md
index 4c45aca..3e0d06b 100644
--- a/docs/bridge-operators/setup/overview.md
+++ b/docs/bridge-operators/setup/overview.md
@@ -15,9 +15,9 @@ Bridge nodes are run by a fixed set of bridge operators selected by Sky Mavis an
We offer two different methods of installing the bridge:
-* Using Docker: if you're familiar with Docker, install and run the bridge as a Docker instance. For instructions, see [Run a bridge node](run-bridge.md).
+* Using Docker: if you're familiar with Docker, install and run the bridge as a Docker instance. For instructions, see [Run a bridge node](run-bridge.mdx).
* Manually: if you're more comfortable using the command line, compile your own bridge binary from the [source code on GitHub](https://github.com/axieinfinity/bridge-v2?tab=readme-ov-file#manually).
## Node upgrade
-Keep the node's software up-to-date by upgrading to the latest version as described in [Upgrade bridge software](upgrade-bridge.md).
+Keep the node's software up-to-date by upgrading to the latest version as described in [Upgrade bridge software](upgrade-bridge.mdx).
diff --git a/docs/bridge-operators/setup/run-bridge.md b/docs/bridge-operators/setup/run-bridge.mdx
similarity index 99%
rename from docs/bridge-operators/setup/run-bridge.md
rename to docs/bridge-operators/setup/run-bridge.mdx
index dd7aa76..53ac780 100644
--- a/docs/bridge-operators/setup/run-bridge.md
+++ b/docs/bridge-operators/setup/run-bridge.mdx
@@ -30,9 +30,9 @@ Have two RPC endpoints ready:
### Private key
-Generate a private key for operating the bridge node. For instructions, see [Generate keys](./../../validators/setup/generate-keys.md).
+Generate a private key for operating the bridge node. For instructions, see [Generate keys](./../../validators/setup/generate-keys.mdx).
-## Run the node
+## Steps
1. Set up a directory for the bridge and two nested directories for its data and the Docker configuration:
diff --git a/docs/bridge-operators/setup/upgrade-bridge.md b/docs/bridge-operators/setup/upgrade-bridge.mdx
similarity index 100%
rename from docs/bridge-operators/setup/upgrade-bridge.md
rename to docs/bridge-operators/setup/upgrade-bridge.mdx
diff --git a/docs/get-started.mdx b/docs/get-started.mdx
index 0fa00a4..18afb0f 100644
--- a/docs/get-started.mdx
+++ b/docs/get-started.mdx
@@ -60,6 +60,15 @@ Run a validator node, claim rewards, and manage your account.
findSidebarItem('/validators/validator-faq'),
]} />
+## Run an RPC node
+
+Run an RPC (non-validator) node.
+
+
+
## Run a bridge node
Run a bridge node, propose and vote on changes to the bridge.
diff --git a/docs/validators/setup/mainnet/run-non-validator.md b/docs/rpc/mainnet-rpc.mdx
similarity index 83%
rename from docs/validators/setup/mainnet/run-non-validator.md
rename to docs/rpc/mainnet-rpc.mdx
index 4c25578..61cfe4b 100644
--- a/docs/validators/setup/mainnet/run-non-validator.md
+++ b/docs/rpc/mainnet-rpc.mdx
@@ -1,24 +1,22 @@
---
-description: Install a mainnet non-validator node using Docker.
-title: Run a non-validator node
+description: Set up and run an RPC node (non-validator node) on the Ronin mainnet using Docker.
+title: Run a mainnet RPC node
tags:
- docker-mainnet
---
## Overview
-This guide demonstrates how to run a non-validator node on the mainnet
-using Docker. A non-validator node is also known as an RPC (remote
-procedure call) node.
+This guide demonstrates how to run an RPC node (non-validator node) on the Ronin mainnet using Docker.
-## Before you start
+## Prerequisites
Install Docker Engine and the Docker Compose plugin:
* [Docker Engine](https://docs.docker.com/engine/)
* [Docker Compose](https://docs.docker.com/compose/)
-## Run the node
+## Steps
1. Set up directories:
@@ -85,10 +83,10 @@ Install Docker Engine and the Docker Compose plugin:
CHAIN_STATS_WS_SECRET=WSyDMrhRBe111
CHAIN_STATS_WS_SERVER=ronin-stats-ws.roninchain.com
- RONIN_PARAMS=--http.api eth,net,web3,consortium --txpool.pricelimit 20000000000 --txpool.nolocals --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
+ RONIN_PARAMS=--http.api eth,net,web3,consortium --txpool.pricelimit 20000000000 --txpool.nolocals --cache 4096 --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
```
-4. (Optional) Download the snapshot from the [ronin-snapshot](https://github.com/axieinfinity/ronin-snapshot) repo:
+4. (Optional) Download the snapshot from the [ronin-snapshot](https://github.com/axieinfinity/ronin-snapshot) repo, preferably using PebbleDB:
```bash
cd ~/ronin/chaindata/data/ronin/
@@ -98,7 +96,7 @@ Install Docker Engine and the Docker Compose plugin:
5. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image and starts the service you defined.
diff --git a/docs/validators/setup/testnet/run-non-validator.md b/docs/rpc/testnet-rpc.mdx
similarity index 90%
rename from docs/validators/setup/testnet/run-non-validator.md
rename to docs/rpc/testnet-rpc.mdx
index a68dd74..987c45b 100644
--- a/docs/validators/setup/testnet/run-non-validator.md
+++ b/docs/rpc/testnet-rpc.mdx
@@ -1,15 +1,13 @@
---
-description: Install a testnet non-validator node using Docker.
-title: Run a non-validator node
+description: Set up and run an RPC node (non-validator node) on the Saigon testnet using Docker.
+title: Run a testnet RPC node
tags:
- docker-testnet
---
## Overview
-This guide demonstrates how to run a non-validator node on the Saigon
-testnet using Docker. A non-validator node is also known as an RPC
-(remote procedure call) node.
+This guide demonstrates how to run an RPC node (non-validator node) on the Saigon testnet using Docker.
## Prerequisites
@@ -18,7 +16,7 @@ Install Docker Engine and the Docker Compose plugin:
* [Docker Engine](https://docs.docker.com/engine/)
* [Docker Compose](https://docs.docker.com/compose/)
-## Run the node
+## Steps
1. Set up directories:
@@ -103,7 +101,7 @@ Install Docker Engine and the Docker Compose plugin:
5. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image and starts the service you defined.
diff --git a/docs/validators/index.mdx b/docs/validators/index.mdx
index 8a0da90..b177296 100644
--- a/docs/validators/index.mdx
+++ b/docs/validators/index.mdx
@@ -13,7 +13,6 @@ Run a node on the Ronin mainnet:
@@ -21,7 +20,6 @@ Run a node on the Saigon testnet:
diff --git a/docs/validators/manage/assets/add-finality-key-1.png b/docs/validators/manage/assets/add-finality-key-1.png
index 0f19a45..2e4a0b8 100644
Binary files a/docs/validators/manage/assets/add-finality-key-1.png and b/docs/validators/manage/assets/add-finality-key-1.png differ
diff --git a/docs/validators/manage/assets/add-finality-key-2.png b/docs/validators/manage/assets/add-finality-key-2.png
index 3f9d8db..1ce11df 100644
Binary files a/docs/validators/manage/assets/add-finality-key-2.png and b/docs/validators/manage/assets/add-finality-key-2.png differ
diff --git a/docs/validators/manage/assets/edit-finality-key-1.png b/docs/validators/manage/assets/edit-finality-key-1.png
deleted file mode 100644
index cb71ff9..0000000
Binary files a/docs/validators/manage/assets/edit-finality-key-1.png and /dev/null differ
diff --git a/docs/validators/manage/assets/edit-finality-key-2.png b/docs/validators/manage/assets/edit-finality-key-2.png
deleted file mode 100644
index 04291f1..0000000
Binary files a/docs/validators/manage/assets/edit-finality-key-2.png and /dev/null differ
diff --git a/docs/validators/manage/assets/profile.png b/docs/validators/manage/assets/profile.png
index a33b7c9..bf433f1 100644
Binary files a/docs/validators/manage/assets/profile.png and b/docs/validators/manage/assets/profile.png differ
diff --git a/docs/validators/manage/finality.mdx b/docs/validators/manage/finality.mdx
index 2e0b198..a05a805 100644
--- a/docs/validators/manage/finality.mdx
+++ b/docs/validators/manage/finality.mdx
@@ -6,20 +6,20 @@ title: Add or change finality vote key
import profile from './assets/profile.png';
import addStepOne from './assets/add-finality-key-1.png';
import addStepTwo from './assets/add-finality-key-2.png';
-import editStepOne from './assets/edit-finality-key-1.png';
-import editStepTwo from './assets/edit-finality-key-2.png';
## Overview
-This guide demonstrates how to add a *finality vote key* to your profile. The finality vote key is used to vote for blocks in the [fast finality mechanism](https://github.com/axieinfinity/REPs/blob/main/REP-0003.md#rewards). If you're an active Ronin validator, you need to have this key added in order to have the fast finality rewards transferred to your admin address by the end of the day.
+This guide demonstrates how to add a *finality vote key* to your profile. The finality vote key is used to vote for blocks in the [fast finality mechanism](https://github.com/axieinfinity/REPs/blob/main/REP-0003.md#rewards). If you're an active Ronin validator, you need to have this key added to have the fast finality rewards transferred to your admin address by the end of the day.
## Prerequisites
### Generate a BLS key pair
-Before you add a finality vote key, you need to generate a BLS key pair. The BLS key pair consists of a private key and a public key. The public BLS key is your finality vote key. For more information, see the [Generate BLS key pair](./../setup/generate-keys.md) guide.
+Before you add a finality vote key, you need to generate a BLS key pair. The BLS key pair consists of a private key and a public key. The public BLS key is your finality vote key. For more information, see the [Generate BLS key pair](./../setup/generate-keys.mdx) guide.
-### Generate proof of possession
+## Steps
+
+### Step 1. Generate proof of possession
To prove that you own the finality vote key, you need to generate a proof of possession. The proof of possession is a signature of the public key using the private key.
There are two ways to generate the proof of possession: using the Ronin CLI or using the Docker image.
@@ -70,12 +70,14 @@ BLS public key #0: {redacted}
BLS proof #0: {redacted}
```
-## Add a finality vote key {#add}
+### Step 2. Add or change your finality vote key
+
+**Note**: The keys you generated do not have the `0x` prefix. Before submitting the form, make sure to add the `0x` prefix to the keys.
1. Open the [Validator Dashboard](https://validator.roninchain.com), then go to your account, and then click **My profile**.
-2. In the **Finality Vote Key** field, click **Add key**.
+2. In the **Finality Vote Key** field, click **Add key** or the edit icon.
3. Paste your BLS public key and the proof of possession.
@@ -83,19 +85,6 @@ BLS proof #0: {redacted}
4. Save the change and confirm the transaction.
-## Change your finality vote key {#change}
-
-1. Open the Validator Dashboard, then go to your account, and then click **My profile**.
-
-
-2. In the **Finality Vote Key** field, click the edit icon.
-
-
-3. Paste your new BLS public key and the proof of possession.
-
-
-4. Save the change and confirm the transaction.
-
:::info[Cooldown period]
-After changing your admin address or fast finality vote key, there's a 24-hour cooldown period. During this time, you won't be able to modify either value until 24 hours after the last change.
-:::
\ No newline at end of file
+After changing your admin address or fast finality vote key, there's a 24-hour cooldown period. During this time, you won't be able to modify either value.
+:::
diff --git a/docs/validators/onboarding/become-validator.mdx b/docs/validators/onboarding/become-validator.mdx
index 0fa88c8..044c421 100644
--- a/docs/validators/onboarding/become-validator.mdx
+++ b/docs/validators/onboarding/become-validator.mdx
@@ -17,24 +17,22 @@ After following the steps in this guide, you'll become a
Validator Candidate and have a chance to be selected as a
Standard Validator on the next day.
-### Validator roles
+### Validator responsibilities and rewards
+
+Ronin Validators share the critical responsibility of ensuring the integrity of all onchain transactions. That means they produce blocks and vote for finality. Ronin has allocated a total of [180M RON](./../../basics/rewards.md) over 8 years to reward Validators for these contributions, and Validators also receive a percentage of Ronin transaction fees.
+
+The rewards are divided into two parts: 85% for finality voting and 15% for block production. All validators vote for finality, but only 22 validators are selected produce blocks in a given epoch.
+These 22 validators include 12 Governing Validators, elected by the community to ensure network security, and 10 Rotating Validators selected randomly. The probability of being chosen as a Rotating Validator is proportional to the amount of stake held by each validator
+
+After receiving rewards, validators then re-distribute a small percentage to Delegators according to a commission rate, which can range from 5% to 20%.
+
-There are three validator roles:
-* **Validator Candidate:** the role you get after following the steps
-in this guide. Validator Candidates are eligible to be selected as Standard Validators the next day.
-* **Standard Validator:** every day, at least 10 Validator Candidates
-with the highest stakes are selected as Standard Validators.
-The system records your total staking amount at 00:00 UTC every day
-for the selection process.
-* **Governing Validator:** the validators chosen by the community and
-Sky Mavis to ensure network security. Governing Validators are
-validators by default, and they account for more than half of the
-total validator set.
## Prerequisites
-Have at least 250,000 RON for the initial stake in your Ronin Wallet. For information on how to buy RON, see [Acquire RON](./../../basics/acquire-ron.mdx).
+Have at least 250,000 RON for the initial stake in your Ronin address. For information on how to buy RON, see [Acquire RON](./../../basics/acquire-ron.mdx).
+**Note: An address applying to become a validator must not have participated in staking previously, either as a validator or a delegator.**
## Steps
@@ -48,7 +46,8 @@ It's also highly recommended that you read the
-4. Fill in your addresses, the commission rate, the fast finality vote key, and the proof of possession. For more information, see [Add or change finality vote key](../manage/finality.mdx).
+4. Fill in your addresses, the commission rate, the fast finality vote key, and the proof of possession. For more information, see [Add or change finality vote key](../manage/finality.mdx). **Note:** The tool generating the keys produces them without the `0x` prefix. Before submitting the form, make sure to add the `0x` prefix to the keys.
+
5. Provide the initial stake of 250,000 RON from your connected Ronin Wallet.
diff --git a/docs/validators/setup/assets/extension.png b/docs/validators/setup/assets/extension.png
deleted file mode 100644
index 8ea12ec..0000000
Binary files a/docs/validators/setup/assets/extension.png and /dev/null differ
diff --git a/docs/validators/setup/assets/mobile.png b/docs/validators/setup/assets/mobile.png
deleted file mode 100644
index 0fbe877..0000000
Binary files a/docs/validators/setup/assets/mobile.png and /dev/null differ
diff --git a/docs/validators/setup/assets/standalone-setup.svg b/docs/validators/setup/assets/standalone-setup.svg
index baade9e..b1d8234 100644
--- a/docs/validators/setup/assets/standalone-setup.svg
+++ b/docs/validators/setup/assets/standalone-setup.svg
@@ -1,4 +1,5 @@
-
\ No newline at end of file
+
+
\ No newline at end of file
diff --git a/docs/validators/setup/cli.md b/docs/validators/setup/cli.md
index b78caaa..cf18b21 100644
--- a/docs/validators/setup/cli.md
+++ b/docs/validators/setup/cli.md
@@ -17,7 +17,9 @@ This guide demonstrates how to compile a Ronin binary on your own using the Roni
* Golang 1.20 or later (follow the instructions at [https://go.dev/doc/install](https://go.dev/doc/install))
* C compiler
-## Step 1. Download Ronin source
+## Steps
+
+### Step 1. Download Ronin source
To download the Ronin source code, clone the GitHub repository. We recommend that you create a home `ronin` directory first and download all the Ronin-related software there:
@@ -26,7 +28,7 @@ mkdir -p ~/roninchain && cd ~/roninchain
git clone git@github.com:axieinfinity/ronin.git
```
-## Step 2. Build the binary
+### Step 2. Build the binary
Create a `ronin` binary from source:
@@ -37,7 +39,7 @@ make ronin
The `make ronin` command creates a `ronin` binary in the `./build/bin` directory.
-## Step 3. Add the binary to PATH
+### Step 3. Add the binary to PATH
To run the `ronin` binary without specifying its location in each command, add the directory where the binary is located to your `$PATH` environment variable:
@@ -51,7 +53,7 @@ If run from the `ronin` directory that you cloned, then the command is as follow
export PATH=$PATH:./build/bin/
```
-## Step 4. Initialize the genesis block
+### Step 4. Initialize the genesis block
To set up the origin state of the chain, initialize the genesis block. In your command, include the path to the genesis files located in the repository's `genesis` directory, and the path where you store the node's data, such as `~/roninchain/data`.
@@ -74,9 +76,9 @@ To set up the origin state of the chain, initialize the genesis block. In your c
Whenever you build the node or upgrade the software with a new hardfork, always initialize the genesis block by running the preceding command.
-## Step 5. Run the node
+### Step 5. Run the node
-To run a full (non-validator) Ronin node, use the following command:
+To run an RPC node, use the following command:
@@ -103,6 +105,8 @@ To run an archive node, modify the preceding command by adding the `--syncmode f
ronin --syncmode full --gcmode archive --http.api ...
```
+## Reference
+
### Configuration
Instead of passing numerous flags to the `ronin` binary, you can pass a configuration file as follows:
@@ -117,9 +121,9 @@ To get an idea of how the file should look like, use the `dumpconfig` subcommand
ronin --your-favourite-flags dumpconfig
```
-## Command reference
+### Commands
-### Synopsis
+#### Synopsis
```bash
ronin [options] [command] [command options] [arguments...]
@@ -127,7 +131,7 @@ ronin [options] [command] [command options] [arguments...]
Use `ronin [command] help` for information on a specific command.
-### Available commands
+#### Available commands
```plaintext
account Manage accounts
@@ -155,7 +159,7 @@ wallet Manage Ethereum presale wallets
help, h Shows a list of commands or help for one command
```
-### Ethereum options
+#### Ethereum options
```plaintext
--config value TOML configuration file
@@ -184,7 +188,7 @@ help, h Shows a list of commands or help for one comm
--ronin.disable Disable ronin p2p protocol
```
-### Light client options
+#### Light client options
```plaintext
--light.serve value Maximum percentage of time allowed for serving LES requests (multi-threaded processing allows values over 100) (default: 0)
@@ -198,7 +202,7 @@ help, h Shows a list of commands or help for one comm
--light.nosyncserve Enables serving light clients before syncing
```
-### Developer chain options
+#### Developer chain options
```plaintext
--dev Ephemeral proof-of-authority network with a pre-funded developer account, mining enabled
@@ -206,7 +210,7 @@ help, h Shows a list of commands or help for one comm
--dev.gaslimit value Initial block gas limit (default: 11500000)
```
-### Ethash options
+#### Ethash options
```plaintext
--ethash.cachedir value Directory to store the ethash verification caches (default = inside the datadir)
@@ -219,7 +223,7 @@ help, h Shows a list of commands or help for one comm
--ethash.dagslockmmap Lock memory maps for recent ethash mining DAGs
```
-### Transaction pool options
+#### Transaction pool options
```plaintext
--txpool.locals value Comma-separated accounts to treat as locals (no flush, priority inclusion)
@@ -235,7 +239,7 @@ help, h Shows a list of commands or help for one comm
--txpool.lifetime value Maximum amount of time non-executable transaction are queued (default: 3h0m0s)
```
-### Performance tuning options
+#### Performance tuning options
```plaintext
--cache value Megabytes of memory allocated to internal caching (default = 4096 mainnet full node, 128 light mode) (default: 1024)
@@ -249,7 +253,7 @@ help, h Shows a list of commands or help for one comm
--cache.preimages Enable recording the SHA3/keccak preimages of trie s
```
-### Account options
+#### Account options
```plaintext
--unlock value Comma-separated list of accounts to unlock
@@ -259,7 +263,7 @@ help, h Shows a list of commands or help for one comm
--enable-signing-methods Enable RPC signing methods
```
-### API and console options
+#### API and console options
```plaintext
--ipcdisable Disable the IPC-RPC server
@@ -291,7 +295,7 @@ help, h Shows a list of commands or help for one comm
--preload value Comma separated list of JavaScript files to preload into the console
```
-### Networking options
+#### Networking options
```plaintext
--bootnodes value Comma-separated enode URLs for P2P discovery bootstrap
@@ -307,7 +311,7 @@ help, h Shows a list of commands or help for one comm
--nodehex value P2P node as hex (for testing)
```
-### Miner options
+#### Miner options
```plaintext
--mine Enable mining
@@ -324,7 +328,7 @@ help, h Shows a list of commands or help for one comm
--miner.blocksizereserve value Reserved block size when committing transactions to block (default: 500000)
```
-### Gas price oracle options
+#### Gas price oracle options
```plaintext
--gpo.blocks value Number of recent blocks to check for gas prices (default: 20)
@@ -333,13 +337,13 @@ help, h Shows a list of commands or help for one comm
--gpo.ignoreprice value Gas price below which gpo will ignore transactions (default: 2)
```
-### Virtual machine options
+#### Virtual machine options
```plaintext
--vmdebug Record information useful for VM and contract debugging
```
-### Logging and debugging options
+#### Logging and debugging options
```plaintext
--fakepow Disables proof-of-work verification
@@ -358,7 +362,7 @@ help, h Shows a list of commands or help for one comm
--trace value Write execution trace to the given file
```
-### Metrics and stats options
+#### Metrics and stats options
```plaintext
--metrics Enable metrics collection and reporting
@@ -377,7 +381,7 @@ help, h Shows a list of commands or help for one comm
--metrics.influxdb.organization value InfluxDB organization name (v2 only) (default: "geth")
```
-### Profiling options
+#### Profiling options
```plaintext
--pyroscope.enabled Enable pyroscope - profiling tool
@@ -387,7 +391,7 @@ help, h Shows a list of commands or help for one comm
--pyroscope.mutexprofilefraction value Get the fraction of mutex contention events (default: 5)
```
-### Fast finality options
+#### Fast finality options
```plaintext
--votepool.maxcurvoteperblock value The maximum finality vote per current block (default: 22)
@@ -401,7 +405,7 @@ help, h Shows a list of commands or help for one comm
--readiness.block.lag value The block lag for deciding the readiness is success or fail (default: 5)
```
-### Other options
+#### Other options
```plaintext
--snapshot Enables snapshot-database mode (default = enable)
diff --git a/docs/validators/setup/generate-keys.md b/docs/validators/setup/generate-keys.mdx
similarity index 91%
rename from docs/validators/setup/generate-keys.md
rename to docs/validators/setup/generate-keys.mdx
index de9d2ed..ad34da0 100644
--- a/docs/validators/setup/generate-keys.md
+++ b/docs/validators/setup/generate-keys.mdx
@@ -3,9 +3,6 @@ description: Securely generate private keys for your validator node.
title: Generate private keys
---
-import extension from './assets/extension.png';
-import mobile from './assets/mobile.png';
-
## Overview
Each validator node requires private keys for signing blocks and consensus messages sent to the other validators in the network.
@@ -17,9 +14,7 @@ The required private keys include a BLS key and an ECDSA key. The keys are named
## Prerequisites
-Go (version 1.20 or later). Follow the
-[installation instructions](https://go.dev/doc/install)
-on the official website.
+Go (version 1.20 or later). Follow the [installation instructions](https://go.dev/doc/install) on the official website.
## Generate a BLS key
@@ -142,15 +137,15 @@ You can generate an ECDSA key pair using the Ronin command-line tool (CLI) or th
### Generate using Ronin Wallet
-ECDSA keys can also be generated using [Ronin Wallet](https://wallet.roninchain.com/), both the browser extension and the mobile app. Follow the steps in the flow diagrams provided in the following sections.
+ECDSA keys can also be generated using [Ronin Wallet](https://wallet.roninchain.com/), both the browser extension and the mobile app.
#### Browser extension
-
+In the browser extension, go to **Settings > your account > Show Private Key > Proceed**.
#### Mobile app
-
+In the mobile app, go to **Settings > Account > Show Private Key > Proceed**.
## See also
diff --git a/docs/validators/setup/mainnet/run-archive.md b/docs/validators/setup/mainnet/run-archive.mdx
similarity index 92%
rename from docs/validators/setup/mainnet/run-archive.md
rename to docs/validators/setup/mainnet/run-archive.mdx
index fc44fb9..1339ccc 100644
--- a/docs/validators/setup/mainnet/run-archive.md
+++ b/docs/validators/setup/mainnet/run-archive.mdx
@@ -16,7 +16,7 @@ Install Docker Engine and the Docker Compose plugin:
* [Docker Engine](https://docs.docker.com/engine/)
* [Docker Compose](https://docs.docker.com/compose/)
-## Run the node
+## Steps
1. Set up directories:
@@ -83,13 +83,13 @@ Install Docker Engine and the Docker Compose plugin:
CHAIN_STATS_WS_SECRET=WSyDMrhRBe111
CHAIN_STATS_WS_SERVER=ronin-stats-ws.roninchain.com
- RONIN_PARAMS=--gcmode archive --http.api eth,net,web3 --txpool.pricelimit 20000000000 --txpool.nolocals --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
+ RONIN_PARAMS=--gcmode archive --http.api eth,net,web3 --txpool.pricelimit 20000000000 --txpool.nolocals --cache 4096 --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
```
4. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image and starts the service you defined.
diff --git a/docs/validators/setup/mainnet/run-combined.md b/docs/validators/setup/mainnet/run-combined.mdx
similarity index 90%
rename from docs/validators/setup/mainnet/run-combined.md
rename to docs/validators/setup/mainnet/run-combined.mdx
index 150c9cc..c56b1d2 100644
--- a/docs/validators/setup/mainnet/run-combined.md
+++ b/docs/validators/setup/mainnet/run-combined.mdx
@@ -9,7 +9,7 @@ tags:
This guide demonstrates how to run a mainnet validator node and a bridge node on one machine using Docker.
-## Before you start
+## Prerequisites
### Docker
@@ -32,9 +32,9 @@ Generate private keys for operating the nodes:
* One key for the validator node
* One key for the bridge operator
-For more information, see [Generate keys](../generate-keys.md).
+For more information, see [Generate keys](../generate-keys.mdx).
-## Run the node
+## Steps
1. Set up directories:
@@ -90,6 +90,7 @@ For more information, see [Generate keys](../generate-keys.md).
- ENABLE_FAST_FINALITY=${ENABLE_FAST_FINALITY}
- ENABLE_FAST_FINALITY_SIGN=${ENABLE_FAST_FINALITY_SIGN}
- BLS_SHOW_PRIVATE_KEY=${BLS_SHOW_PRIVATE_KEY}
+ - GENERATE_BLS_PROOF=${GENERATE_BLS_PROOF}
db:
image: postgres:14.3
restart: always
@@ -155,14 +156,14 @@ For more information, see [Generate keys](../generate-keys.md).
# Your bridge operator private key without the 0x prefix
LISTENERS__RONIN__SECRET__BRIDGEOPERATOR__PLAINPRIVATEKEY=
- # Your validator private key without the 0x prefix
- VALIDATOR_PRIVATE_KEY=
+ # Your ECDSA private key without the 0x prefix, see https://docs.roninchain.com/validators/setup/generate-keys#generate-an-ecdsa-key
+ VALIDATOR_PRIVATE_KEY=
# The password used to encrypt the node's private key file
PASSWORD=
# BLS Wallet features
- # Your BLS private key without the 0x prefix
+ # Your BLS private key without the 0x prefix, see https://docs.roninchain.com/validators/setup/generate-keys#generate-a-bls-key
BLS_PRIVATE_KEY=
# The password used to encrypt the BLS private key file
@@ -206,14 +207,14 @@ For more information, see [Generate keys](../generate-keys.md).
CHAIN_STATS_WS_SECRET=WSyDMrhRBe111
CHAIN_STATS_WS_SERVER=ronin-stats-ws.roninchain.com
- RONIN_PARAMS=--http.api eth,net,web3,consortium --miner.gaslimit 100000000 --miner.gasreserve 10000000 --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
+ RONIN_PARAMS=--http.api eth,net,web3,consortium --miner.gaslimit 100000000 --miner.gasreserve 10000000 --cache 4096 --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
LISTENERS__RONIN__STATS__NODE=
LISTENERS__RONIN__STATS__HOST=wss://ronin-stats-ws.roninchain.com/bridge
LISTENERS__RONIN__STATS__SECRET=WSyDMrhRBe111
```
-5. (Optional) Download the snapshot from the [ronin-snapshot](https://github.com/axieinfinity/ronin-snapshot) repo:
+5. (Optional) Download the snapshot from the [ronin-snapshot](https://github.com/axieinfinity/ronin-snapshot) repo, preferably using PebbleDB:
```bash
cd ~/ronin/chaindata/data/ronin/
@@ -223,7 +224,7 @@ For more information, see [Generate keys](../generate-keys.md).
6. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image, a bridge image, a Postgres database, and starts the services you defined.
diff --git a/docs/validators/setup/mainnet/run-validator.md b/docs/validators/setup/mainnet/run-validator.mdx
similarity index 85%
rename from docs/validators/setup/mainnet/run-validator.md
rename to docs/validators/setup/mainnet/run-validator.mdx
index 7c957c0..96dde5e 100644
--- a/docs/validators/setup/mainnet/run-validator.md
+++ b/docs/validators/setup/mainnet/run-validator.mdx
@@ -9,7 +9,7 @@ tags:
This guide demonstrates how to run a validator node on the mainnet using Docker.
-## Before you start
+## Prerequisites
### Docker
@@ -20,9 +20,9 @@ Install Docker Engine and the Docker Compose plugin:
### Private key
-Generate a private key for your validator node. For more information, see [Generate keys](../generate-keys.md).
+Generate a private key for your validator node. For more information, see [Generate keys](../generate-keys.mdx).
-## Run the node
+## Steps
1. Set up directories:
@@ -72,6 +72,7 @@ Generate a private key for your validator node. For more information, see [Gener
- ENABLE_FAST_FINALITY=${ENABLE_FAST_FINALITY}
- ENABLE_FAST_FINALITY_SIGN=${ENABLE_FAST_FINALITY_SIGN}
- BLS_SHOW_PRIVATE_KEY=${BLS_SHOW_PRIVATE_KEY}
+ - GENERATE_BLS_PROOF=${GENERATE_BLS_PROOF}
```
This compose file defines the `node` service that pulls a Ronin node image from the GitHub Container Registry.
@@ -84,14 +85,14 @@ Generate a private key for your validator node. For more information, see [Gener
# The latest version of the node's image as listed in https://docs.roninchain.com/validators/setup/upgrade-validator
NODE_IMAGE=
- # Your validator private key without the 0x prefix
- VALIDATOR_PRIVATE_KEY=
+ # Your ECDSA private key without the 0x prefix, see https://docs.roninchain.com/validators/setup/generate-keys#generate-an-ecdsa-key
+ VALIDATOR_PRIVATE_KEY=
# The password used to encrypt the node's private key file
PASSWORD=
# BLS Wallet features
- # Your BLS private key without the 0x prefix
+ # Your BLS private key without the 0x prefix, see https://docs.roninchain.com/validators/setup/generate-keys#generate-a-bls-key
BLS_PRIVATE_KEY=
# The password used to encrypt the BLS private key file
@@ -118,10 +119,10 @@ Generate a private key for your validator node. For more information, see [Gener
CHAIN_STATS_WS_SECRET=WSyDMrhRBe111
CHAIN_STATS_WS_SERVER=ronin-stats-ws.roninchain.com
- RONIN_PARAMS=--http.api eth,net,web3,consortium --miner.gaslimit 100000000 --miner.gasreserve 10000000 --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
+ RONIN_PARAMS=--http.api eth,net,web3,consortium --miner.gaslimit 100000000 --miner.gasreserve 10000000 --cache 4096 --discovery.dns enrtree://AIGOFYDZH6BGVVALVJLRPHSOYJ434MPFVVQFXJDXHW5ZYORPTGKUI@nodes.roninchain.com
```
-4. (Optional) Download the snapshot from the [ronin-snapshot](https://github.com/axieinfinity/ronin-snapshot) repo:
+4. (Optional) Download the snapshot from the [ronin-snapshot](https://github.com/axieinfinity/ronin-snapshot) repo, preferably using PebbleDB:
```bash
cd ~/ronin/chaindata/data/ronin/
@@ -131,7 +132,7 @@ Generate a private key for your validator node. For more information, see [Gener
5. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image and starts the service you defined.
@@ -142,6 +143,7 @@ Generate a private key for your validator node. For more information, see [Gener
```
7. After a few minutes, check the status of your node on the [Ronin Analytics](https://ronin-stats.roninchain.com/) page. If it's green, the node is connected and up to date with the network.
+8.
## Verify the node is working
diff --git a/docs/validators/setup/overview.md b/docs/validators/setup/overview.md
index 350fd25..034d8e5 100644
--- a/docs/validators/setup/overview.md
+++ b/docs/validators/setup/overview.md
@@ -23,7 +23,7 @@ To run a reliable, performant node, we suggest that the node’s hardware profil
### Ronin mainnet
-| Validator node | Non-validator node | Archive node | Bridge node |
+| Validator node | RPC node | Archive node | Bridge node |
|---------------------------|---------------------------|------------------------|---------------------------|
| 8-core CPU | 6-core CPU | 8-core CPU | 4-core CPU |
| 32 GB RAM | 25 GB RAM | 32 GB RAM | 8 GB RAM |
@@ -32,7 +32,7 @@ To run a reliable, performant node, we suggest that the node’s hardware profil
### Saigon testnet
-| Validator node | Non-validator node | Archive node | Bridge node |
+| Validator node | RPC node | Archive node | Bridge node |
|---------------------------|---------------------------|------------------------|---------------------------|
| 2-core CPU | 6-core CPU | 4-core CPU | - |
| 8 GB RAM | 8 GB RAM | 8 GB RAM | - |
diff --git a/docs/validators/setup/random-beacon.md b/docs/validators/setup/random-beacon.md
index d93191e..3c44f90 100644
--- a/docs/validators/setup/random-beacon.md
+++ b/docs/validators/setup/random-beacon.md
@@ -125,7 +125,7 @@ docker logs ronin-random-beacon-chain -f –tail 100
## Run Random Beacon Service in combined mode
-1. Setup directory for postgres db data (assume that your node directory is as same as setting in [here](./mainnet/run-validator.md))
+1. Setup directory for postgres db data (assume that your node directory is as same as setting in [here](./mainnet/run-validator.mdx))
```
cd ~/ronin
diff --git a/docs/validators/setup/testnet/run-archive.md b/docs/validators/setup/testnet/run-archive.mdx
similarity index 97%
rename from docs/validators/setup/testnet/run-archive.md
rename to docs/validators/setup/testnet/run-archive.mdx
index 094e904..67547a3 100644
--- a/docs/validators/setup/testnet/run-archive.md
+++ b/docs/validators/setup/testnet/run-archive.mdx
@@ -9,7 +9,7 @@ tags:
This guide demonstrates how to run an archive node on the Saigon testnet using Docker.
-## Before you start
+## Prerequisites
### Docker
@@ -18,7 +18,7 @@ Install Docker Engine and the Docker Compose plugin:
* [Docker Engine](https://docs.docker.com/engine/)
* [Docker Compose](https://docs.docker.com/compose/)
-## Run the node
+## Steps
1. Set up directories:
@@ -94,7 +94,7 @@ Install Docker Engine and the Docker Compose plugin:
4. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image and starts the service you defined.
diff --git a/docs/validators/setup/testnet/run-combined.md b/docs/validators/setup/testnet/run-combined.mdx
similarity index 93%
rename from docs/validators/setup/testnet/run-combined.md
rename to docs/validators/setup/testnet/run-combined.mdx
index 73d8ab5..acc8f34 100644
--- a/docs/validators/setup/testnet/run-combined.md
+++ b/docs/validators/setup/testnet/run-combined.mdx
@@ -9,7 +9,7 @@ tags:
This guide demonstrates how to run a testnet validator node and a bridge operator on one machine using Docker.
-## Before you start
+## Prerequisites
### Docker
@@ -32,9 +32,9 @@ Generate private keys for operating the nodes:
* One key for the validator
* One key for the bridge
-For more information, see [Generate keys](../generate-keys.md).
+For more information, see [Generate keys](../generate-keys.mdx).
-## Run the node
+## Steps
1. Set up directories:
@@ -91,6 +91,7 @@ For more information, see [Generate keys](../generate-keys.md).
- ENABLE_FAST_FINALITY=${ENABLE_FAST_FINALITY}
- ENABLE_FAST_FINALITY_SIGN=${ENABLE_FAST_FINALITY_SIGN}
- BLS_SHOW_PRIVATE_KEY=${BLS_SHOW_PRIVATE_KEY}
+ - GENERATE_BLS_PROOF=${GENERATE_BLS_PROOF}
db:
image: postgres:14.3
restart: always
@@ -151,14 +152,14 @@ For more information, see [Generate keys](../generate-keys.md).
# Your bridge operator private key without the 0x prefix
BRIDGE_OPERATOR_PRIVATE_KEY=
- # Your validator private key without the 0x prefix
- VALIDATOR_PRIVATE_KEY=
+ # Your ECDSA private key without the 0x prefix, see https://docs.roninchain.com/validators/setup/generate-keys#generate-an-ecdsa-key
+ VALIDATOR_PRIVATE_KEY=
# The password used to encrypt the node's private key file
PASSWORD=
# BLS Wallet features
- # Your BLS private key without the 0x prefix
+ # Your BLS private key without the 0x prefix, see https://docs.roninchain.com/validators/setup/generate-keys#generate-a-bls-key
BLS_PRIVATE_KEY=
# The password used to encrypt the BLS private key file
@@ -217,7 +218,7 @@ For more information, see [Generate keys](../generate-keys.md).
5. Start the node:
```bash
- cd ~/ronin && docker-compose up -d
+ cd ~/ronin/docker && docker-compose up -d
```
This command pulls a Ronin node image, a bridge image, a Postgres database, and starts the services you defined.
diff --git a/docs/validators/setup/upgrade-validator.md b/docs/validators/setup/upgrade-validator.md
index 6a0c16b..6f19bd5 100644
--- a/docs/validators/setup/upgrade-validator.md
+++ b/docs/validators/setup/upgrade-validator.md
@@ -59,4 +59,4 @@ To download the latest image for your node, follow these steps:
## See also
-[Upgrade bridge version](./../../bridge-operators/setup/upgrade-bridge.md)
+[Upgrade bridge version](./../../bridge-operators/setup/upgrade-bridge.mdx)
diff --git a/sidebars.js b/sidebars.js
index 633bb38..aa44888 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -198,6 +198,20 @@ const sidebars = {
'apps/multisig',
],
},
+ // RPC nodes
+ {
+ type: 'category',
+ label: 'RPC nodes',
+ link: {
+ type: 'generated-index',
+ slug: '/rpc',
+ description: 'Guides for setting up and using an RPC node.',
+ },
+ items: [
+ 'rpc/mainnet-rpc',
+ 'rpc/testnet-rpc',
+ ],
+ },
// Delegators
{
type: 'category',
@@ -249,8 +263,6 @@ const sidebars = {
'validators/setup/mainnet/run-combined',
// Run a validator
'validators/setup/mainnet/run-validator',
- // Run a full node
- 'validators/setup/mainnet/run-non-validator',
// Run an archive node
'validators/setup/mainnet/run-archive',
],
@@ -267,8 +279,6 @@ const sidebars = {
items: [
// Run a validator and bridge together
'validators/setup/testnet/run-combined',
- // Run a non-validator-node
- 'validators/setup/testnet/run-non-validator',
// Run a full archive node
'validators/setup/testnet/run-archive',
],