You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: