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
Currently when using heimdall-decompile, the decompiled ABI provides access to the function name as well as the params, return data, mutability, etc. however it would be helpful to have the function selector or signature.
I am working on a feature in amms-rs where a user can search for all AMM Factory forks (ex. all instances of UniswapV2Factory) deployed to a specific chain.
amms-rs uses the sol! macro from alloy to create Rust bindings for contract interfaces. The struct generated by the sol! macro only provides access to function selectors or signatures. It would be helpful to have access to the selector or signature from the decompiled ABI to check if the target interface matches the decompiled code. This can be constructed from the data returned but it would be nice to have out of the box.
Below is a quick example showing the difference in between the two. Here is the link to the example if you would like to run it yourself as well!
Component
Heimdall (Core)
Describe the feature you would like
Currently when using
heimdall-decompile
, the decompiled ABI provides access to the function name as well as the params, return data, mutability, etc. however it would be helpful to have the function selector or signature.I am working on a feature in amms-rs where a user can search for all AMM Factory forks (ex. all instances of UniswapV2Factory) deployed to a specific chain.
amms-rs
uses thesol!
macro fromalloy
to create Rust bindings for contract interfaces. The struct generated by thesol!
macro only provides access to function selectors or signatures. It would be helpful to have access to the selector or signature from the decompiled ABI to check if the target interface matches the decompiled code. This can be constructed from the data returned but it would be nice to have out of the box.Below is a quick example showing the difference in between the two. Here is the link to the example if you would like to run it yourself as well!
The text was updated successfully, but these errors were encountered: