PoS: update node deployment tag

- remove mumbai tag
- add amoy tag
- add seed node note for amoy
- minor fixes

Author: hsutaiyu

docs/pos/how-to/erigon-archive-node.md

@@ -6,7 +6,7 @@
 - **Storage**
     - Basically **io1** or above with at least 20k+ iops and RAID-0 based disk structure
     - Mainnet archive node: 10TB
-    - Mumbai testnet archive node: 2TB
+    - Amoy testnet archive node: 2TB
     - SSD or NVMe. Bear in mind that SSD performance deteriorates when close to capacity
 - **Golang:** >= v1.20
 - **GCC:** >= v10
@@ -31,10 +31,10 @@ This should create the binary at `./build/bin/erigon`
 
 ## Start Erigon client
 
-When connecting to Mumbai testnet, use the following command to start your Erigon client:
+When connecting to Amoy testnet, use the following command to start your Erigon client:
 
 ```bash
-erigon --chain=mumbai
+erigon --chain=amoy
 ```
 
 If you're deploying to mainnet, run the following command:
@@ -48,18 +48,18 @@ erigon --chain=bor-mainnet --db.size.limit=12TB --db.pagesize=16KB # remaining f
 If you want to store Erigon files in a non-default location, use `-datadir` to specify a new location:
 
 ```bash
-erigon --chain=mumbai --datadir=<your_data_dir>
+erigon --chain=amoy --datadir=<your_data_dir>
 ```
 
 If you are not using local **heimdall**, use `-bor.heimdall=<your heimdall url>`. By default, it will try to connect to `localhost:1317`.
 
-```makefile
-erigon --chain=mumbai --bor.heimdall=<your heimdall url> --datadir=<your_data_dir>
+```bash
+erigon --chain=amoy --bor.heimdall=<your heimdall url> --datadir=<your_data_dir>
 ```
 
 !!! note
 
-    - If you want to connect to Polygon Mumbai Testnet, use: [https://heimdall-api-testnet.polygon.technology](https://heimdall-api-testnet.polygon.technology)
+    - If you want to connect to Polygon Amoy Testnet, use: [https://heimdall-api-testnet.polygon.technology](https://heimdall-api-testnet.polygon.technology)
 
     - For Polygon mainnet, use: [https://heimdall-api.polygon.technology](https://heimdall-api.polygon.technology)
 
@@ -74,4 +74,4 @@ erigon --chain=mumbai --bor.heimdall=<your heimdall url> --datadir=<your_data_di
 
 ## Reporting issues
 
-In case you encounter any issues and are looking for support, please get in touch with the Erigon team. More details available in [this GitHub README](https://github.com/ledgerwatch/erigon?tab=readme-ov-file#getting-in-touch).
+In case you encounter any issues and are looking for support, please get in touch with the Erigon team. More details available in [the Erigon GitHub README](https://github.com/ledgerwatch/erigon?tab=readme-ov-file#getting-in-touch).

docs/pos/how-to/full-node/full-node-binaries.md

@@ -1,5 +1,5 @@
 
-This deployment guide walks you through starting and running a full node through various methods. For the system requirements, see the [Minimum Technical Requirements](../validator/validator-system-requirements.md) guide.
+This deployment guide walks you through starting and running a full node through various methods. For the system requirements, see the [minimum technical requirements](../validator/validator-system-requirements.md) guide.
 
 !!!tip "Snapshots"
 
@@ -64,9 +64,11 @@ To install **Heimdall**, run the below commands:
 curl -L https://raw.githubusercontent.com/maticnetwork/install/main/heimdall.sh | bash -s -- <heimdall_version> <network_type> <node_type>
 ```
 
-**heimdall_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/heimdall/releases`
-**network_type**: `mainnet` and `mumbai`
-**node_type**: `sentry`
+You can run the above command with following options:
+
+- **heimdall_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/heimdall/releases`
+- **network_type**: `mainnet` and `amoy`
+- **node_type**: `sentry`
 
 That will install the `heimdalld` and `heimdallcli` binaries. Verify the installation by checking the Heimdall version on your machine:
 
@@ -81,15 +83,9 @@ sed -i 's|^seeds =.*|seeds = "1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.
 chown heimdall /var/lib/heimdall
 ```
 
-### Configure Heimdall seeds (Mumbai)
-
-```bash
-sed -i 's|^seeds =.*|seeds = "9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656,d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656,1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656"|g' /var/lib/heimdall/config/config.toml
-chown heimdall /var/lib/heimdall
-```
+### Configure Heimdall seeds (Amoy)
 
-!!! tip
-    The following Heimdall seed can be used for both mainnet and Mumbai testnet: `8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656`
+The Heimdall seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
 
 ### Bor install
 
@@ -98,32 +94,29 @@ Install the latest version of Bor, based on valid v1.0+ [released version](https
 ```bash
 curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash -s -- <bor_version> <network_type> <node_type>
 ```
+You can run the above command with following options:
 
-**bor_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/bor/releases`
-**network_type**: `mainnet` and `mumbai`
-**node_type**: `sentry`
+- **bor_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/bor/releases`
+- **network_type**: `mainnet` and `amoy`
+- **node_type**: `sentry`
 
 That will install the `bor` binary. Verify the installation by checking the Bor version on your machine:
 
 ```bash
 bor version
 ```
 
-### Configure Bor seeds (mainnet)
+### Configure Bor seeds (Mainnet)
 
 ```bash
 sed -i 's|.*\[p2p.discovery\]|  \[p2p.discovery\] |g' /var/lib/bor/config.toml
 sed -i 's|.*bootnodes =.*|    bootnodes = ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]|g' /var/lib/bor/config.toml
 chown bor /var/lib/bor
 ```
 
-### Configure Bor seeds (mumbai)
+### Configure Bor seeds (Amoy)
 
-```bash
-sed -i 's|.*\[p2p.discovery\]|  \[p2p.discovery\] |g' /var/lib/bor/config.toml
-sed -i 's|.*bootnodes =.*|    bootnodes = ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]|g' /var/lib/bor/config.toml
-chown bor /var/lib/bor
-```
+The Bor seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
 
 ### Update service config user permission
 

docs/pos/how-to/full-node/full-node-packages.md

@@ -26,7 +26,7 @@
     curl -L https://raw.githubusercontent.com/maticnetwork/install/main/heimdall.sh | bash
     ```
 
-    or install a specific version, node type (`sentry` or `validator`), and network (`mainnet` or `mumbai`). All release versions can be found on
+    or install a specific version, node type (`sentry` or `validator`), and network (`mainnet` or `amoy`). All release versions can be found on
     [Heimdall GitHub repository](https://github.com/maticnetwork/heimdall/releases).
 
     ```shell
@@ -43,7 +43,7 @@
     curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash
     ```
 
-    or install a specific version, node type (`sentry` or `validator`), and network (`mainnet` or `mumbai`). All release versions could be found on
+    or install a specific version, node type (`sentry` or `validator`), and network (`mainnet` or `amoy`). All release versions could be found on
     [Bor Github repository](https://github.com/maticnetwork/bor/releases).
 
     ```shell
@@ -75,7 +75,7 @@ In this section, we will go through steps to initialize and customize configurat
 sudo -u heimdall heimdalld init --chain=mainnet --home /var/lib/heimdall
 
 # For testnet
-sudo -u heimdall heimdalld init --chain=mumbai --home /var/lib/heimdall
+sudo -u heimdall heimdalld init --chain=amoy --home /var/lib/heimdall
 ```
 
 - You will need to add a few details in the `config.toml` file. To open the `config.toml` file run the following command `vi /var/lib/heimdall/config/config.toml`
@@ -99,13 +99,13 @@ You will need to check and modify these files accordingly.
 
 - Make sure the chain is set correctly in `/lib/systemd/system/heimdalld.service` file. Open the file with following command `sudo vi /lib/systemd/system/heimdalld.service`
 
-    - In the service file, set `--chain` to `mainnet` or `mumbai` accordingly
+    - In the service file, set `--chain` to `mainnet` or `amoy` accordingly
 
   Save the changes in `/lib/systemd/system/heimdalld.service`.
 
 - Make sure the chain is set correctly in `/var/lib/bor/config.toml` file. Open the file with following command `sudo vi /var/lib/bor/config.toml`
 
-    - In the config file, set `chain` to `mainnet` or `mumbai` accordingly.
+    - In the config file, set `chain` to `mainnet` or `amoy` accordingly.
 
     - To enable Archive mode you can optionally enable the following flags:
 

docs/pos/how-to/validator/validator-binaries.md

@@ -143,10 +143,11 @@ To install **Heimdall**, run the below commands:
 ```bash
 curl -L https://raw.githubusercontent.com/maticnetwork/install/main/heimdall.sh | bash -s -- <heimdall_version> <network_type> <node_type>
 ```
+You can run the above command with following options:
 
-**heimdall_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/heimdall/releases`
-**network_type**: `mainnet` and `mumbai`
-**node_type**: `sentry`
+- **heimdall_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/heimdall/releases`
+- **network_type**: `mainnet` and `amoy`
+- **node_type**: `sentry`
 
 That will install the `heimdalld` and `heimdallcli` binaries. Verify the installation by checking the Heimdall version on your machine:
 
@@ -166,10 +167,11 @@ Install the latest version of Bor, based on valid v1.0+ [released version](https
 ```bash
 curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash -s -- <bor_version> <network_type> <node_type>
 ```
+You can run the above command with following options:
 
-**bor_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/bor/releases`
-**network_type**: `mainnet` and `mumbai`
-**node_type**: `sentry`
+- **bor_version**: `valid v1.0+ release tag from https://github.com/maticnetwork/bor/releases`
+- **network_type**: `mainnet` and `amoy`
+- **node_type**: `sentry`
 
 That will install the `bor` binary. Verify the installation by checking the Bor version on your machine:
 
@@ -517,29 +519,24 @@ journalctl -u bor.service -f
 
 ### Seed nodes and bootnodes
 
+!!! note "Amoy node seeds"
+
+    The Heimdall and Bor seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
+
 - Heimdall seed nodes:
 
   ```bash
   moniker=<enter unique identifier>
 
   # Mainnet:
   seeds="1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656,dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656,8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656,e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656,6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656"
-
-  # Testnet:
-  seeds="9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656,d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656,1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656"
   ```
 
-!!! tip
-    The following Heimdall seed can be used for both mainnet and Mumbai testnet: `8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656`
-
 - Bootnodes:
 
   ```bash
   # Mainnet:
   bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]
-
-  # Testnet:
-  bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]
   ```
 
 

docs/pos/how-to/validator/validator-packages.md

@@ -39,7 +39,7 @@ To get to a running validator node, conduct the following in this **exact sequen
     curl -L https://raw.githubusercontent.com/maticnetwork/install/main/heimdall.sh | bash
     ```
 
-    or install a specific version, node type (`sentry` or `validator`), and network (`mainnet` or `mumbai`). All release versions can be found on
+    or install a specific version, node type (`sentry` or `validator`), and network (`mainnet` or `amoy`). All release versions can be found on
     [Heimdall GitHub repository](https://github.com/maticnetwork/heimdall/releases).
 
     ```shell
@@ -56,7 +56,7 @@ To get to a running validator node, conduct the following in this **exact sequen
     curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash
     ```
 
-    or install a specific version,  node type (`sentry` or `validator`), and network (`mainnet` or `mumbai`). All release versions could be found on
+    or install a specific version,  node type (`sentry` or `validator`), and network (`mainnet` or `amoy`). All release versions could be found on
     [Bor Github repository](https://github.com/maticnetwork/bor/releases).
 
     ```shell
@@ -104,7 +104,7 @@ In this section, we will go through steps to initialize and customize configurat
 sudo -u heimdall heimdalld init --chain=mainnet --home /var/lib/heimdall
 
 # For testnet
-sudo -u heimdall heimdalld init --chain=mumbai --home /var/lib/heimdall
+sudo -u heimdall heimdalld init --chain=amoy --home /var/lib/heimdall
 ```
 
 Open the Heimdall configuration file for editing:
@@ -182,13 +182,13 @@ After successfully installing Bor and Heimdall through [packages](#installing-pa
 file could be found under `/var/lib/bor/config.toml`.
 You will need to check and modify these files accordingly.
 
-    - In the service file, set `--chain` to `mainnet` or `mumbai` accordingly
+    - In the service file, set `--chain` to `mainnet` or `amoy` accordingly
 
   Save the changes in `/lib/systemd/system/heimdalld.service`.
 
 - Make sure the chain is set correctly in `/var/lib/bor/config.toml` file. Open the file with following command `sudo vi /var/lib/bor/config.toml`
 
-    - In the config file, set `chain` to `mainnet` or `mumbai` accordingly.
+    - In the config file, set `chain` to `mainnet` or `amoy` accordingly.
 
     - To enable Archive mode, you can optionally enable the following flags:
 
@@ -307,7 +307,7 @@ Initialize heimdall configs
 sudo -u heimdall heimdalld init --chain=mainnet --home /var/lib/heimdall
 
 # For testnet
-sudo -u heimdall heimdalld init --chain=mumbai --home /var/lib/heimdall
+sudo -u heimdall heimdalld init --chain=amoy --home /var/lib/heimdall
 ```
 
 Open the Heimdall configuration file for editing:
@@ -459,7 +459,7 @@ You will need to check and modify these files accordingly.
 
 - Make sure the chain is set correctly in `/lib/systemd/system/heimdalld.service` file. Open the file with following command `sudo vi /lib/systemd/system/heimdalld.service`
 
-    - In the service file, set `--chain` to `mainnet` or `mumbai` accordingly
+    - In the service file, set `--chain` to `mainnet` or `amoy` accordingly
     - Add `--bridge --all` to the heimdall command line for validator, example:
       ```
         ExecStart=/usr/local/bin/heimdalld start --home /var/lib/heimdall \
@@ -472,7 +472,7 @@ You will need to check and modify these files accordingly.
 
 - Make sure the chain is set correctly in `/var/lib/bor/config.toml` file. Open the file with following command `sudo vi /var/lib/bor/config.toml`
 
-    - In the config file, set `chain` to `mainnet` or `mumbai` accordingly.
+    - In the config file, set `chain` to `mainnet` or `amoy` accordingly.
 
     - Enable validator flags, example:
       ```
@@ -565,29 +565,24 @@ journalctl -u bor.service -f
 ```
 ### Seed nodes and bootnodes
 
+!!! note "Amoy node seeds"
+
+    The Heimdall and Bor seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
+
 - Heimdall seed nodes:
 
   ```bash
   moniker=<enter unique identifier>
 
   # Mainnet:
   seeds="1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656,dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656,8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656,e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656,6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656"
-
-  # Testnet:
-  seeds="9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656,d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656,1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656"
   ```
 
-!!! tip
-    The following Heimdall seed can be used for both mainnet and Mumbai testnet: `8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656`
-
 - Bootnodes:
 
   ```bash
   # Mainnet:
   bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]
-
-  # Testnet:
-  bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]
   ```
 
 ## Health Checks with the Community