-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web3modal update #192
Web3modal update #192
Conversation
I have read the CLA Document and I hereby sign the CLA |
@@ -49,7 +49,7 @@ module.exports = { | |||
}, | |||
etherscan: { | |||
apiKey: { | |||
klaytn: "unnecessary", | |||
kairos: "unnecessary", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@youngancient Thanks for your contribution.
Did you test it with explorer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I did. My first step was to deploy a contract on kaia testnet (kairos) and then verify.
My hardhat config at first looked like this:
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";
require('dotenv').config();
const config: HardhatUserConfig = {
solidity: "0.8.20",
networks: {
// for testnet
kairos: {
url: process.env.VITE_KAIA_TESTNET_RPC_URL!,
accounts: [process.env.PRIVATE_KEY!],
// gasPrice: 100000000000,
},
},
etherscan: {
apiKey: {
klaytn: "unnecessary",
},
customChains: [
{
network: "kairos",
chainId: 1001,
urls: {
apiURL: "https://api-baobab.klaytnscope.com/api",
browserURL: "https://kairos.kaiascope.com",
},
},
],
},
};
export default config;
In the network object, the network name is "kairos" but in the etherscan apiKey obj, "klaytn" was there, so I had the bug which was fixed by changing klaytn to kairos.
Proposed changes
Types of changes
Please put an x in the boxes related to your change.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
I have read the CLA Document and I hereby sign the CLA
in first time contributeRelated issues
Further comments