Current behavior
Currently, we can see the section "Co-signature received" for aggregate bonded transactions. This section shows public keys for accounts that are cosigned aggregate bonded.
Screenshot:
Expected behavior (improvement proposition)
Consider listing those that have and have not signed aggregate bonded transactions. So the proposition is to list all addresses (we want to present address instead public key) that can sign a transaction. And mark with tick sign addresses that are already signed.
It would be a great simplification for wallet implementation if that information would be returned by Rest API by aggregate transaction hash.
How it looked in the old NEM NCC wallet (addresses replaces by names because of presence in address book):
Something to re-think: How to present multisig-multilevel trees? Flat list with leaves only?
Current behavior
Currently, we can see the section "Co-signature received" for aggregate bonded transactions. This section shows public keys for accounts that are cosigned aggregate bonded.
Screenshot:
Expected behavior (improvement proposition)
Consider listing those that have and have not signed aggregate bonded transactions. So the proposition is to list all addresses (we want to present address instead public key) that can sign a transaction. And mark with tick sign addresses that are already signed.
It would be a great simplification for wallet implementation if that information would be returned by Rest API by aggregate transaction hash.
How it looked in the old NEM NCC wallet (addresses replaces by names because of presence in address book):
Something to re-think: How to present multisig-multilevel trees? Flat list with leaves only?