-
Notifications
You must be signed in to change notification settings - Fork 49
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
fix ABI parsing bugs #106
Comments
This was referenced Dec 7, 2023
Closed
Just to add: Trying to load dynamic arrays in the abi is tough since etherscan returns Example abi: https://etherscan.io/address/0x6A8cbed756804B16E05E741eDaBd5cB544AE21bf#code which has: Trace: |
This is also the case with
|
@bout3fiddy the given contract has been added to the test cases in #108 and it seems to work fine |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the ABI parser currently depends on the vyper implementation:
titanoboa/boa/vyper/contract.py
Lines 1136 to 1151 in 5860aa4
however, this doesn't work whenever the ABI is not parseable by vyper. this can happen when names in the ABI are vyper keywords (more common than you would think, as
from
is a keyword in python), and whenever there are types not supported by vyper (e.g. dynamic arrays).probably the best thing to do here is make a standalone ABI parser, but it might be a bit tricky as a lot of functions depend on having a
ContractFunctionT
.The text was updated successfully, but these errors were encountered: