Description:
It would be incredibly helpful if the Safe transaction decoding API could support decoding based on the transaction hash (tx hash), in addition to the current support via raw data input.
Currently, as developers, we have to manually retrieve and decode input data using the raw calldata. If the decoding API could accept a transaction hash directly, it would save time and simplify workflows.
Additional Suggestion:
It also seems that the current decoding logic does not support transactions routed through the sponsoredCallV2(...) method, When I try to decode a transaction that uses this method , the decoder throws an error.
Proposed Improvements:
example transaction executed from sponser call v2 func https://polygonscan.com/tx/0xcbdbc5bad78748c650b07432449daf2bed95ac1f032da7e3a7b07dbf464aa573
Thanks for the great work so far!
Description:
It would be incredibly helpful if the Safe transaction decoding API could support decoding based on the transaction hash (tx hash), in addition to the current support via raw data input.
Currently, as developers, we have to manually retrieve and decode input data using the raw calldata. If the decoding API could accept a transaction hash directly, it would save time and simplify workflows.
Additional Suggestion:
It also seems that the current decoding logic does not support transactions routed through the sponsoredCallV2(...) method, When I try to decode a transaction that uses this method , the decoder throws an error.
Proposed Improvements:
Add support for decoding based on transaction hash
Extend decoding support to handle sponsoredCallV2(...) and similar wrapper functions by inspecting inner payloads
example transaction executed from sponser call v2 func https://polygonscan.com/tx/0xcbdbc5bad78748c650b07432449daf2bed95ac1f032da7e3a7b07dbf464aa573
Thanks for the great work so far!