-
Notifications
You must be signed in to change notification settings - Fork 34
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
Support more encoding/decoding types #170
Comments
@dawsbot Would you be open to such a PR, or would you prefer building the decoding logic from scratch? |
@KeKs0r I'm open to being inspired by Let me know what you think! |
Thanks for considering. I started to dive into the efforts and realized that even the encoders of |
Hi @KeKs0r any thoughts on the above? I can help make suggestions or jump-in if you have anything mid-way completed on this 🙏 |
Hey @dawsbot, I migrated to ethers to build an initial feature, since I realized it would take quite some efforts to reimplement in essentia-eth. Sorry for dropping the ball on this. |
All good, I still do that at-times too whenever it's too big of a lift to implement inside here. Could you help me out by linking me to a smart-contract which contains these data-types @KeKs0r ? I'll do the rest. |
Unfortunately I dont remember which contracts exactly hit some issues, but I have a list of contracts that I am calling in my code and their abis. |
Incredible, that should be plenty to help with debugging this @KeKs0r 🙏 |
There are several encoding + decoding types that are not yet working.
Enabling signing will be dangerous until most or all encoding/decoding types are working with
essential-eth
.To start, we should find production smart-contracts which have unique and difficult types then add support via jest tests like was done with the CRV smart-contract tests. The readme outlines types that are already covered properly. Assume all others will error and this issue is to track adding support.
The text was updated successfully, but these errors were encountered: