-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
i tried verify contract on sepolia testnet but it show error #1861
Comments
Got same error with sepolia |
I have a similar problem. The Rinkeby network is no longer working, I am using the Sepolia network. Up to now things have worked, but when I want to verify a contract problems come up. I have used the Keys API from etherscan.io . I add these API Keys to the .env file as explained in Vasiliy Gualoto's video time 6:27 (https://www.youtube.com/watch?v=yN3zpI3sNAE&t=23701s&ab_channel=Chainlink). I also updated the deploy.py file, but when executing the command in the terminal I get an error that I don't know how to solve. Here I show you the command and the result (brownieProjects) horacio@DESKTOP-DJSHN39:~/demos/brownie_fund_me$ brownie run scripts/deploy.py --network sepolia BrownieFundMeProject is the active project. Running 'scripts/deploy.py::main'... File "brownie/_cli/run.py", line 51, in main Somebody has the same problem? I do not know what is the meaning of "Explorer API not set for this network". |
I forgot to indicate that I added the sepolia network to Brownie and it is displayed like this: The following networks are declared: Ethereum Ethereum Classic |
what alternatives to rinkeby network can I use? |
I find the right way to add sepolia to brownie , just use it and everything will be fine : |
For my problem, after searching a lot, I found a solution and I was finally able to verify the smart contract in brownie. I went into .brownie\network-config and replaced the sepolia data with the following: -chainid: 11155111 I redisplayed the contract and brownie verified it. I could check it at https://sepolia.etherscan.io/ I found this information at: https://ethereum.stackexchange.com/questions/147238/infura-network-support-for-sepollia-in-brownie |
I have kinda similar error with @hbarrabasqui it says ValueError: Explorer API not set for this network And I figured out how to set the explorer API. You just have to modify the network through the terminal: \brownie_fund_me> brownie networks modify sepolia explorer=https://api-sepolia.etherscan.io/api If your sepolia network has the same name as mine, it is supposed to be working well |
I tried deploy and verify on goerli it work but on sepolia ( Add sepolia using infura api ) it shows :
Transaction sent: 0x574214495409706e1e0c946f2a8bc0030b73bac140d290c9b87c45ada398f8ca
Gas price: 2.726061052 gwei Gas limit: 449772 Nonce: 53
FundMe.constructor confirmed Block: 3244279 Gas used: 408884 (90.91%)
FundMe deployed at: 0x7C4dB3AaDfDD4E94f9E0DcC92716d1caf6be83e0
File "D:\python3_10\lib\site-packages\brownie_cli\run.py", line 51, in main
return_value, frame = run(
File "D:\python3_10\lib\site-packages\brownie\project\scripts.py", line 110, in run
return_value = f_locals[method_name](*args, **kwargs)
File ".\scripts\deploy.py", line 12, in main
deploy_FundMe()
File ".\scripts\deploy.py", line 7, in deploy_FundMe
fund_me = FundMe.deploy({"from": account}, publish_source=True)
File "D:\python3_10\lib\site-packages\brownie\network\contract.py", line 549, in call
return tx["from"].deploy(
File "D:\python3_10\lib\site-packages\brownie\network\account.py", line 557, in deploy
contract.publish_source(deployed_contract, silent=silent)
File "D:\python3_10\lib\site-packages\brownie\network\contract.py", line 408, in publish_source
data = response.json()
File "D:\python3_10\lib\site-packages\requests\models.py", line 975, in json
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
JSONDecodeError: Expecting value: line 2 column 1 (char 1)
PS E:\solidity_learn\brownie_fund_me>
Contract deployed but seem like brownie have some error when verifying contract
The text was updated successfully, but these errors were encountered: