Closed yenkhoon closed 4 years ago
@b00f @jeansoonsik
Can you explain ore how the signature verification can fail?
For any signature we iterate all the public keys to match them with the signature. Sequence should not be random here: In multi_sig sequence is same as tx_id which is not random and it is sequential. In non multi_sig there is always one public key and one signature.
YK & Mostafa,
I get this same error message while I testing for multiSig-NFTs by running this '/maxonrow-go/tests/multisigNFTs_test.go'.
You can refer this test-case :
Also under the issue been prompted out before this : -- https://github.com/maxonrow/maxonrow-go/pull/89
I get this same error message while I testing for multiSig-NFTs
@githubckgoh1439 Which message?
Hi, Mostafa
I run this test-case under file of 'tests/multisigNFTs_test.go' : [ Create MultiSig Tx for NFTs [Approve-token] - Happy path - commit.' ]
and get this error : [ return nil, sdkTypes.ErrUnauthorized("signature verification failed; verify correct account sequence and chain-id" + string(signBytes)) ]
Please help to check, since last Wednesday.
@githubckgoh1439 This is because it has wrong tx_id. is should be 3, not 0.
We cant certain the pubkey and signature are matching, slice is random the sequence is random. Once the signbytes failed to get verify, we will get signature verification error.