Support contracts without auxdata #2456
Open
Conversation
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
manuelwedler
reviewed
Nov 6, 2025
| noOnchainMetadata = true; | ||
| } | ||
| } catch (err: any) { | ||
| noOnchainMetadata = true; |
Member
There was a problem hiding this comment.
for my understanding, decode throws if there is no auxdata, or how does it work?
manuelwedler
reviewed
Nov 6, 2025
| } | ||
|
|
||
| // we throw the bytecode length mismatch error only if there is onchain metadata | ||
| if (!noOnchainMetadata) { |
Member
There was a problem hiding this comment.
For Vyper, there will never be auxdata in the onchain runtime code. This means the logic is changed for Vyper. Is this intentional?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See #2374