update CDK/zkEVM: Roll up deploy tutorial from Goerli to Sepolia

Author: BrianSeong99

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/configure-node-deployment.md

@@ -31,50 +31,62 @@ comments: true
 4. In the `.env` file, set the following:
 
     ```sh
-    ZKEVM_NODE_ETHERMAN_URL = ""  # set valid Goerli RPC endpoint
+    ZKEVM_NODE_ETHERMAN_URL = ""  # set valid Sepolia RPC endpoint
     ZKEVM_NODE_STATEDB_DATA_DIR = "~/zkevm/data/statedb"
     ZKEVM_NODE_POOLDB_DATA_DIR = "~/zkevm/data/pooldb"
     ```
 
     !!! warning "Workaround if you have configuration issues"
         - You may have to hardcode these variables into the `mainnet/docker-compose.yaml` file.
-        - Also, the `ZKEVM_NETWORK` variable which you can set to `mainnet`.
-        - Note, there are more than one references to hardcode in.
+            - Also, the `ZKEVM_NETWORK` variable which you can set to `mainnet`.
+            - Note, there are more than one references to hardcode in.
 
-## Approve MATIC token for sequencer
+## Approve POL token for sequencer
 
-1. Launch a Hardhat console connected to the Goerli network.
+1. Launch a Hardhat console connected to the Sepolia network.
 
     ```sh
     cd ~/zkevm-contracts
-    npx hardhat console --network goerli
+    npx hardhat console --network sepolia
     ```
 
 2. Add the missing data as directed and copy/paste the following code into the open console.
 
     ```js
-    const provider = ethers.getDefaultProvider("<GOERLI_RPC_NODE>"); // set Goerli RPC node
+    const provider = ethers.getDefaultProvider("https://sepolia.drpc.org"); // set Sepolia RPC node
+    const privateKey = "0xdd3ddb7e864207f6c11ed73348221823eccb8e872d2d6f3103df6f32b284a15a"; // from wallets.txt 
+    const wallet = new ethers.Wallet(privateKey, provider);
+    
+    const polTokenFactory = await ethers.getContractFactory(
+    "ERC20PermitMock",
+    provider
+    );
+    polTokenContract = polTokenFactory.attach("0x2B2Ef864542EA38657221393B0A18215e5c3fc7e"); // from ~/zkevm-contracts/deployments/deploy_output.json 
+    polTokenContractWallet = polTokenContract.connect(wallet);
+    await polTokenContractWallet.approve("0x702394d505ABC47cEd3F4D2CD04453719A9168cc", ethers.parseEther("100.0")); // from ~/zkevm-contracts/deployments/deploy_output.json 
+    
+    const provider = ethers.getDefaultProvider("<SEPOLIA_RPC_NODE>"); // set Sepolia RPC node
     const privateKey = "<TRUSTED_SEQUENCER_PK>"; // from wallets.txt 
     const wallet = new ethers.Wallet(privateKey, provider);
-
-    const maticTokenFactory = await ethers.getContractFactory(
+    
+    const polTokenFactory = await ethers.getContractFactory(
     "ERC20PermitMock",
     provider
     );
-    maticTokenContract = maticTokenFactory.attach("<maticTokenAddress>"); // from ~/zkevm-contracts/deployments/deploy_output.json 
-    maticTokenContractWallet = maticTokenContract.connect(wallet);
-    await maticTokenContractWallet.approve("<polygonZkEVMAddress>", ethers.utils.parseEther("100.0")); // from ~/zkevm-contracts/deployments/deploy_output.json 
+    polTokenContract = polTokenFactory.attach("<polTokenAddress>"); // from ~/zkevm-contracts/deployments/deploy_output.json 
+    polTokenContractWallet = polTokenContract.connect(wallet);
+    await polTokenContractWallet.approve("<polygonZkEVMAddress>", ethers.parseEther("100.0")); // from ~/zkevm-contracts/deployments/deploy_output.json 
     ```
 
 ## Configure genesis
 
 1. Copy the `genesis.json` file into the appropriate location.
 
     ```sh
-    cp ~/zkevm-contracts/deployment/genesis.json ~/zkevm/mainnet/config/environments/mainnet/public.genesis.config.json
+    cp ~/zkevm-contracts/deployment/v2/genesis.json ~/zkevm/mainnet/config/environments/mainnet/public.genesis.config.json
     ```
 
-2. Copy/paste the json below to the head of the `public.genesis.config.json` file inputting the data from `~/zkevm/zkevm-contracts/deployments/deploy_output.json`. 
+2. Copy/paste the json below to the head of the `public.genesis.config.json` file inputting the data from `~/zkevm-contracts/deployments/v2/deploy_output.json`. 
 
     !!! important
         The `genesisBlockNumber` is called `deploymentBlockNumber` in `deploy_output.json`.
@@ -83,7 +95,7 @@ comments: true
     "l1Config" : {
         "chainId": 5,
         "polygonZkEVMAddress": "", 
-        "maticTokenAddress": "", 
+        "polTokenAddress": "", 
         "polygonZkEVMGlobalExitRootAddress": ""  
     },
     "genesisBlockNumber": <number-here>,  
@@ -97,7 +109,7 @@ Add the following missing parameters to the `~/zkevm/mainnet/config/environments
     If you're having trouble locating the configuration file, try looking for `node.config.toml`, since it may exist under that name in some cases. Once you've added the missing parameters, rename the file to `public.node.config.toml`.
 
 - `ApiKey`  # for Etherscan
-- `URL`     # for Goerli node, under [ETHERMAN]
+- `URL`     # for Sepolia node, under [ETHERMAN]
 
 ## Add wallet keystores
 

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/create-wallets.md

@@ -8,7 +8,7 @@ Clone the wallet contracts from the [`zkevm-contracts` repository](https://githu
 
 ```sh
 git clone https://github.com/0xPolygonHermez/zkevm-contracts.git
-cd ~/zkevm-contracts
+cd zkevm-contracts
 npm i
 ```
 
@@ -17,7 +17,7 @@ npm i
 1. Create a `wallets.js` file.
 
     ```sh
-    cd ~/zkevm-contracts
+    cd zkevm-contracts
     nano wallets.js
     ```
 
@@ -36,8 +36,8 @@ npm i
         const wallet = ethers.Wallet.createRandom();
         console.log(arrayNames[i]);
         console.log(`Address: ${wallet.address}`);
-        console.log(`PrvKey: ${wallet._signingKey().privateKey}`);
-        console.log(`mnemonic: "${wallet._mnemonic().phrase}"`);
+        console.log(`PrvKey: ${wallet.privateKey}`);
+        console.log(`mnemonic: "${wallet.mnemonic.phrase}"`);
 
         const keystoreJson = await wallet.encrypt("password");
         console.log(`keystore: ${keystoreJson}`);
@@ -73,14 +73,14 @@ npm i
     ETHERSCAN_API_KEY="..."   # your Etherscan API key
     ```
 
-3. Send 0.5 Sepolia ETH to the deployment address wallet listed in `wallets.txt`.
+3. Send 1 Sepolia ETH to the deployment address wallet listed in `wallets.txt`.
 
 ## Edit deployment configuration
 
 1. Open the `deploy-parameters.json` file.
 
     ```sh
-    cd ~/zkevm-contracts/deployment
+    cd zkevm-contracts/deployment/v2
     cp deploy_parameters.json.example deploy_parameters.json
     nano deploy_parameters.json
     ```
@@ -94,39 +94,75 @@ npm i
     - `timelockAddress`: deployment address in `wallets.txt`.
     - `initialZkEVMDeployerAddress`: deployment address in `wallets.txt`.  
     - `zkEVMDeployerAddress`: deployment address in `wallets.txt`.  
+    - `emergencyCouncilAddress`: deployment address in `wallets.txt`.
+    - `deployerPvtKey`: deployment private key in `wallets.txt`.
 
-## Deploy contracts
+3. Open the `create_rollup_parameters.json` file.
 
-1. `cd` back to `zkevm-contract` root directory and run the deployment scripts.
+    ```bash
+    cd zkevm-contracts/deployment/v2
+    cp create_rollup_parameters.json.example create_rollup_parameters.json
+    vim create_rollup_parameters.json
+    ```
 
-    !!! tip
-        It might be helpful to run these one at a time.
+4. Edit the following parameters to match the rollup parameters
 
-    ```sh
-    cd ..
-    npm i @openzeppelin/hardhat-upgrades
-    npm run deploy:deployer:ZkEVM:goerli
-    npm run verify:deployer:ZkEVM:goerli
-    npm run prepare:testnet:ZkEVM:goerli && npm run deploy:ZkEVM:test:goerli
-    npm run verify:ZkEVM:goerli
-    ```
+    - `trustedSequencer`:  trusted sequencer address in `wallets.txt`.
+    - `adminZkEVM`: deployment address in `wallets.txt`.
 
-    You should see output that looks something like this at the start each time:
+## Deploy & verify contracts
 
-    ```sh
-    > @0xpolygonhermez/zkevm-contracts@3.0.0 deploy:deployer:ZkEVM:goerli
-    > npx hardhat run deployment/2_deployPolygonZKEVMDeployer.js --network goerli
+`cd` back to `zkevm-contract` root directory and run the deployment scripts.
 
-    #######################
+1. Install Hardhat
 
-    polygonZkEVMDeployer deployed on:  0x8c4e69A65f84D5Ee0d83095916706Be74C133571
-    ```
+   ```
+   cd ..
+   npm i @openzeppelin/hardhat-upgrades
+   ```
+
+2. Deploy Polygon ZKEVM Deployer
+
+   ```bash
+   npx hardhat run deployment/v2/2_deployPolygonZKEVMDeployer.ts --network sepolia
+   ```
+
+   You should see output that looks like this:
+
+   ```bash
+   #######################
+   
+   polygonZkEVMDeployer deployed on:  0xB1A5BA61fBAD71Ba52d70B769d6A994c01b40983
+   ```
+
+3. Verify Deployer
+
+   ```bash
+   npx hardhat run deployment/v2/verifyzkEVMDeployer.js --network sepolia
+   ```
+
+   You should see ouput that looks like this:
+
+   ```bash
+   The contract 0xB1A5BA61fBAD71Ba52d70B769d6A994c01b40983 has already been verified.
+   https://sepolia.etherscan.io/address/0xB1A5BA61fBAD71Ba52d70B769d6A994c01b40983#code
+   ```
+
+4. Prepare Testnet
+
+   ```bash
+   npx hardhat run deployment/testnet/prepareTestnet.ts --network sepolia
+   ```
+
+   You should see output that looks like this:
 
-    !!! info
-        The scripts auto-deploy the MATIC token contract and the `zkEVMDeployer` contract if required.
+   ```bash
+   #######################
+   
+   pol deployed to: 0x2B2Ef864542EA38657221393B0A18215e5c3fc7e
+   ```
 
-2. Check the deployment was successful on Etherscan.
+   And now if you go to sepolia scan, you should also see that under your account, there's a new `Pol` Erc-20 token created with the balance of `19,900,000` tokens.
 
-    ```html
-    https://goerli.etherscan.io/address/[deployment-address] <!-- from `wallets.txt` -->
-    ```
+!!! info
+    The scripts auto-deploy the MATIC token contract and the `zkEVMDeployer` contract if required.

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/environment-overview.md

@@ -24,5 +24,5 @@ Deploying the full zkEVM stack requires installing and deploying a number of dif
 | zkEVM explorer    | `zkevm-explorer-l2`    | L2 network's block explorer. i.e., The zkRollup Etherscan [explorer](https://zkevm.polygonscan.com). |
 | zkEVM explorer DB | `zkevm-explorer-l2-db` | Database for the L2 network's Block explorer. i.e., Where all the zkRollup Etherscan explorer queries are made. |
 | Gas pricer        | `zkevm-l2gaspricer`    | Responsible for suggesting the gas price for the L2 network fees. |
-| Goërli execution  | `goerli-execution`     | L1 node's execution layer.                                   |
-| Goërli consensus  | `goerli-consensus`     | L1 node's consensus layer.       
+| Sepolia execution  | `sepolia-execution`     | L1 node's execution layer.                                   |
+| Sepolia consensus  | `sepolia-consensus`     | L1 node's consensus layer.       

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/install-dependencies.md

@@ -26,7 +26,7 @@ newgrp docker && newgrp $USER
 ```sh
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash
 source ~/.bashrc
-nvm install 16
+nvm install 18
 node -v
 ```
 

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/intro.md

@@ -2,7 +2,7 @@
 comments: true
 ---
 
-This tutorial takes you through the process of deploying a full zkEVM stack on Goerli.
+This tutorial takes you through the process of deploying a full zkEVM stack on Sepolia.
 
 It relies on specific component versions so we have hidden most of the configuration complexity in scripts to make the process straightforward.
 

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/prerequisites.md

@@ -31,5 +31,5 @@ The commands on the [install dependencies page](install-dependencies.md) fulfill
 
 - `INFURA_API_KEY`: [Infura](https://infura.io/) API key
 - `ETHERSCAN_API_KEY`: [Etherscan](https://etherscan.io/) API key
-- Goërli node RPC URL: e.g. https://goerli.infura.io/v3/YOUR-INFURA-API-KEY
-- Goërli account address holding minimum 0.5 GoërliETH
+- Sepolia node RPC URL: e.g. https://sepolia.infura.io/v3/YOUR-INFURA-API-KEY
+- Sepolia account address holding minimum 0.5 SepoliaETH

docs/zkEVM/get-started/setup-nodes/deploy-zkevm/start-node.md

@@ -7,7 +7,7 @@ comments: true
 From the `zkevm` root directory, run the following:
 
 ```sh
-docker-compose -f mainnet/docker-compose.yml up
+sudo docker-compose -f mainnet/docker-compose.yml up
 ```
 
 This command spins up the following services: