Skip to content
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

--evm-version flag needed for forge verify-contract #7176

Closed
2 tasks done
pegahcarter opened this issue Feb 19, 2024 · 0 comments · Fixed by #7178
Closed
2 tasks done

--evm-version flag needed for forge verify-contract #7176

pegahcarter opened this issue Feb 19, 2024 · 0 comments · Fixed by #7178
Labels
T-bug Type: bug

Comments

@pegahcarter
Copy link
Contributor

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

What version of Foundry are you on?

forge 0.2.0 (1bb2d67 2024-02-19T00:17:15.443050638Z)

What command(s) is the bug in?

forge verify-contract

Operating System

Linux

Describe the bug

I am trying to verify a contract I recently deployed using Solidity 0.8.20. My foundry.toml uses the existing profile:

evm_version = "london"

Solidity v0.8.20 by default uses "byzantium" (see "evmVersion" here). So, I have a conflict where my deployed contract is using a different version than the default.

However, forge verify-contract does not have an --evm-version flag and so my compiled bytecode does not match my deployed outcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-bug Type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant