We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Runtime transactions can have multiple signers. We should display them all.
Currently, Nexus's API only gives us the first signer, but that is going to change:
When the missing data becomes available, Explorer should be able to show multiple senders in the "From:" section of Runtime TX details.
Example TX with multiple signers: 9b6f77229709326983fa513d33aa0972a7543197118f4454693fe13541fdf26b
9b6f77229709326983fa513d33aa0972a7543197118f4454693fe13541fdf26b
The text was updated successfully, but these errors were encountered:
csillag
No branches or pull requests
Is there an existing issue for this?
SUMMARY
Runtime transactions can have multiple signers. We should display them all.
DESCRIPTION
Currently, Nexus's API only gives us the first signer, but that is going to change:
When the missing data becomes available, Explorer should be able to show multiple senders in the "From:" section of Runtime TX details.
Example TX with multiple signers:
9b6f77229709326983fa513d33aa0972a7543197118f4454693fe13541fdf26b
The text was updated successfully, but these errors were encountered: