[BRO-13] Payload decoding in the browser wallet of the CIS3 standard

[Ivan-Mahda]

Purpose

The browser wallet can also decode the payload field by looking up the parameter schema of the entry_point_name and using this schema to decode the payload. The payload is the input parameter that is sent to the entry_point_name.

Changes

Proposal on how to decode the payload for the CIS3 contract.

Checklist

• My code follows the style of this project.
• The code compiles without warnings.
• I have performed a self-review of the changes.
• I have documented my code, in particular the intent of the
  hard-to-understand areas.
• (If necessary) I have updated the CHANGELOG.

By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0

• link: https://developers.concordium.com/CLAs/Contributor-License-Agreement-v1.0.pdf

• I accept the above linked CLA.

[limemloh]

As mentioned in the related issue #279
We cannot make signMessage behave like this, since it won't work reliably and worse it could be triggered for unrelated messages.

[limemloh]

Adding @soerenbf as reviewer since he is more familiar with the UI part of the wallet than me

[soerenbf]

I don't know that much about the CIS3 standard; I think @limemloh is better suited to comment on this part (as he already has). It would however be good if you created a small example application under /examples that uses the functionality.

There is an app /examples/two-step-transfer which has a pile of different functionality all inlined in a <script> tag in the html document. You can also find the sponsored transaction example there and adapt it. I would prefer if you created a small isolated (typescript) example though. We usually use vite to do this.

[limemloh]

Looks good to me

[soerenbf]

Are we not doing the example for running this, or what is the resolution on that?

[Ivan-Mahda]

Are we not doing the example for running this, or what is the resolution on that?

Yes, after wallet update. I will update example in sponsored transaction Concordium/concordium-dapp-examples#77