Merge pull request 0xPolygon#163 from 0xPolygon/empieichO-docs-review

EmpieichO · web-flow · commit 65548355577e · 2024-01-19T17:07:40.000+02:00
Update zkEVM - Adding forkID info
diff --git a/docs/zkEVM/get-started/historical-data.md b/docs/zkEVM/get-started/historical-data.md
@@ -15,6 +15,8 @@ This update included a reduced number of RPC logs and aligned error messages to
 |     Prover      |                            v3.0.2                            |
 |     Bridge      |                            v0.3.1                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.4.4 |
+| Supported ForkIDs | Mainnet: ForkIDs 4, 5 & 6.  Testnet: ForkIDs 1, 2, 3, 4, 5 & 6. |
+
 
 
 
@@ -30,8 +32,9 @@ The changes made in this update were mainly in the node (Additional CORS header
 |     Prover      |                            v3.0.2                            |
 |     Bridge      |                            v0.3.0                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.4.1 |
+| Supported ForkIDs | Mainnet: ForkIDs 4, 5 & 6. Testnet: ForkIDs 1, 2, 3, 4, 5, 6. |
 
-Infrastructure partners were instructed to update, and then use instructions given here (https://polygontechnology.notion.site/Instructions-zkEVM-Mainnet-Node-v0-4-1-Prover-v3-0-2-7a585f394cd24b90b90283086276533c)
+Infrastructure partners were instructed to update, and then use instructions given [here](https://polygontechnology.notion.site/Instructions-zkEVM-Mainnet-Node-v0-4-1-Prover-v3-0-2-7a585f394cd24b90b90283086276533c).
 
 
 
@@ -47,6 +50,7 @@ This update brought several significant changes to zkEVM node, bridge, prover in
 |     Prover      |                            v3.0.2                            |
 |     Bridge      |                            v0.3.0                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.4.0 |
+| Supported ForkIDs | Mainnet: ForkIDs 4, 5 & 6. Testnet: ForkIDs 1, 2, 3, 4, 5, 6. |
 
 
 
@@ -62,6 +66,7 @@ The changes made in this update brought cryptographic optimisations and bug fixe
 |     Prover      |                            v3.0.0                            |
 |     Bridge      |                            v0.2.0                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.3 |
+| Supported ForkIDs | Mainnet: ForkIDs 4, 5 & 6. Testnet: ForkIDs 1, 2, 3, 4, 5 & 6. |
 
 
 
@@ -77,6 +82,7 @@ The changes made in this update were the node and prover versions, as well as up
 |     Prover      |                            v3.0.0                            |
 |     Bridge      |                            v0.2.0                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.3 |
+| Supported ForkIDs | Mainnet: ForkIDs 4, 5 & 6. Testnet: ForkIDs 1, 2, 3, 4, 5 & 6. |
 
 
 
@@ -92,6 +98,7 @@ The changes made in this upgrade were cryptographic optimisations and some bug f
 |     Prover      |                            v3.0.0                            |
 |     Bridge      |                            v0.2.0                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.2 |
+| Supported ForkIDs | Mainnet: ForkIDs 4, 5 & 6. Testnet: ForkIDs 1, 2, 3, 4, 5 & 6. |
 
 
 
@@ -107,6 +114,7 @@ The changes made in this update were new version updates of the prover and node.
 |     Prover      |                            v2.2.2                            |
 |     Bridge      |                            v0.2.0                            |
 | Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.1 |
+| Supported ForkIDs | Mainnet: ForkIDs 4 & 5. Testnet: ForkIDs 1, 2, 3, 4, & 5. |
 
 
 ### 20th Sep, 2023
diff --git a/docs/zkEVM/get-started/quick-start/bridge-to-zkevm.md b/docs/zkEVM/get-started/quick-start/bridge-to-zkevm.md
@@ -19,7 +19,7 @@ Follow this step-by-step guide on how to bridge assets from Ethereum to Polygon
 
 ![Figure: wallet](../../../img/zkEVM/zkv-zkwallet-1.jpg)
 
-- Click on the **Bridge** module to access the zkEVM environment.
+- Click on the Bridge wallet feature to access the zkEVM environment.
 
 - Set the amount of tokens to transfer from Ethereum network to zkEVM Mainnet (Or, from an Ethereum testnet to zkEVM testnet).
 
diff --git a/docs/zkEVM/get-started/quick-start/zkevm-faucet.md b/docs/zkEVM/get-started/quick-start/zkevm-faucet.md
@@ -12,18 +12,18 @@ The faucet allows anyone to request ETH testnet tokens, such as Sepolia testnet
 
 Here is how to use the Polygon zkEVM faucet:
 
-- Navigate to [**faucet.polygon.technology**](https://faucet.polygon.technology/)
+- Navigate to [`faucet.polygon.technology`](https://faucet.polygon.technology/)
 ![Figure: faucet-zk](../../../img/zkEVM/zkv-faucet-zketh.png)
 
-- Select the network where you want to receive the test tokens. In our case, we will select **Polygon zkEVM**.
+- Select the network where you want to receive the test tokens. In our case, we will select `Polygon zkEVM`.
 
-- Select the type of Testnet token that you want to receive. In our case, we only have the option to receive **zkEVM ETH** which is also the default option.
+- Select the type of Testnet token that you want to receive. In our case, we only have the option to receive `zkEVM ETH` which is also the default option.
 
-- Enter your **wallet address** (you can copy it from your MetaMask or any wallet that supports testnet tokens).
+- Enter your wallet address (you can copy it from your MetaMask or any wallet that supports testnet tokens).
 
-- Click on the **Submit** button to send your token request.
+- Click on the `Submit` button to send your token request.
 
-- Click **Confirm** to finalize the transaction.
+- Click `Confirm` to finalize the transaction.
 
 ![Figure: confirm-tx](../../../img/zkEVM/zkv-confirm-zketh.png)
 
diff --git a/docs/zkEVM/overview.md b/docs/zkEVM/overview.md
@@ -1,22 +1,22 @@
 Polygon zkEVM is a Layer 2 network of the Ethereum Virtual Machine (EVM), a zero-knowledge (ZK) rollup scaling solution. Polygon zkEVM uses a cryptographic primitive called a ZK proof to validate state transitions.
 
-Polygon zkEVM is compatible with the EVM, supporting the majority of Ethereum EIPs, pre-compiles, and opcodes. Developers benefit from the seamless deployment of smart contracts, developer tools, and wallets that already work on Ethereum, but in an environment with significantly lower costs. 
+Polygon zkEVM is EVM-equivalent. It supports the majority of Ethereum EIPs, precompiles, and opcodes. Developers benefit from the seamless deployment of smart contracts, developer tools, and wallets that already work on Ethereum, but in an environment with significantly lower costs.
 
 
 ## Protocol development highlights
 
-The testnet for Polygon zkEVM launched with a complete ZK proving system and full transaction data availability in October 2022. The proving system for Polygon zkEVM uses a combination of eSTARK proofs and FRI that are then compressed using FFLONK SNARKs to create the final ZK proof.
+The Polygon zkEVM testnet launched with a complete ZK proving system and full transaction data availability in October 2022. The proving system uses a combination of eSTARK proofs and FRI, that are then compressed using FFLONK SNARKs to create the final ZK proof.
 
 Following the launch of the testnet, the code base for Polygon zkEVM underwent several security audits. These were among the first audits ever performed on a complete, in-production ZK proving system. 
 
 After the audits, Polygon zkEVM Mainnet Beta [launched in March 2023](https://www.youtube.com/watch?v=UvQIX5i09A4&ab_channel=ETHGlobal). Since then, the zkEVM network has had two major upgrades: [Dragon Fruit (ForkID5)](https://polygon.technology/blog/polygon-zkevm-dragon-fruit-upgrade-with-new-opcode-coming-to-mainnet-beta), in September 2023, and [Inca Berry (ForkID6)](https://polygon.technology/blog/polygon-zkevm-inca-berry-upgrade-coming-to-mainnet-beta), in November 2023.
 
 ## Security measures
 
-The security measures taken by the zkEVM team for an upgrade are on par with Ethereum's security standards as they involve the deployment of:
+zkEVM's upgrades are on par with Ethereum's security standards as they involve deployment of the following contracts:
 
-- An admin multisig contract to avoid having one account controlling upgrades,
-- A timelock contract to give users sufficient time delay to withdraw before execution, and
+- An admin multisig contract to avoid having one account controlling upgrades.
+- A timelock contract to give users sufficient time delay to withdraw before execution.
 - A transparent upgradeable proxy, from OpenZeppelin’s libraries of audited and battle-tested contracts.
 
 The activation of the 10-day timelock for upgrading zkEVM's smart contracts on Ethereum requires approval by the network's [Admin](https://etherscan.io/address/0x242daE44F5d8fb54B198D03a94dA45B5a4413e21), a three-participant multisig that acts as a [governance tool](https://wiki.polygon.technology/docs/zkevm/protocol/admin-role/#:~:text=Governance%20of%20zKEVM%20Contracts%E2%80%8B&text=sol%20contract%20instance%20is%20assigned,of%20Polygon%20zkEVM%20L1%20contracts.) for the protocol. This is a Gnosis Safe with a 2/3 threshold.
