Merge pull request 0xPolygon#205 from 0xPolygon/howto-reorg

Howto reorg

Author: hsutaiyu

docs/pos/get-started/building-on-polygon.md

@@ -21,15 +21,45 @@ In order to be a validator on the Polygon Network, you need to:
 
 ## Wallets
 
-To interact with the Polygon Network, you need to have an Ethereum-based wallet because Polygon runs on Ethereum Virtual Machine (EVM). You can choose to set up a [Metamask](https://github.com/0xPolygon/wiki/blob/master/docs/tools/wallets/metamask/overview.md) or Arkane Wallet.
+You'll need an Ethereum-based wallet to interact with Polygon because the network runs on Ethereum Virtual Machine (EVM). You can choose to set up a [Metamask](../../tools/wallets/metamask/create-metamask-wallet.md), or [Venly](../../tools/wallets/venly/create-wallet.md) (Arkane) Wallet. 
+
+There are several other third-party wallet options available to choose from, and you'll find them listed out on [this page here](../../tools/wallets/getting-started.md).
+
+!!! tip "Set up web3 provider"
+
+    Refer to the following guides and follow along to set up your wallet for making web3 function calls:
+    
+    - [MetaMask](../../tools/wallets/metamask/index.md#1-set-up-web3)
+    - [Venly](../../tools/wallets/venly/index.md#initialize-the-web3-provider)
+
+## Common tasks
+
+Token bridging between Polygon PoS and Ethereum and vice-versa, and inter-layer communication are basic and essential actions that most dApps need to perform. Use the links below to navigate to guides that'll help you get started with these tasks.
+
+* [Bridge tokens from Ethereum to PoS](../how-to/bridging/ethereum-polygon/ethereum-to-matic.md)
+* [Bridge tokens from PoS to Ethereum](../how-to/bridging/ethereum-polygon/matic-to-ethereum.md)
+* [L1 - L2 communication](../how-to/bridging/l1-l2-communication/state-transfer.md)
 
 ## Smart contracts
 
-Polygon supports many services you can use to test, compile, debug, and deploy decentralized applications onto the Polygon Network. These include deployment using thirdweb, Alchemy, Chainstack, QuickNode, Remix, Truffle, Hardhat, and Replit.
+Polygon supports many popular frameworks and tools that you can choose from to deploy, debug, compile, and test smart contracts on Polygon PoS. This helps ensure your dApp development experience on Polygon is virtually the same as it would be if you were deploying to Ethereum. These frameworks and tools include:
+
+- [Alchemy](../../tools/dApp-development/pos/alchemy.md)
+- [thirdweb](../../tools/dApp-development/pos/thirdweb.md)
+- [ChainIDE](../../tools/dApp-development/pos/chainide.md)
+- [Chainstack](../../tools/dApp-development/pos/chainstack.md)
+- [QuickNode](../../tools/dApp-development/pos/quicknode.md)
+- [GetBlock](../../tools/dApp-development/pos/quicknode.md)
+- [Crossmint](../../tools/dApp-development/pos/crossmint.md)
+- [SmartPress](../../tools/dApp-development/pos/crossmint.md)
+- [Remix](../../tools/dApp-development/common-tools/remix.md)
+- [Hardhat](../../tools/dApp-development/common-tools/hardhat.md)
+- [Truffle](../../tools/dApp-development/common-tools/hardhat.md)
+- [Replit](../../tools/dApp-development/common-tools/replit.md)
 
 ## Connecting to Polygon
 
-You can add Polygon to MetaMask or directly use Arkane, which allows you to connect to Polygon using RPC.
+You can add Polygon to MetaMask, or directly use Venly (Arkane), which allows you to connect to Polygon using RPC.
 
 In order to connect with the Polygon network to read blockchain information, we recommend using the Alchemy SDK.
 
@@ -76,9 +106,15 @@ Suppose you have no prior experience building decentralized applications (dApps)
 - Arkane
 - Develop a dApp using Fauna, Polygon and React
 
+## Polygon DID
+
+You can refer to the elaborate startup guide for users who wish to implement the Polygon DID, which is a three-part package consisting of an identity-registrar, identity-resolver, and identity-registry-contract.
+
+* [Polygon DID integration guide](../how-to/polygon-did.md)
+
 ## Already have a dApp?
 
 If you already have a decentralized application (dApp) and are looking for a platform to help you scale efficiently, then you are at the right place because Polygon allows you to:
 
 1. **Easily migrate from Ethereum Virtual Machine (EVM) based chain**: Polygon prides itself in being the ultimate Layer-2 scaling solution for Ethereum. You don't have to worry about the underlying architecture while moving or deploying your dApps to the Polygon Network as long as it is EVM-compatible.
-2. **Use Polygon as a faster transaction layer**: Deploying your dApp to the Polygon Mainnet allows you to leverage Polygon as a faster transaction layer for your dApp. Additionally, you can get your tokens mapped by us. You can join our [technical discussions group](http://bit.ly/matic-technical-group) on Telegram to learn more.
+2. **Use Polygon as a faster transaction layer**: Deploying your dApp to the Polygon Mainnet allows you to leverage Polygon as a faster transaction layer for your dApp. Additionally, you can get your tokens mapped by us. You can join our [technical discussions group](http://bit.ly/matic-technical-group) on Telegram to learn more.

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

@@ -1,71 +1,77 @@
 
-## System Requirements
+## System requirements
 
-- 16-core CPU
-- 64 GB RAM
-- Basically io1 or above with at least 20k+ iops and RAID-0 based disk structure
+- **CPU:** 16-core, 64-bit architecture
+- **RAM:** 64GB
+- **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
+    - SSD or NVMe. Bear in mind that SSD performance deteriorates when close to capacity
+- **Golang:** >= v1.20
+- **GCC:** >= v10
 
-## System Requirements
+!!! note "HDD not recommended"
 
-- For an Archive node of Polygon Mainnet: 8TB
-- For an Archive node of Mumbai Testnet: 1TB
-- SSD or NVMe. Bear in mind that SSD performance deteriorates when close to capacity
-- RAM: >= 32GB, 64-bit architecture
-- Golang version >= 1.18, GCC 10+ 
+    On HDDs, Erigon will always stay *N* blocks behind the chain tip, but will not fall behind. 
 
-!!!note
-    HDD not recommended
 
-    On HDDs, Erigon will always stay N blocks behind the chain tip, but will not fall behind. 
-
-
-## Install Erigon Client
+## Install Erigon client
 
 Run the following commands to install Erigon:
 
 ```bash
-git clone --recurse-submodules -j8 https://github.com/maticnetwork/erigon.git
+git clone --recurse-submodules -j8 https://github.com/ledgerwatch/erigon
 cd erigon
-git checkout v0.0.8
+git checkout v2.57.3
 make erigon
 ```
 
 This should create the binary at `./build/bin/erigon`
 
-Use the tag `v0.0.8` on our forked repo to have a stable version. 
-
-## Start Erigon Client
+## Start Erigon client
 
-To start Erigon, run:
+When connecting to Mumbai testnet, use the following command to start your Erigon client:
 
 ```bash
 erigon --chain=mumbai
 ```
 
-- Use `chain=mumbai` for Mumbai testnet
-- Use `chain=bor-mainnet` for Polygon Mainnet
+If you're deploying to mainnet, run the following command:
 
-## Configure Erigon Client
+```bash
+erigon --chain=bor-mainnet --db.size.limit=12TB --db.pagesize=16KB # remaining flags follow
+```
 
-- If you want to store Erigon files in a non-default location, use `-datadir`
-    
-    ```
-    erigon --chain=mumbai --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`.
+## Configure Erigon client
+
+If you want to store Erigon files in a non-default location, use `-datadir` to specify a new location:
 
-    ```makefile
-    erigon --chain=mumbai --bor.heimdall=<your heimdall url> --datadir=<your_data_dir>
-    ```
+```bash
+erigon --chain=mumbai --datadir=<your_data_dir>
+```
 
-    - If you want to connect to Polygon Mumbai Testnet use: [https://heimdall-api-testnet.polygon.technology](https://heimdall-api-testnet.polygon.technology)
+If you are not using local **heimdall**, use `-bor.heimdall=<your heimdall url>`. By default, it will try to connect to `localhost:1317`.
 
-    - For Polygon Mainnet: [https://heimdall-api.polygon.technology](https://heimdall-api.polygon.technology)
+```makefile
+erigon --chain=mumbai --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)
 
-**Note:** Remote heimdall is not recommended for production use, Only use it for testing purposes.
+    - For Polygon mainnet, use: [https://heimdall-api.polygon.technology](https://heimdall-api.polygon.technology)
 
-## Tips for Faster Sync
+!!! tip 
+
+    Remote heimdall is better suited for testing, and is not recommended for production use. 
+
+## Tips for faster sync
 
 - Use the machine with high IOPS and RAM for the faster initial sync
-- Memory optimized nodes are recommended for faster sync, For example, AWS EC2 `r5` or `r6` series instances.
+- Memory optimized nodes are recommended for faster sync. For example, AWS EC2 `r5` or `r6` series instances.
+
+## 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).

docs/pos/how-to/index.md

@@ -1,18 +1,6 @@
+Welcome to the Polygon PoS node how-tos section!
 
-Welcome to the Polygon PoS how-to section! 
-
-## Common tasks
-
-There are a number of guides here to help you get started with technical tasks like bridging assets from Ethereum to the Polygon PoS chain and vice-versa, smart contract development basics covering deployment and verification, messaging between Layer-1 (L1) and Layer-2 (L2) networks, etc. Check out the links listed below:
-
-* [Bridge tokens from Ethereum to PoS](bridging/ethereum-polygon/ethereum-to-matic.md)
-* [Bridge tokens from PoS to Ethereum](bridging/ethereum-polygon/matic-to-ethereum.md)
-* [L1 - L2 communication](bridging/l1-l2-communication/state-transfer.md)
-* [Work with smart contracts on PoS](smart-contracts/index.md)
-
-## Deploy, operate, and maintain nodes
-
-This section also contains guides that describe the system requirements and configurations necessary to spin up different kinds of Polygon nodes, and then take you step by step through the process of setting them up on the PoS network. 
+This section contains guides that describe the system requirements and configurations necessary to spin up different kinds of Polygon nodes, and then take you step by step through the process of setting them up on the PoS network. 
 
 Depending on the extent to which you're looking to participate in different network processes, and the kind of computational and network capabilities you can offer, you can choose to deploy any of the following nodes:
 
@@ -28,9 +16,3 @@ Depending on the extent to which you're looking to participate in different netw
 |        [Packages](validator/validator-packages.md)         |        [Packages](full-node/full-node-packages.md)         |             -              |      -       |
 |                             -                              |          [Docker](full-node/full-node-docker.md)           |             -              |      -       |
 |                             -                              |             [GCP](full-node/full-node-gcp.md)              |             -              |      -       |
-
-## Polygon DID
-
-Included in the section is an elaborate startup guide for users who wish to implement the Polygon DID, which is a three-part package consisting of an identity-registrar, identity-resolver, and identity-registry-contract.
-
-* [Polygon DID integration guide](./polygon-did.md)