we've added Safe App support to our app at https://www.drips.network/, but not yet requested to list it on the Safe App registry.

Today, one of our users manually added our app to their safe, and reported seeing this strange "Failed decoding transaction data" error on the TX confirmation screen for any transaction the app triggers:

enter image description here

The "Details" are just "1337". This error doesn't seem to be affecting functionality at all - the transaction can still be triggered, and executes fine. Just wondering what could be causing this error and if there's anything we can do about it from our end.

  • You should use customer support for this type of requests
    – mikheevm
    Commented May 11, 2023 at 15:34

1 Answer 1


That error is because the gnosis transaction decoder didn't find the corresponding function signature, if you want to see what function is being used in the transaction and what parameters you can use this tool: https://calldata-decoder.apoorv.xyz/, just past the encoded data.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.