Open statictype opened 1 year ago
This is probably intentional, as I disabled the button if no callData
is available for this pending transaction.
We should think about this case, how to show multisig transactions we are missing the callData for. This could be transaction triggered by other multisig apps i.e. .
Maybe show the whole transaction in a "disabled" state with a info to why this transaction can not be viewed & signed with our multisig app? cc @Goranch3
i think we should allow the user to paste call data in this case. the call data was there, but for some reason was not stored properly. we could also allow users to remove a pending transaction from the UI.
Even if the multisig has pending proposals, the UI doesn't allow signing them. Looks like for the respective proposal, the
RuntimeCall
isundefined
so the button is disabled