Closed vagueink closed 3 years ago
I was able to bypass this issue using the Etherscan Contract Verification plugin for Remix. I just needed an API key from Etherscan...there was also about a 10 minute lag between my API being created and it being usable.
I was able to deploy the contract (on Rinkeby) per your latest video tutorial with no issues. When I look at the contract on Etherscan it tells me I need to verify the contract which I attempt to do using the settings on the attached screenshot.
I use the JSON file that Remix generates and paste the constructor arguments in ABI encoded format. To get the ABI encoded constructor arguments I copy the ABI out of Remix and into https://abi.hashex.org then fill out my parameter values to generate the ABI-encoded data. I then paste that into the Constructor Arguments and click Verify and Publish.
I then get the following error (Unknown key "abi"). I have attached a screenshot. Any help appreciated.