Improve register multisignature group transaction validation

[reyraa]

Description

Lisk Core accepts the following configurations for a multisignature group which cause broken or confusing user experience as explained below:

• The required signatures number is equal to the number of mandatory members, but there are optional members too.
  • In this case the optional members never get to sign.
  • If an optional member signs the transaction before at least one mandatory member, the transaction becomes invalid.
• The required signatures number is equal to the number of mandatory and optional members.
  • The transactions need to be signed by every single member, practically turning optional members into mandatory.
  • This is not a blocking bug. But it leads to a confusing UX.
  • I believe we should make sure users set all members as mandatory in this case.

Additional Information

Lisk Desktop can add an additional validation layer to prevent registration of such groups, but if other clients do not perform these validations, we will end up with more problematic groups being registered.

[shuse2]

Closing this issue for no activity