Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Inconsistent api data for malformed relay transaction #1087

Open
1 task done
MWFIAE opened this issue Jun 26, 2023 · 0 comments
Open
1 task done

[Bug]: Inconsistent api data for malformed relay transaction #1087

MWFIAE opened this issue Jun 26, 2023 · 0 comments

Comments

@MWFIAE
Copy link

MWFIAE commented Jun 26, 2023

Contact Details

[email protected]

Description

Api does display some misleading data for a malformed relay transaction

Steps to reproduce

If we take a look at the following transaction we see that the transaction does not contain any logs or transaction results.
https://devnet-explorer.multiversx.com/transactions/4452cb0ac0a467952e8e88e80e77ad5fc53d540cdc0346a900afe566d4ec795a

The api however extracted the method name, detected a multi transfer and even lists the tokens.
https://devnet-api.multiversx.com/transaction/4452cb0ac0a467952e8e88e80e77ad5fc53d540cdc0346a900afe566d4ec795a?withResults=true&withLogs=true

This is caused by the transaction being malformed, in this case the relay transaction contains a multi esdt nft transfer that doesn't use the correct receiver address in the inner transaction.

Also it would be great if the explorer could include some additional error messages in this case.

On which network is the bug manifesting itself?

Devnet

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant