Skip to content
This repository has been archived by the owner on Jun 7, 2019. It is now read-only.

Multisignature registration transaction always fails with error: 'Account is not a multisignature' #1122

Closed
SargeKhan opened this issue Feb 20, 2019 · 0 comments
Closed

Multisignature registration transaction always fails with error: 'Account is not a multisignature' #1122

SargeKhan opened this issue Feb 20, 2019 · 0 comments
Labels
🐛bug *easy lisk-transactions
Milestone
Improve transacti...

Comments

@SargeKhan
Copy link
Contributor

Expected behavior

For the multisignature registration transaction, the transaction asset contains signatures property and they should be verified against the keysgroup present in the transaction asset.

Actual behavior

The transaction fails because BaseTransaction tries to verify signatures against the sender. Since sender is not a multisignature account, it fails with 'Account is not a multisignature account'.

Which version(s) does this affect? (Environment, OS, etc...)

2.1.0-alpha.1
@shuse2 shuse2 assigned mitsuaki-u and shuse2 and unassigned mitsuaki-u Feb 21, 2019
@shuse2 shuse2 mentioned this issue Feb 25, 2019
Merged
shuse2 added a commit that referenced this issue Feb 25, 2019
@shuse2
Merge pull request #1136 from LiskHQ/1122-fix_multisignature_double_c…
f15a95e 
…heck

Fix multisignature double check - Closes #1122
@shuse2 shuse2 closed this as completed Feb 25, 2019
@karmacoma karmacoma changed the title Multisignature registeration transaction always fails with error: 'Account is not a multisignature' Multisignature registration transaction always fails with error: 'Account is not a multisignature' Mar 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
🐛bug *easy lisk-transactions
Projects
None yet
Milestone
Improve transaction processing effici...
Development

No branches or pull requests
3 participants
@shuse2 @SargeKhan @mitsuaki-u