Include ptr , len and bytes in ABI Receipts

[maschad]

Related Component

compiler

Problem you are trying to solve

On beta5, when decoding a contract call from a transaction ABI receipt, one could have used the previous Param1 to determine the function selector.

Now with the new encoding for contract calls the contract calls first param is now encoded using the pointer and so consumers can no longer determine the function selector from the transaction receipt.

Solution you'd like

As shown in the screenshot above from the following transaction, given that Param1 and Param2 are pointers, they will always return the same values, and more importantly they are meaningless without access to the VM memory (which a consumer can't access at this point).

One solution could be to return thee ptr, len and bytes when returning the ABI Receipt.

Notes

No response

[IGI-111]

This should be convenience provided by the SDK when it reports the receipts, not a change in how the VM or Sway works.

The problem is not that it's a pointer, but that you didn't have the value recorder before giving up access to VM memory.

[maschad]

Thanks for clarifying. As it turns out I may have overcomplicated this as we can actually access the scriptData in contract calls and thus we can slice the encoded selector offset. Closing as this is no longer relevant.