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, viewing transactions has mostly the transaction function selector hex value and not the human-readable function name.
🤔 Rationale
I propose that we make a request to the OpenChain API to attempt to convert these function selectors even if the contact is not verified, so that people can more easily see what's going on.
The endpoint to use would be: https://api.openchain.xyz/signature-database/v1/lookup where you pass in a comma-delimited list of function selectors as follows:
🌟 Feature Request
📝 Description
Currently, viewing transactions has mostly the transaction function selector hex value and not the human-readable function name.
🤔 Rationale
I propose that we make a request to the OpenChain API to attempt to convert these function selectors even if the contact is not verified, so that people can more easily see what's going on.
BEFORE
AFTER
📋 Additional Context
Here's a link to the OpenChain.xyz API docs: https://docs.openchain.xyz/#/default/get_signature_database_v1_search
The endpoint to use would be:
https://api.openchain.xyz/signature-database/v1/lookup
where you pass in a comma-delimited list of function selectors as follows:Example response:
The text was updated successfully, but these errors were encountered: