Skip to content

Commit b9e9db9

Browse files
authored
Merge pull request 0xPolygon#509 from KENILSHAHH/main
Changed references from zkevm blueberry testnet (deprecated) to zkevm Cardona testnet
2 parents 1f8d709 + fec6e96 commit b9e9db9

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

docs/zkEVM/how-to/using-foundry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ In order to deploy on the zkEVM Testnet, populate the `.env` file in the usual w
129129
- Populate `.env.sample` file with your `ACCOUNT_PRIVATE_KEY` and the zkEVM Testnet's `RPC URL` found [here](../get-started/quick-start.md). So the `.env.sample` file looks like this:
130130
131131
```json
132-
RPC_URL="https://rpc.public.zkevm-test.net"
132+
RPC_URL="https://rpc.cardona.zkevm-rpc.com"
133133
PVTKEY="<insert private key here>"
134134
```
135135

docs/zkEVM/how-to/using-hardhat.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ mv README.md README-tutorial.md
8787
},
8888
networks: {
8989
zkEVM: {
90-
url: `https://rpc.public.zkevm-test.net`,
90+
url: `https://rpc.cardona.zkevm-rpc.com`,
9191
accounts: [process.env.ACCOUNT_PRIVATE_KEY],
9292
},
9393
},
@@ -130,7 +130,7 @@ mv README.md README-tutorial.md
130130
const deployedContract = await hre.ethers.deployContract("Counter");
131131
await deployedContract.waitForDeployment();
132132
console.log(
133-
`Counter contract deployed to https://explorer.public.zkevm-test.net/address/${deployedContract.target}`
133+
`Counter contract deployed to https://cardona-zkevm.polygonscan.com/address/${deployedContract.target}`
134134
);
135135
}
136136
@@ -160,7 +160,7 @@ mv README.md README-tutorial.md
160160
161161
​Here's an output example:
162162
163-
`Counter contract deployed to https://explorer.public.zkevm-test.net/address/0x5FbDB2315678afecb367f032d93F642f64180aa3`
163+
`Counter contract deployed to https://cardona-zkevm.polygonscan.com/address/0x5FbDB2315678afecb367f032d93F642f64180aa3`
164164
165165
## Update frontend
166166

docs/zkEVM/how-to/verify-contract.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ After successfully compiling a smart contract, follow the next steps to verify y
88

99
1. Copy the address to which the smart contract is deployed.
1010

11-
2. Navigate to the [zkEVM Explorer](https://testnet-zkevm.polygonscan.com) and paste the contract address into the Search box. This opens a window with a box labelled **Contract Address Details**.
11+
2. Navigate to the [zkEVM Explorer](https://cardona-zkevm.polygonscan.com/) and paste the contract address into the Search box. This opens a window with a box labelled **Contract Address Details**.
1212

1313
3. Scroll down to the box with tabs labelled **Transactions**, **Internal Transactions**, **Coin Balance History**, **Logs**, and **Code**.
1414

@@ -40,7 +40,7 @@ After successfully compiling a smart contract, follow the next steps to verify y
4040
forge flatten src/<Contract-Name> -o <Any-Name-For-Flattened-Code>.sol
4141
```
4242

43-
With this command, the flattened code gets saved in the `<Any-Name-For-Flattened-Code>.sol` file. Copy the contents of the new `<Any-Name-For-Flattened-Code>.sol` file and paste into the `Enter the Solodity Contract` field in the [explorer](https://testnet-zkevm.polygonscan.com).
43+
With this command, the flattened code gets saved in the `<Any-Name-For-Flattened-Code>.sol` file. Copy the contents of the new `<Any-Name-For-Flattened-Code>.sol` file and paste into the `Enter the Solodity Contract` field in the [explorer](https://cardona-zkevm.polygonscan.com/).
4444

4545
??? "Standard input JSON"
4646
Click **Next** after selecting the **via Standard Input JSON** option.
@@ -76,14 +76,14 @@ We use the ready-made `Storage.sol` contract in Remix. Compile the contract and
7676
1. Deploy the `Storage.sol` contract:
7777

7878
- Click the **Deploy** icon on the left-side of the IDE window.
79-
- Change `ENVIRONMENT` to "Injected Provider - MetaMask" (ensure that your wallet is already connected to Goërli network).
79+
- Change `ENVIRONMENT` to "Injected Provider - MetaMask" (ensure that your wallet is already connected to Sepolia network).
8080
- Confirm the connection request when MetaMask pops up.
8181
- Click the **Deploy** button and confirm.
8282

8383
2. Check the deployed smart contract on Etherscan:
8484

8585
- Copy the contract address below the **Deploy Contracts**.
86-
- Navigate to the [Goërli explorer](https://goerli.etherscan.io).
86+
- Navigate to the [Sepolia explorer](https://sepolia.etherscan.io).
8787
- Paste the contract address in the _Search by address_ field and press **ENTER**.
8888
- Click on the **Transaction Hash** to see transaction details.
8989

@@ -105,7 +105,7 @@ We use the ready-made `Storage.sol` contract in Remix. Compile the contract and
105105

106106
- Click on the Etherscan icon.
107107

108-
- Ensure that **Goërli** is present in the **Selected Network** field.
108+
- Ensure that **Sepolia** is present in the **Selected Network** field.
109109

110110
- Click within the _Contract Name_ field and type in the name of your deployed contract, or select it if it appears.
111111

0 commit comments

Comments
 (0)