Calldata decoder & API Encoder (with ABI) #952
Description
Is your feature request related to a problem? Please describe.
This feature is nice to have as tools could use it and build on it.
Currently, we support encoding &. decoding with ABI:
JSC types -> calldata
responsedata -> JSC types
Describe the solution you'd like
It would also be nice to have a calldata decoder:
calldata -> JSC types
and api data encoder:
JSC types -> responsedata
Internally we do not need such a flow other than maybe adding additional validation options/ testing,
but this could help
- case: describe calldata parameters for various explorers &. tools.
- case: encode response for rpc node & tools.
Additional context
With ABI this would complete a circle of data conversion as so one could do:
calldata -> JSC types -> responsedata
We could improve the test with excepted results for echo test methods
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Participants
Activity
AryanGodara commentedon Mar 2, 2024
Hi @tabaktoni ; Can I work on this issue?
I've been reading up on the repo, for some time now.
I initially saw it on OnlyDust, and asked @ivpavici if I could work on this one.
Looks like no one else has picked this issue yet :D
AryanGodara commentedon Mar 6, 2024
@ivpavici Thanks for assigning this to me. :D
I won't be able to get to it before coming Monday, because of some other obligations 😅
But this is in my list and I'll try to push the relevant changes in a few days.
ivpavici commentedon Mar 6, 2024
no worries, take your time!