-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
forge verify-contract is unable to verify #2996
Comments
@defijesus could you give some more context, please - which version of foundry are you using, how were you deploying the contracts and how did you resolve version incompatibility between contracts? |
@defijesus same story. after i resolved version incompatibility and stack too deep errors, i ran the following command and got the contract verified forge script script/FeiRiskParamsUpdatePayload.s.sol --verify --fork-url <rpc-url> --broadcast --sender <sender> --private-key $PRIVATE_KEY https://goerli.etherscan.io/address/0xD77644A6B0B5B3e330B30531Df3456c2bBe64F81 p.s. i added one more attribute, so that etherscan does not match the similar bytecode verified previously |
Those are not from the Payload but from the Tests, correct? The Payload has no imports so it shouldn't have any stack too deep or version incompatibility, Can you try to simply pull the repo, compile as is, run the |
ah, it's the usual suspect - |
gl & hf 🫡 |
@defijesus should be fixed now. feel free to reopen if the issue persists |
Foundry can't verify this contract. This contract was deployed by running
make deploy
. Trying to verify directly on Etherscan with same build config also doesn't work. Trying to build and verify using Remix also doesn't work. Am I stoned, or is this gods work?The Foundry version is updated to latest using foundryup.
The platform you are on: M1 Mac
Code snippets: This repo has a single contract with no imports.
Concrete steps to reproduce the bug: make verify
More info:
papa bless ☀️
The text was updated successfully, but these errors were encountered: