This repository was archived by the owner on Apr 20, 2026. It is now read-only.
fix: normalize Vyper EVM version during input creation#345
Merged
zerosnacks merged 2 commits intomainfrom Jan 19, 2026
Merged
Conversation
zerosnacks
force-pushed
the
fix-vyper-evm-version-normalization
branch
from
ce08df7 to
c7fe66c
Compare
zerosnacks
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
klkvr,
mattsse and
onbjerg
as code owners
VyperInput::new() was only calling sanitize_output_selection() instead of sanitize(), which meant normalize_evm_version() was never invoked. This caused compilation failures when using EVM versions not supported by the Vyper version (e.g., osaka with Vyper 0.4.3 which only supports up to prague).
zerosnacks
force-pushed
the
fix-vyper-evm-version-normalization
branch
from
c7fe66c to
df56e34
Compare
grandizzy
approved these changes
Jan 19, 2026
This was referenced Jan 19, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
VyperInput::new()was callingsanitize_output_selection()instead ofsanitize(), which meantnormalize_evm_version()was never invoked during input creation.This caused compilation failures when using EVM versions not supported by the Vyper compiler version. For example, using
osaka(the new default in Foundry) with Vyper 0.4.3 would fail with:Fix
Call
sanitize()instead ofsanitize_output_selection()inVyperInput::new(). Thesanitize()method already calls bothsanitize_output_selection()andnormalize_evm_version(), so this ensures the EVM version is properly downgraded to the maximum supported by the Vyper version (e.g.,praguefor Vyper 0.4.3).