Merge pull request 0xPolygon#3 from 0xPolygon/empieichO/zkevmdocs_edit

Adding initial review

Author: kmurphypolygon

docs/zkEVM/develop.md

@@ -0,0 +1,75 @@
+---
+id: develop
+title: Get Started with Polygon zkEVM
+sidebar_label: Quickstart
+description: A guide to how to connect to the Polygon zkEVM network and start building with higher throughput and lower fees.
+keywords:
+  - polygon
+  - develop
+  - zkEVM
+  - deploy smart contracts
+  - connecting to zkEVM
+---
+
+
+## Connecting to zkEVM
+
+Add the **Polygon zkEVM** network to your wallet in order to interact with either the mainnet or the testnet.
+
+Navigate to `Add network` in your wallet, and enter the respective network details as given in the below table:
+
+| Network | RPC URL | ChainID | Block Explorer URL | Currency |
+| ------- | ------------------------------- | ---------------- | ---------------- | ----- |
+| Polygon zkEVM | `https://zkevm-rpc.com` | `1101` | `https://zkevm.polygonscan.com/` | **ETH** |
+| zkEVM Testnet | `https://rpc.public.zkevm-test.net` | `1442` | `https://testnet-zkevm.polygonscan.com` | **ETH** |
+
+
+Once the wallet is connected, the next step is to [bridge crypto assets](zkEVM/bridge-to-zkevm.md) from Ethereum to zkEVM. 
+
+For testnet purposes, you can use the zkEVM faucet to get testnet tokens. 
+
+
+
+## Deploying Smart Contracts
+
+The development experience on zkEVM is seamless and identical to Ethereum Virtual Machine. Developers on zkEVM can use their existing code and toolings to deploy on zkEVM with much higher throughput and lower fees.
+
+Here is a video tutorial on **how to add Polygon zkEVM Testnet to MetaMask and deploy smart contracts**:
+
+<video autoplay width="100%" height="100%" controls="true" >
+  <source type="video/mp4" src="/img/zkevm/tutorial.mp4"></source>
+  <p>Your browser does not support the video element.</p>
+</video>
+
+## Get Started with Web3Modal
+
+:::caution Content disclaimer
+
+Please view the third-party content disclaimer [<ins>here</ins>](https://github.com/0xPolygon/wiki/blob/master/CONTENT_DISCLAIMER.md).
+
+:::
+
+### Overview
+
+[<ins>Web3Modal</ins>](https://web3modal.com/) is a simple and intuitive SDK that provides a drop-in UI to enable users of any wallet to seamlessly log in to applications, offering a unified and smooth experience. It features a streamlined wallet selection interface with automatic detection of various wallet types, including mobile, extension, desktop, and web app wallets.
+
+### Code Sandbox for Polygon
+
+The Web3Modal team has prepared a [<ins>Polygon Code Sandbox</ins>](https://codesandbox.io/p/sandbox/web3modal-v3-polygon-7264l5?file=/src/main.tsx:9,19-9,50). It’s a straightforward way for developers to integrate and get hands-on experience with Polygon.
+
+### How to Integrate
+
+1. **Visit Web3Modal:** Go to [<ins>Web3Modal's official website</ins>](https://web3modal.com/) to explore its features and capabilities.
+2. **Explore the Code Sandbox:** Utilize the [<ins>Polygon Code Sandbox</ins>](https://codesandbox.io/p/sandbox/web3modal-v3-polygon-7264l5?file=/src/main.tsx:9,19-9,50) to demo and understand the integration process.
+3. **Follow the Documentation:** Refer to the provided documentation and instructions to integrate Web3Modal into your projects and leverage its features effectively.
+
+## zkEVM Support
+
+If you need help with anything related to the Polygon zkEVM, you can raise a ticket on the [Polygon Support](https://support.polygon.technology/support/tickets/new) portal, and check out the [Knowledge base](https://support.polygon.technology/support/solutions/folders/82000694871) to view the most common queries about the zkEVM. Additionally, you can reach out to the support team available on the **#zkevm-support** channel on the [Polygon Discord server](https://discord.com/invite/XvpHAxZ). Instructions for raising a zkEVM support ticket are as follows:
+
+1. Join the **Polygon Discord** server [here](https://discord.gg/0xPolygon).
+2. Accept the invite sent via DM.
+3. Take the **Member** role under **#roles**.
+4. Navigate to the **#zkevm-support** channel.
+
+You can now contact the zkEVM support staff with your questions and concerns. We will actively monitor for issues and work to resolve them as soon as possible.

docs/zkEVM/figures/fig1-simpl-arch.png

@@ -0,0 +1,15 @@
+This documentation contains guides on how to connect wallets to the Polygon zkEVM network, deploy new or existing Ethereum smart contracts, and bridge assets between Polygon zkEVM and Ethereum.
+
+Developers can find guides to setting up an RPC zkNode, spinning up a production zkNode, or even implementing their own fully-fledged zkEVM.
+
+All the while, there is no need for any special toolings or wallets to build or interact with Polygon zkEVM.
+
+Polygon zkEVM is fully compatible with Ethereum to provide a complete EVM-like UX for both Developers and Users.
+
+Simply switch to the zkEVM RPC and start building on a network with a much higher throughput and lower fees.
+
+:::caution Risks
+
+Check the list of potential risks associated with the use of Polygon zkEVM in the [<ins>Risks FAQ</ins>](/zkevm/risk-disclosure.md) section.
+
+:::

docs/zkEVM/figures/fig2-simple-poe.png

@@ -0,0 +1,54 @@
+---
+id: risk-disclosure
+title: Polygon zkEVM Risk Disclosures
+sidebar_label: Risk Disclosures
+description: This article explains the potential risks associated with using Polygon zkEVM Mainnet Beta.
+keywords:
+  - zkEVM
+  - polygon
+  - Risk Disclosures
+  - Network Availability
+  - Decentralization
+---
+
+Polygon zkEVM Mainnet Beta is provided on an **AS-IS** and **AS-AVAILABLE** basis. The documentation contains statements about technical specifications, some of which may relate to future versions of Polygon zkEVM rather than its current implementation.
+
+## Attack Vectors/Security
+
+- This is a **Mainnet Beta** and **not a Mainnet release of Polygon zkEVM**, [<ins>security audits</ins>](https://polygon.technology/blog/polygon-zkevm-results-of-hexens-security-audit) and assessments are ongoing. Your data and crypto-assets may be at risk as a result of bugs or otherwise.
+
+- **Polygon zkEVM technology is novel**. As such, there may be unanticipated issues and risks associated with your use of the technology. For example, there may be errors that result in losing data or crypto-assets.
+
+- **Cross-blockchain bridging may be subject to cyberattacks and exploits** including, without limitation, hacks that exploit a vulnerability in the software, hardware, systems or equipment associated with any bridge component, smart contracts, and related systems.
+
+## Network Availability/Performance
+
+As this is a Mainnet Beta, Polygon zkEVM may be slow or unavailable from time to time without notice, which could result in unexpected loss of use or data or crypto-assets. Before engaging in high value transactions, be mindful that there may be time delays before transactions are finalized.
+
+## Decentralization Progress
+
+Polygon Labs is in the process of further decentralizing Polygon zkEVM. This refers to the process of gradually increasing decentralization of the system over time.
+
+- The Mainnet Beta will have some centralized features, such as the Sequencer and Aggregator (Prover), that Polygon Labs currently maintains in an effort to provide greater security at this time. **The Sequencer has the ability to delay the inclusion of a transaction and otherwise reorder transactions**.
+
+- Security of Polygon zkEVM Mainnet Beta is a continuous process. This process includes responding to security concerns, which depends on the Security Council. **The Security Council consists of 8 individuals who are empowered to upgrade Polygon zkEVM Mainnet Beta** without a timelock to respond to urgent security issues. If members of the Council behave maliciously or collude, then the integrity of the system may be compromised including network upgrades that may result in loss of crypto-assets.
+
+- As the Sequencer and Aggregator are centralized for Mainnet Beta, there are risks for potential network downtime and outages, including those that are outside the control of Polygon Labs.
+
+- During the initial phase of the Mainnet Beta release, users will not be able to force transactions on Layer 1.
+
+## Gas Fees
+
+If the gas fees associated with a proposed transaction are too low, it is possible that such transaction will not be sequenced and that those fees may be lost.
+
+## Security Audits
+
+- Polygon Labs’ implementation of Polygon zkEVM has been carefully constructed, was audited by several internal and external parties, and is continuously being reviewed and tested against engineering best practices. It is, however, unlikely that all potential bugs or vulnerabilities were identified through these audits and thus there may be undiscovered vulnerabilities that may put user funds at risk. Users should consider this risk when deciding how much value to place onto the Polygon zkEVM Mainnet Beta. To see the audit reports, see [<ins>here</ins>](https://github.com/0xPolygonHermez/zkevm-rom/blob/main/audits/Hexens_Polygon_zkEVM_PUBLIC_27.02.23.pdf).
+
+- There is a robust bug bounty program for Polygon zkEVM to help encourage the community to find critical bugs in the codebase. Head over to the [<ins>Polygon zkEVM Bug Bounty page on Immunefi</ins>](https://immunefi.com/bounty/polygonzkevm/).
+
+## Prover Infrastructure
+
+- Currently the Polygon zkEVM zkProver does not run on ARM-powered Macs. For Windows users, using WSL/WSL2 is not recommended. Apple M1 chips are not supported for now, since some optimizations on the zkProver require specific Intel instructions. This means some non-M1 computers won't work regardless of the OS, for example: AMD.
+
+- In the event you are deploying a full node of Polygon zkEVM Mainnet Beta, be mindful that the network data is stored inside of each docker container. This means once you remove the container that network data will be lost and you will be required to resync the network data.