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

EmpieichO · web-flow · commit 787f2bda5c25 · 2024-08-20T20:42:22.000+02:00
zkEVM - edit main-overview doc
diff --git a/docs/zkEVM/architecture/index.md b/docs/zkEVM/architecture/index.md
@@ -97,9 +97,7 @@ The smart contract, therefore, makes two calls:
     
     Although the current protocol design allows for several sequencers and aggregators, to prioritize security and given the early stage of protocol development, only one sequencer and one aggregator are currently operational.
 
-    These are henceforth referred to as the _trusted sequencer_ and the _trusted aggregator_. 
-
-<!-- ### Tokenomics -->
+    These are henceforth referred to as the _trusted sequencer_ and the _trusted aggregator_.
 
 ## zkNode
 
@@ -232,35 +230,3 @@ To do so, users need to deposit Ether to L2 through the [Polygon Portal](https:/
 The above process is a summarized version of how transactions are processed in Polygon zkEVM. 
 
 Take a look at the complete description in the [transaction life cycle](protocol/transaction-life-cycle/submit-transaction.md) document.
-
-## Design characteristics
-
-The Polygon zkEVM network is secure, efficient, and comes with verifiable block data.
-
-Development efforts aim at permissionless-ness, that is, allowing anyone with the zkEVM software to participate in the network. For instance, the consensus algorithm could give anyone the opportunity to be an aggregator.
-
-Data availability is most crucial for decentralization, where every user has sufficient data needed to rebuild the full state of a rollup. As a rollup, Polygon zkEVM posts all transaction data and validity proof on Ethereum.
-
-The aim is to ensure that there is no censorship and that no one party can control the network. For this reason, mechanisms such as [force batches](protocol/malfunction-resistance/sequencer-resistance.md) and [force verification](protocol/malfunction-resistance/aggregator-resistance.md) have been activated.
-
-Polygon zkEVM was designed with security in mind. As an L2 solution, it inherits its security from Ethereum.
-
-Smart contracts are deployed to ensure that everyone who executes state changes does so appropriately, creates a proof that attests to the validity of a state change, and makes validity proofs available on-chain for verification.
-
-## Efficiency and overall strategy
-
-Efficiency is key to network performance. Polygon zkEVM uses several implementation strategies to maximize efficiency. A few are listed below:
-
-1. The first strategy is to deploy the consensus contract, which incentivizes the aggregator to participate in the proof generation process.
-
-2. The second strategy is to carry out all computations off-chain while keeping only the necessary data and zk-proofs on-chain.
-
-3. The bridge smart contract's implementation is made efficient by only using Merkle roots of exit trees.
-
-4. Utilization of specialized cryptographic primitives within the zkProver in order to speed up computations and minimize proof sizes, as seen in:
-    
-    - Running a special zero-knowledge assembly language (zkASM) for interpretation of bytecode.
-
-    - Using zero-knowledge tools such as zk-STARKs for proving purposes; these proofs are very fast though they are big in size.
-
-    - Instead of publishing the sizeable zk-STARK proofs as validity proofs, a zk-SNARK is used to attest to the correctness of the zk-STARK proofs. These zk-SNARKs are, in turn, published as the validity proofs to state changes. This helps in reducing the gas costs from 5M to 350K.
diff --git a/docs/zkEVM/index.md b/docs/zkEVM/index.md
@@ -20,19 +20,27 @@ hide:
 
 <div class="grid-container">
     <div class="grid-item">
-       <a href="./get-started/setup-nodes/local-node">
+       <a href="./overview">
           <div class="product-list-item-header">
-             <div class="feature-card-heading">zkEVM local node</div>
+             <div class="feature-card-heading">Polygon zkEVM overview</div>
           </div>
-          <p class="feature-paragraph">Get started by setting up a local zkEVM node.</p>
+          <p class="feature-paragraph">Take a global view of the Polygon zkEVM network.</p>
        </a>
     </div>
     <div class="grid-item">
-       <a href="./get-started/setup-nodes/deploy-zkevm/intro">
+       <a href="./get-started/quick-start">
           <div class="product-list-item-header">
-             <div class="feature-card-heading">Deploy zkEVM</div>
+             <div class="feature-card-heading">Connect wallet</div>
           </div>
-          <p class="feature-paragraph">Get started by deploying zkEVM.</p>
+          <p class="feature-paragraph">Connect your wallet to zkEVM mainnet or testnet.</p>
+       </a>
+    </div>
+    <div class="grid-item">
+       <a href="./get-started/setup-nodes/local-node">
+          <div class="product-list-item-header">
+             <div class="feature-card-heading">zkEVM local node</div>
+          </div>
+          <p class="feature-paragraph">Get started by setting up a local zkEVM node.</p>
        </a>
     </div>
     <div class="grid-item">
@@ -43,6 +51,13 @@ hide:
           <p class="feature-paragraph">Discover the key differences between zkEVM and EVM.</p>
        </a>
     </div>
+    <div class="grid-item">
+       <a href="./get-started/setup-nodes/deploy-zkevm/intro">
+          <div class="product-list-item-header">
+             <div class="feature-card-heading">Deploy zkEVM</div>
+          </div>
+          <p class="feature-paragraph">Get started by deploying zkEVM.</p>
+       </a>
+    </div>
 </div>
 </div>
-
diff --git a/docs/zkEVM/overview.md b/docs/zkEVM/overview.md
@@ -2,6 +2,13 @@ Polygon zkEVM is to Ethereum a Layer 2 network and a scalability solution utiliz
 
 Polygon zkEVM supports a 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.
 
+Connect to the fully-audited Polygon zkEVM mainnet or its testnet (Cardona testnet) using the details in the table below.
+
+| Network | RPC URL | ChainID | Block explorer URL | Gas token |
+| ------- | ------------------------------- | ---------------- | ---------------- | ----- |
+| Polygon zkEVM | `https://zkevm-rpc.com` | `1101` | `https://zkevm.polygonscan.com/` | **ETH** |
+| Cardona zkEVM testnet | `https://rpc.cardona.zkevm-rpc.com` | `2442` | `https://cardona-zkevm.polygonscan.com/` | **ETH** |
+
 ## Protocol development highlights
 
 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.
@@ -24,3 +31,37 @@ The activation of the 10-day timelock for upgrading zkEVM's smart contracts on E
 
 In the event of an emergency that puts user funds at risk, the network's [Security Council](https://etherscan.io/address/0x37c58Dfa7BF0A165C5AAEdDf3e2EdB475ac6Dcb6) may remove the 10-day timelock. In such an emergency, the network state stops advancing and bridge functionality is paused. The Security Council is an eight-participant multisig. This is a Gnosis Safe with a 6/8 threshold. Learn more about [zkEVM upgradability](https://docs.polygon.technology/zkEVM/architecture/protocol/upgradability/).
 
+## Design characteristics
+
+Polygon zkEVM was designed with security in mind. As an L2 solution, it inherits its security from Ethereum.
+
+Smart contracts are deployed to ensure that everyone who executes state changes does so appropriately, creates a proof that attests to the validity of each state change, and makes validity proofs available on-chain for verification.
+
+Development efforts aim at permissionless-ness, that is, allowing anyone with the zkEVM software to participate in the network. 
+
+For instance, the network allows anyone to circumvent any transaction-censorship by triggering the [force batches](./architecture/protocol/malfunction-resistance/sequencer-resistance.md) mechanism, or to avoid denial of validity-proving by activating the [force verification](./architecture/protocol/malfunction-resistance/aggregator-resistance.md) feature. 
+
+The ultimate aim is to ensure that there is no censorship and that no one party can control the network.
+
+Since data availability is most crucial for decentralization, Polygon zkEVM posts all transaction data and validity proofs on Ethereum. This means every Polygon zkEVM user has sufficient data needed to rebuild the full state of a rollup.
+
+## Efficiency and overall strategy
+
+As a scalability solution, efficiency is key to Polygon zkEVM. 
+
+The network therefore utilizes several implementation strategies to maximize efficiency.
+
+A few of these strategies are listed below:
+
+1. Deployment of the consensus contract, which incentivizes the aggregator for participating in the proof generation process.
+2. Carry out all computations off-chain while keeping only the necessary data and ZK-proofs on-chain.
+3. Implementation of the bridge smart contract is made efficient by using only Merkle roots of exit trees.
+4. Utilization of specialized cryptographic primitives within the proving component, [zkProver](https://docs.polygon.technology/zkEVM/architecture/zkprover/), to speed up computations and minimize proof sizes. This is seen in:
+    * Running a special zero-knowledge assembly language ([zkASM](./spec/zkasm/index.md)) for interpretation of bytecode.
+    * Using zero-knowledge technology such as zk-STARKs for proving purposes; these proofs are very fast though they are big in size.
+    * Instead of publishing the sizeable zk-STARK proofs as validity proofs, a zk-SNARK is used to attest to the correctness of the zk-STARK proofs. 
+    * Publishing zk-SNARKs as the validity proofs to state changes.
+    
+	These help in reducing gas costs from 5M to 350K (wei).
+
+The Polygon zkEVM network is therefore secure, efficient, comes with verifiable block data, and cost-effective.
