[Feature] Decoding call data

When using the superhero wallet and interacting with contracts I have no idea what’s going on - what data is actually being passed to the contract…
As a dev I can always do some wizardry like:
image
or:
image

My point is that the SDK or the superhero wallet should be able to automatically decode such data.
What is better?

cb_KxEq+mD+G2+CB3jsoBRB 

or

 fn_2afa60fe(1976)

?

If there would be interest in this feature I can implement such a thing in the SDK :wink:
CC: @yani.chain @milenradkov.chain @philipp.chain

Just leaving it here as a footnote. From what I see:
https://github.com/aeternity/aepp-calldata-js
is currently in a state where such decoding can be done trivially :slight_smile:

2 Likes

We’ve been discussing this for a while. It will be nice to have it in the wallet, though it wont bring much more security to the end user.

2 Likes

@milenradkov.chain as a footnote https://github.com/gorbak25/erlscripten/tree/develop is in a state where probably next week aebytecode/aeserialization can be compiled to a JS bundle and fully available on the client side - I will DM you when this happens.

3 Likes

Let’s push it to npm when it’s ready.

1 Like