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

[FEAT] Add support for Vyper contracts #109

Open
thevaizman opened this issue Oct 24, 2023 · 0 comments
Open

[FEAT] Add support for Vyper contracts #109

thevaizman opened this issue Oct 24, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@thevaizman
Copy link
Collaborator

Description

Support for Vyper compiled contracts.

Spec

We currently only have one supported compiler - solc.
That means that whenever a contract is analyzed, we only look for patterns that are used in solc in order to extract the storage layout information.
That means that we only minimally support Vyper contracts as only the patterns that are shared between the two compilers will get picked up by our analysis.

We should be able to identify that a contract was compiled by Vyper, either by looking for distinctive bytecode patterns, or by looking for the distinctive Vyper signature (available only on modern Vyper compiler versions) or even by providing a flag with the compiler type.

Then we should add support for the currently missing bytecode patterns rhat are generated by Vyper compiler to perform storage related operations (e.g., mapping accesses).

@thevaizman thevaizman added the enhancement New feature or request label Oct 24, 2023
@thevaizman thevaizman changed the title [FEAT] [FEAT] Add support for Vyper contracts Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant