Mainnet basic data (#611)

Maar-io · Mar.io · andabak · web-flow · commit b6047254c835 · 2024-02-28T09:58:58.000+01:00
* mainnet basic data

* Update bridge-to-zkevm.md

generalize to any wallet

* Update bridge-to-zkevm.md

---------

Co-authored-by: Mar.io &lt;mario@stake.co.jp&gt;
Co-authored-by: Ivan &lt;95318860+andabak@users.noreply.github.com&gt;
diff --git a/docs/build/zkEVM/bridge-to-zkevm.md b/docs/build/zkEVM/bridge-to-zkevm.md
@@ -15,15 +15,18 @@ import walletselect from '/docs/build/zkEVM/img/wallet-select.jpg'
 
 ## Overview
 
-Here you will find information about how to bridge assets to the Astar zkEVM. Presently, there are two options for bridging assets to the zkEVM: 
+Here you will find information about how to bridge assets to the Astar zkEVM, both to **zKatana testnet** and to **Astar zkEVM mainnet**. Presently, there are two options for bridging assets to the zkEVM:
 
 1. Ethereum L1 to Astar zkEVM -> Bridged ETH is the native token required for testing and deployment of dApps on the Astar zkEVM, so before using the network, developers need to bridge some ETH from Layer 1 to Layer 2. Accessible through the Astar Portal, which can take approximately 10-30 minutes, depending on network usage.
 2. _Astar Parachain to Astar zkEVM (currently under development) -> A 3rd-party asset bridge or message network facilitating locking and minting of synthetic (wrapped) assets between Astar Substrate EVM and Astar zkEVM. See the [integrations section](/docs/build/zkEVM/integrations/bridges-relays/) for more information about how to use 3rd-party bridge services and compatible assets._
 
 ### Transfer ETH using the Astar Portal
 
-Visit the [Astar Portal](https://portal.astar.network) and connect MetaMask. 
+Visit the [Astar Portal](https://portal.astar.network) and connect your wallet.
 
+:::note
+This example is using MetaMask wallet and examples are with for the testnet but same applies for the mainnet.
+:::
 
 <div style={{textAlign: 'center'}}>
   <img src={walletselect} style={{width: 400}} />
@@ -38,15 +41,15 @@ Use the network selector and switch to zKatana network, or allow MetaMask to swi
   </div>
 
 
-Click on the Bridge tab on the left-hand side. Ensure Sepolia is selected as Bridge source, and zKatana is selected as destination. After you have entered the amount of ETH to transfer, press the Confirm button. 
+Click on the Bridge tab on the left-hand side. Ensure Sepolia is selected as Bridge source, and zKatana is selected as destination. After you have entered the amount of ETH to transfer, press the Confirm button.
 
 
 <div style={{textAlign: 'center'}}>
   <img src={bridge2} style={{width: 1000}} />
   </div>
 
 
-Sign the MetaMask transaction. 
+Sign the MetaMask transaction.
 
 :::note
 Once the transaction shows as confirmed on the MetaMask Activity tab, it will take approximately 5-10 minutes for the Astar Portal and MetaMask to update your balance on the zKatana network side.
diff --git a/docs/build/zkEVM/fee.md b/docs/build/zkEVM/fee.md
@@ -30,9 +30,36 @@ curl https://rpc.zkatana.gelato.digital/ \
   The result is the hex value of the gas price in wei.
 
 ## Use Blockscout Price Oracle
-Blockscout Price Oracle calculates the gas price from the average of previous blocks. It doesn't call `eth_gasPrice`. 
+Blockscout Price Oracle calculates the gas price from the average of previous blocks. It doesn't call `eth_gasPrice`.
+
 <Tabs>
-<TabItem value="testnet" label="zKatana testnet" default>
+<TabItem value="Mainnet" label="Astar zkEVM" default>
+
+Send a GET request to the [Blockscout Price Oracle endpoint](https://astar-zkevm.explorer.startale.com/api/v1/gas-price-oracle) to get a gas price recommendation from this oracle.
+
+#### cURL
+
+```bash
+curl https://astar-zkevm.explorer.startale.com/api/v1/gas-price-oracle
+```
+
+#### JavaScript
+
+```javascript
+fetch('https://astar-zkevm.explorer.startale.com/api/v1/gas-price-oracle')
+  .then(response => response.json())
+  .then(json => console.log(json))
+```
+
+#### Python
+
+```python
+import requests
+requests.get('https://astar-zkevm.explorer.startale.com/api/v1/gas-price-oracle').json()
+```
+</TabItem>
+
+<TabItem value="testnet" label="zKatana testnet">
 
 Send a GET request to the [Blockscout Price Oracle endpoint](https://zkatana.blockscout.com/api/v1/gas-price-oracle) to get a gas price recommendation from this oracle.
 
@@ -56,10 +83,6 @@ fetch('https://zkatana.blockscout.com/api/v1/gas-price-oracle')
 import requests
 requests.get('https://zkatana.blockscout.com/api/v1/gas-price-oracle').json()
 ```
-
-</TabItem>
-<TabItem value="Mainnet" label="Astar zkEVM">
-coming soon...
 </TabItem>
 
 </Tabs>
@@ -70,9 +93,9 @@ An example JSON response from Blockscout Price Oracle will look like this:
 
 ```json
 {
-    "average":0.02,
-    "fast":0.02,
-    "slow":0.02,
+    "average":3.02,
+    "fast":3.02,
+    "slow":3.02,
 }
 ```
 
diff --git a/docs/build/zkEVM/quickstart.md b/docs/build/zkEVM/quickstart.md
@@ -20,40 +20,39 @@ Solidity developers are right at home on Astar zkEVM. Simply switch to the zkEVM
 No special tools or wallets are required to build or interact with Astar zkEVM.
 :::
 
-Developers can deploy existing contracts from other EVM chains to the zkEVM, and users are able to deposit assets from Ethereum to transact on the zkEVM in batches, which are ultimately finalized through novel use of zero-knowledge proofs. Native account abstraction means developers can craft user interfaces that are more intuitive and web2-like, that eliminate complexity and drastically simplify the onboarding process. 
+Developers can deploy existing contracts from other EVM chains to the zkEVM, and users are able to deposit assets from Ethereum to transact on the zkEVM in batches, which are ultimately finalized through novel use of zero-knowledge proofs. Native account abstraction means developers can craft user interfaces that are more intuitive and web2-like, that eliminate complexity and drastically simplify the onboarding process.
 
 ## Connecting to zkEVM
 
 :::info Reminder
-**Astar zKatana testnet and its related documentation are under active development.** 
+**Astar zKatana testnet and its related documentation are under active development.**
 
 All feedback is welcome and highly appreciated, so please report errors or inconsistencies to a team member or as an issue on the [Astar Docs Github repo](https://github.com/AstarNetwork/astar-docs/issues), thank you.
 :::
 
 To add the **Astar zkEVM** network to your wallet manually, enter the following details :
 <Tabs>
-<TabItem value="testnet" label="zKatana Testnet" default>
+<TabItem value="mainnet" label="Astar zkEVM Mainnet" default>
+| RPC URL | ChainID | Block Explorer URL | Currency |
+| ------------------------------- | ---------------- | ---------------- | ----- |
+| `https://rpc.startale.com/astar-zkevm` | `3776` | [https://astar-zkevm.explorer.startale.com/](https://astar-zkevm.explorer.startale.com/) | **ETH** | []
+</TabItem>
 
+<TabItem value="testnet" label="zKatana Testnet">
 | RPC URL | ChainID | Block Explorer URL | Currency |
 | ------------------------------- | ---------------- | ---------------- | ----- |
 | `https://rpc.startale.com/zkatana` | `1261120` | [https://zkatana.explorer.startale.com/](https://zkatana.explorer.startale.com/) | **ETH** |
 | `https://rpc.zkatana.gelato.digital` | `1261120` | [https://zkatana.blockscout.com/](https://zkatana.blockscout.com/) | **ETH** |
 | `https://astar-zkatana-rpc.dwellir.com` | `1261120` | | **ETH** |
 </TabItem>
 
-<TabItem value="mainnet" label="Astar zkEVM Mainnet" disabled>
-
-| RPC URL | ChainID | Block Explorer URL | Currency |
-| ------------------------------- | ---------------- | ---------------- | ----- |
-| `coming soon...` | `-` | `-` | **ETH** |
-</TabItem>
 </Tabs>
 
 To add the network to MetaMask, use the data above or the link at the bottom of the respective block explorer page.
 
 ## Bridging Assets
 
-The next step is to [bridge assets](/docs/build/zkEVM/bridge-to-zkevm.md) from Ethereum &rarr; Astar zkEVM. 
+The next step is to [bridge assets](/docs/build/zkEVM/bridge-to-zkevm.md) from Ethereum &rarr; Astar zkEVM.
 
 :::important
 Astar's canonical [zkEVM Bridge](https://portal.astar.network) does not inherit any counterparty risk compared to 3rd party bridge services, and is trustless at the protocol level.
@@ -65,7 +64,7 @@ The development experience on zkEVM is seamless and identical to the Ethereum Vi
 
 ## Astar zkEVM Support for Developers
 
-Developers requiring support can open an issue on [Ethereum StackExchange](https://ethereum.stackexchange.com/) and tag it with `Astar` (preferred) or join the [Astar Discord server](https://discord.gg/astarnetwork). 
+Developers requiring support can open an issue on [Ethereum StackExchange](https://ethereum.stackexchange.com/) and tag it with `Astar` (preferred) or join the [Astar Discord server](https://discord.gg/astarnetwork).
 
 <details>
 <summary>Ethereum StackExchange</summary>
diff --git a/docs/build/zkEVM/smart-contracts/using-hardhat.md b/docs/build/zkEVM/smart-contracts/using-hardhat.md
@@ -23,9 +23,9 @@ To create the sample project, run `npx hardhat init` in your project folder:
 <Figure src={require('/docs/build/zkEVM/smart-contracts/img/hardhat-init.png').default} width="100%" />
 
 - **Press** `<ENTER>` choose javascript, typescript or empty project
-- **Press** `<ENTER>` to set the project root 
+- **Press** `<ENTER>` to set the project root
 - **Press** `<ENTER>` again to accept addition of `.gitignore`
-- **Press** `<ENTER>` to install `hardhat @nomicfoundation/hardhat-toolbox` 
+- **Press** `<ENTER>` to install `hardhat @nomicfoundation/hardhat-toolbox`
 
 ## Create deployer account
 - Create the `.env` file in your project root folder and add the following line:
@@ -75,6 +75,10 @@ Verify that your .gitignore file contains `.env` to prevent your private key fro
             url: `https://rpc.zkatana.gelato.digital`,
             accounts: [process.env.ACCOUNT_PRIVATE_KEY],
             },
+            astarZkEvm: {
+            url: `https://rpc.startale.com/astar-zkevm`,
+            accounts: [process.env.ACCOUNT_PRIVATE_KEY],
+            },
         },
     };
 ```
@@ -100,6 +104,10 @@ Verify that your .gitignore file contains `.env` to prevent your private key fro
             url: `https://rpc.zkatana.gelato.digital`,
             accounts: [ACCOUNT_PRIVATE_KEY]
             },
+            astarZkEvm: {
+            url: `https://rpc.startale.com/astar-zkevm`,
+            accounts: [process.env.ACCOUNT_PRIVATE_KEY],
+            },
         },
     };
 
diff --git a/docs/build/zkEVM/smart-contracts/verify-smart-contract.md b/docs/build/zkEVM/smart-contracts/verify-smart-contract.md
@@ -7,7 +7,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import Figure from '/src/components/figure'
 
-Once a smart contract is deployed to zKatana testnet, it can be verified in various ways depending on the framework of deployment as well as the complexity of the contract. The aim here is to use examples to illustrate how you can manually verify a deployed smart contract. 
+Once a smart contract is deployed to zKatana testnet, it can be verified in various ways depending on the framework of deployment as well as the complexity of the contract. The aim here is to use examples to illustrate how you can manually verify a deployed smart contract.
 
 Ensure that your wallet is connected while following this guide. We will use Metamask wallet throughout this tutorial.
 For detailed explanation on how to verify smart contracts, please refer to the [Blockscout documentation](https://docs.blockscout.com/for-developers/verify-contracts).
@@ -16,9 +16,9 @@ For detailed explanation on how to verify smart contracts, please refer to the [
 
 After successfully compiling a smart contract, follow the next steps to verify your smart contract.
 
-1. Copy the **Address** to which the smart contract is deployed. 
+1. Copy the **Address** to which the smart contract is deployed.
 
-2. Navigate to the [zKatana Explorer](https://zkatana.blockscout.com) and paste the contract address into the Search box. This opens a window with a box labelled **Contract Details**.
+2. Navigate to the [block Explorer](docs/build/zkEVM/quickstart.md) and paste the contract address into the Search box. This opens a window with a box labelled **Contract Details**.
 
 3. Scroll down to the box with tabs labelled - **Transactions**, **Token transfers** **Internal txns**, **Coin Balance History**, and **Contract**.
 
@@ -30,10 +30,10 @@ After successfully compiling a smart contract, follow the next steps to verify y
 
 ### Solidity, Flattened Source Code
 
-1. Click **Next** after selecting the **via Flattened Source Code** option. 
-2. In order to update the **Compiler** based on your contract's compiler version, 
+1. Click **Next** after selecting the **via Flattened Source Code** option.
+2. In order to update the **Compiler** based on your contract's compiler version,
 
-    - Click the &#8595; for a list of compiler versions. 
+    - Click the &#8595; for a list of compiler versions.
 
     - Select the corresponding version. For example, select `v0.8.9+commit.e5eed63a` if your code has `pragma solidity ^0.8.9;`.
 3. Select the Optimization option based on your contract's optimization settings.
@@ -47,7 +47,7 @@ In order to flatten the contract code with Hardhat, one needs to only run the fo
 npx hardhat flatten
 ```
 The result will be printed to stdout. You can create a file with the flattened sources using the `>` redirection operator:
-    
+
 ```bash
 npx hardhat flatten > flattened.sol
 ```
@@ -63,7 +63,7 @@ After selecting **Flatten**, a new `.sol` file with the suffix `_flatten.sol` is
 </TabItem>
 
 <TabItem value="foundry" label="Foundry">
-In order to flatten the code using Foundry, the following command can be used: 
+In order to flatten the code using Foundry, the following command can be used:
 
 ```bash
 forge flatten src/<Contract-Name> -o <Any-Name-For-Flattened-Code>.sol
@@ -80,9 +80,9 @@ Select the Optimization option based on your contract's optimization settings.
 
 Click **Next** after selecting the **via Standard JSON Input** option.
 
-1. In order to update the **Compiler** based on your contract's compiler version, 
+1. In order to update the **Compiler** based on your contract's compiler version,
 
-    - Click the &#8595; for a list of compiler versions. 
+    - Click the &#8595; for a list of compiler versions.
 
     - Select the corresponding version. For example, select `v0.8.9+commit.e5eed63a` if your code has `pragma solidity ^0.8.9;`.
 
