Merge pull request 0xPolygon#634 from 0xPolygon/dev-tools-pos-update

hsutaiyu · web-flow · commit 47cd4c216f88 · 2024-08-07T18:06:40.000+04:00
Dev tools + PoS update
diff --git a/docs/pos/concepts/transactions/meta-transactions.md b/docs/pos/concepts/transactions/meta-transactions.md
@@ -95,11 +95,11 @@ For any action that requires blockchain interaction,
     Steps:
 
     1. Let's register our contracts to Biconomy dashboard
-       1. Visit [Biconomy's offical docs](https://docs.biconomy.io/dashboard)
-       2. Navigate and login to the Dashboard
-       3. Select `Polygon Mumbai` when registering your dapp
-    2. Copy the`API key` to use for you dapp's frontend
-    3. And Add function `executeMetaTransaction` in Manage-Api and make sure to enable meta-tx. (Check 'native-metatx' option)
+       1. Visit [Biconomy's offical docs](https://docs.biconomy.io/dashboard).
+       2. Navigate and login to the Dashboard.
+       3. Select **Polygon Amoy Testnet** when registering your dApp.
+    2. Copy the API key to use for you dApp's frontend.
+    3. And add function `executeMetaTransaction` in **Manage-Api** and make sure to enable meta-tx (Check **native-metatx** option).
 
   - If you'd like to use your own custom API that sends signed transactions on the blockchain, you can refer to the server code here: [https://github.com/angelagilhotra/ETHOnline-Workshop/tree/master/2-network-agnostic-transfer](https://github.com/angelagilhotra/ETHOnline-Workshop/tree/master/2-network-agnostic-transfer)
 
diff --git a/docs/pos/how-to/bridging/ethereum-polygon/ethereum-to-matic.md b/docs/pos/how-to/bridging/ethereum-polygon/ethereum-to-matic.md
@@ -151,7 +151,7 @@ let receiver = new matic.eth.Contract(JSON.parse(receiverABI), receiverAddress)
 
 We're using `@maticnetwork/meta` package for the RPCs, the package isn't a requirement to run the script.
 
-`matic` and `main` objects refer to the web3 object initialized with Polygon's and Ropsten's RPC respectively.
+`matic` and `main` objects refer to the web3 object initialized with Polygon Amoy and Sepolia network's respective RPC URLs.
 
 `sender` and `receiver` objects refer to the contract objects of `Sender.sol` and `Receiver.sol` that we deployed in Step 1 and 2.
 
diff --git a/docs/pos/how-to/troubleshoot/technical-faqs.md b/docs/pos/how-to/troubleshoot/technical-faqs.md
@@ -176,7 +176,7 @@ and start Heimdall services again. You can refer to this [guide](../validator/pr
 
 ### 5. From where do I create the API key?
 
-You can access this link: [https://infura.io/register](https://infura.io/register) . Make sure that once you have setup your account and project, you copy the API key for Ropsten and not Mainnet.
+You can access this link: [https://infura.io/register](https://infura.io/register) . Make sure that once you have setup your account and project, you copy the API key for Sepolia and not mainnet.
 
 Mainnet is selected by default.
 
diff --git a/docs/tools/dApp-development/launchpad/commands.md b/docs/tools/dApp-development/launchpad/commands.md
@@ -37,7 +37,7 @@ The `dev` command starts
 
 | Option                               | Description                                                                                                                                                                                                    |
 |--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| -n, --fork-network-name [NAME]       | Name of the network to fork; optional. By default, it starts a new chain from genesis block. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet")             |
+| -n, --fork-network-name [NAME]       | Name of the network to fork; optional. By default, it starts a new chain from genesis block. (choices: "ethereum", "goerli", "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet")             |
 | -b, --fork-block-num [number]        | Block number to fork at. By default, it's the latest block.                                                                                                                                                    |
 | -r, --reset-on-change                | Resets the entire local blockchain when any code is changed; for forked mode, it resets back to forked block number; NOT DEFAULT.                                                                              |
 | --only-smart-contracts               | Deploys only smart contracts (having started local test chain) and updates Smart contract configs for frontend; does not start frontend dev environment.                                                       |
@@ -66,7 +66,7 @@ dapp-launchpad deploy -n CHAIN_NAME
 
 |        Option         |        Description         |
 |:----------------------:|:-------------------------------------------------------|
-| -n, --network-name     | Name of the network to deploy smart contracts to. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet")               |
+| -n, --network-name     | Name of the network to deploy smart contracts to. (choices: "ethereum", "goerli", "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet")               |
 | --only-smart-contracts | Deploys only smart contracts and updates Smart contracts config for frontend.                                                                                         |
 | --only-frontend        | Deploys only frontend; smart contracts data is read from Smart contracts config which must pre-exist. To generate these manually, use generate smart-contracts-config |
 | -h, --help             | Display help for command                                                                                                                                              |
@@ -114,5 +114,5 @@ dapp-launchpad generate smart-contracts-config
 |          Option         |                         Description      |
 |:-----------------------:|:-----------------------------------------|
 | -e, --environment <ENV> | Environment where this config would be used (choices: "development", "production", default: "development")                                        |
-| -n, --network-name      | Name of the network to generate config for. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet") |
+| -n, --network-name      | Name of the network to generate config for. (choices: "ethereum", "goerli", "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet") |
 | -h, --help              | Display help for command                  |
diff --git a/docs/tools/dApp-development/launchpad/common-pitfalls.md b/docs/tools/dApp-development/launchpad/common-pitfalls.md
@@ -2,16 +2,22 @@
 comments: true
 ---
 
-## MetaMask transactions fail with a nonce error in dev environment 
+### MetaMask transactions fail with a nonce error in dev environment 
 
 Every time the dev environment starts, a new local test chain is started. Metamask maintains a cache of "latest block number" and "account transaction nonce". Since every run of `dev` creates a new chain, it never matches with this cache.
 
 To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
 
-## MetaMask transactions fail with a nonce error when using the **reset on change** option in dev environment
+### MetaMask transactions fail with a nonce error when using the **reset on change** option in dev environment
 
 The reset on change option resets the blockchain on every code change. 
 
 MetaMask maintains a cache of *latest block number* and *account transaction nonce*. After resetting the chain, the latest block number and account transaction nonce should go back to the initial state as well, but MetaMask does not update this cache on its own.
 
 To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
+
+### Error: `could not coalesce error (error={ "code": -32603, "message": "Internal JSON-RPC error." })`
+
+Clear your wallet cache and try again.
+
+To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
diff --git a/docs/tools/dApp-development/launchpad/quickstart.md b/docs/tools/dApp-development/launchpad/quickstart.md
@@ -107,7 +107,7 @@ The chain name options are in this section of the help output:
 -n, --fork-network-name [NAME]        Name of the network to fork; optional. 
                                         By default, it starts a new
                                         chain from genesis block. (choices: "ethereum", "goerli",
-                                        "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet")
+                                        "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet")
 ```
 
 To fork Polygon zkEVM, for example, run the following command:
diff --git a/docs/tools/data/covalent.md b/docs/tools/data/covalent.md
@@ -9,22 +9,21 @@
 
 ## Supported endpoints
 
-All [__Class A__](https://www.covalenthq.com/docs/api/#tag--Class-A) endpoints are supported for the Matic mainnet and the Mumbai testnet. You can query either network via the unified API by changing the `chainId`.
+All [__Class A__](https://www.covalenthq.com/docs/api/#tag--Class-A) endpoints are supported for the Matic mainnet and the Amoy testnet. You can query either network via the unified API by changing the `chainName`.
 
 !!! info "Endpoints"
 
     A full list of all the requests you are able to do on the Polygon network using Covalent are available on the [Covalent API documentation](https://www.covalenthq.com/docs/api/).
 
 ## Appendix
 
-### Matic gas token
+### MATIC gas token
 
-To interact with the Matic network, MATIC tokens are required to pay as gas fees. Covalent's
-responses automatically returns `gas_*` fields in the MATIC units.
+To interact with Polygon network, MATIC tokens are required to pay gas fees. Covalent's responses automatically return `gas_*` fields in MATIC units.
 
 ### Token mapping
 
-Covalent maintains an on-chain real-time mapping of token addresses between the Ethereum mainnet and the Matic chain. These addresses are used to reverse-lookup prices on Matic and also to return the right token logo URLs.
+Covalent maintains an on-chain real-time mapping of token addresses between the Ethereum mainnet and Polygon. These addresses are used to reverse-lookup prices on MATIC and also to return the right token logo URLs.
 
 Some example of mapped tokens:
 
diff --git a/docs/tools/data/subquery.md b/docs/tools/data/subquery.md
@@ -4,11 +4,11 @@
 
 ## Intro
 
-SubQuery is a leading blockchain data indexer that provides developers with fast, flexible, universal, open source and decentralised APIs for web3 projects. SubQuery SDK allows developers to get rich indexed data and build intuitive and immersive decentralised applications in a faster and more efficient way. SubQuery supports 100+ ecosystems including Polygon, Polygon zkEVM, Polygon Mumbai, Ethereum, Polkadot, Algorand, NEAR, and Avalanche.
+SubQuery is a leading blockchain data indexer that provides developers with fast, flexible, universal, open source and decentralised APIs for web3 projects. SubQuery SDK allows developers to get rich indexed data and build intuitive and immersive decentralised applications in a faster and more efficient way. SubQuery supports 100+ ecosystems including Polygon, Polygon zkEVM, Polygon Amoy, Ethereum, Polkadot, Algorand, NEAR, and Avalanche.
 
 Another one of SubQuery's competitive advantages is the ability to aggregate data not only within a chain but across multiple blockchains all within a single project. This allows the creation of feature-rich dashboard analytics and multi-chain block scanners.
 
-Other advantages include superior performance with multiple RPC endpoint configurations, multi-worker capabilities and a configurable caching architecture. To find out more, visit our [documentation](https://academy.subquery/).
+Other advantages include superior performance with multiple RPC endpoint configurations, multi-worker capabilities and a configurable caching architecture. To find out more, visit our [documentation](https://academy.subquery.network/).
 
 **Useful resources**:
 
diff --git a/docs/tools/matic-js/advanced/abi-manager.md b/docs/tools/matic-js/advanced/abi-manager.md
@@ -34,7 +34,7 @@ The network name, contract name, bridge name etc can be taken from our [official
 import { ABIManager } from '@maticnetwork/maticjs'
 
 
-const manager = new ABIManager('testnet','mumbai');
+const manager = new ABIManager('testnet','amoy');
 await manager.init();
 
 // set abi
diff --git a/docs/tools/matic-js/advanced/exit-util.md b/docs/tools/matic-js/advanced/exit-util.md
@@ -21,7 +21,7 @@ const client = new Web3SideChainClient<any>();
 await client.init({
     // log: true,
     network: 'testnet',
-    version: 'mumbai',
+    version: 'amoy',
     parent: {
         provider: new HDWalletProvider(privateKey, RPC.parent),
         defaultConfig: {
@@ -66,7 +66,7 @@ use(Web3ClientPlugin);
 const posClient = new POSClient();
 await posClient.init({
     network: 'testnet',
-    version: 'mumbai',
+    version: 'amoy',
     parent: {
       provider: new HDWalletProvider(privateKey, mainRPC),
       defaultConfig: {
diff --git a/docs/tools/matic-js/pos/client.md b/docs/tools/matic-js/pos/client.md
@@ -18,7 +18,7 @@ use(Web3ClientPlugin);
 const posClient = new POSClient();
 await posClient.init({
     network: 'testnet',
-    version: 'mumbai',
+    version: 'amoy',
     parent: {
       provider: new HDWalletProvider(privateKey, mainRPC),
       defaultConfig: {
@@ -39,13 +39,13 @@ After the `POSClient` is initiated, we can work with token types, such as `erc20
 
 ### ERC20
 
-**Create erc20 child token**
+#### Create ERC20 child token
 
 ```js
 const erc20ChildToken = posClient.erc20(<token address>);
 ```
 
-**Create erc20 parent token**
+#### Create ERC20 parent token
 
 ```js
 const erc20ParentToken = posClient.erc20(<token address>, true);
diff --git a/docs/tools/matic-js/setup/ethers.md b/docs/tools/matic-js/setup/ethers.md
@@ -41,7 +41,7 @@ const childProvider = new providers.JsonRpcProvider(rpc.child);
 const posClient = new POSClient();
 await posClient.init({
     network: 'testnet',
-    version: 'mumbai',
+    version: 'amoy',
     parent: {
       provider: new Wallet(privateKey, parentProvider),
       defaultConfig: {
diff --git a/docs/tools/matic-js/setup/web3js.md b/docs/tools/matic-js/setup/web3js.md
@@ -37,7 +37,7 @@ use(Web3ClientPlugin);
 const posClient = new POSClient();
 await posClient.init({
     network: 'testnet',
-    version: 'mumbai',
+    version: 'amoy',
     parent: {
       provider: new HDWalletProvider(privateKey, mainRPC),
       defaultConfig: {
diff --git a/docs/tools/oracles/razor.md b/docs/tools/oracles/razor.md
@@ -8,6 +8,6 @@ The core of Razor Network is a set of smart contracts that can run on any Ethere
 
 ## Usage
 
-This oracle network is currently running on the Polygon Mumbai testnet. To get started with connecting to the data feed, check out this **[tutorial](https://docs.razor.network/)**.
+This oracle network is currently running on the Polygon mainnet and testnet. To get started with connecting to the data feed, check out this **[tutorial](https://docs.razor.network/)**.
 
 The Razor Network can be explored using [Razorscan](https://razorscan.io/).
diff --git a/docs/tools/storage/crusthelpers.md b/docs/tools/storage/crusthelpers.md
@@ -5,11 +5,8 @@
 
 The protocol matches people who have hard drive space to spare with those who need to store data or host content. Crust supports most smart contract platforms with its cross-chain solution, including Polygon. Find out all the platforms that Crust storage supports on their [official website](https://crust.network/).
 
-:::info Learn more about Crust Network
-
-Check out the **[Decentralized Storage Market](https://wiki.crust.network/docs/en/DSM)** and **[Cross-chain Storage Solution](https://wiki.crust.network/docs/en/buildCrossChainSolution#ii-native-ipfs-integration)** offered by Crust Network. Also, you can start building with **[Crust Build-101](https://wiki.crust.network/docs/en/build101)**.
-
-:::
+!!! info "Learn more about Crust Network"
+    Check out the **[Decentralized Storage Market](https://wiki.crust.network/docs/en/DSM)** and **[Cross-chain Storage Solution](https://wiki.crust.network/docs/en/buildCrossChainSolution#ii-native-ipfs-integration)** offered by Crust Network. Also, you can start building with **[Crust Build-101](https://wiki.crust.network/docs/en/build101)**.
 
 ## Crust storage helpers
 
diff --git a/docs/tools/wallets/walletconnect.md b/docs/tools/wallets/walletconnect.md
@@ -26,21 +26,21 @@ import Web3 from "web3"
 import Matic from "maticjs"
 ```
 
-Next, set up Polygon and Ropsten provider via WalletConnect’s object:
+Next, set up Polygon and Sepolia provider via WalletConnect’s object:
 
 ```javascript
 const maticProvider = new WalletConnectProvider(
   {
-    host: `https://rpc-mumbai.matic.today`,
+    host: `https://rpc-amoy.polygon.technology`,
     callbacks: {
       onConnect: console.log('connected'),
       onDisconnect: console.log('disconnected!')
     }
   }
 )
 
-const ropstenProvider = new WalletConnectProvider({
-  host: `https://ropsten.infura.io/v3/70645f042c3a409599c60f96f6dd9fbc`,
+const sepoliaProvider = new WalletConnectProvider({
+  host: `https://ethereum-sepolia-rpc.publicnode.com`,
   callbacks: {
     onConnect: console.log('connected'),
     onDisconnect: console.log('disconnected')
@@ -52,7 +52,7 @@ We created the above two provider objects to instantiate our Web3 object with:
 
 ```js
 const maticWeb3 = new Web3(maticProvider)
-const ropstenWeb3 = new Web3(ropstenProvider)
+const sepoliaWeb3 = new Web3(sepoliaProvider)
 ```
 
 ## Instantiating contracts
