You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
When second person (not original sender) use signMultiSignatureTransactionWithPrivateKey with includeSenderSignature, it overwrites the transaction.signatures[0]
Steps to reproduce
Register a multi-signature account (e.g 2 mandatory)
Sign a multi-signature registration transaction from account1
Sign a multi-signature registration transaction from account2
Observe the signatures of account1 is replaced with account2
Additional information
This issue can be resolved by
Get public key from const signerPublicKey = lisk_cryptography_1.getPublicKey(privateKey);
Expected behavior
signMultiSignatureTransactionWithPrivateKey
should include correct signatures according to keys.Actual behavior
signMultiSignatureTransactionWithPrivateKey
overrides signaturesWhen second person (not original sender) use
signMultiSignatureTransactionWithPrivateKey
withincludeSenderSignature
, it overwrites thetransaction.signatures[0]
Steps to reproduce
Additional information
This issue can be resolved by
const signerPublicKey = lisk_cryptography_1.getPublicKey(privateKey);
Which version(s) does this affect? (Environment, OS, etc...)
5.2.0
The text was updated successfully, but these errors were encountered: