-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
atc.gatherSignatures() failing with Multisig #821
Comments
Are you using a multisig that only requires one signature? |
@winder Yes, it's a 1 of 2 multi-sig. I started looking into the problem and realized that was a factor. Sorry it wasn't in the repro steps. I figure something like this in place of this line would fix it... Line 76 in 7469c41
|
@acfunk thanks, that sounds right to me as well. Would you like to make a PR? |
@winder I was going to, but I couldn't figure out how to test it locally. Editing the file in node_modules had no effect - too much optimization by Vite it seems. And I'd feel bad submitting a PR that I hadn't tested... unless you told me to. |
@algochoi could you provide some testing guidance here? |
We could have a mocha unit test here: https://github.com/algorand/js-algorand-sdk/blob/develop/tests/10.ABI.ts something like:
|
I submitted a PR #822 |
atc.gatherSignatures() failing with Multisig
When gathering signatures for an AtomicTransactionComposer group with a multisig transaction, the following error is thrown:
Not enough multisig transactions to merge. Need at least two
Your environment
algosdk 2.5.0
Steps to reproduce
TransactionWithSigner
s that have a MultiSig signerconst signedTxns = await atc.gatherSignatures()
Expected behaviour
signedTxns
contains signed transactionsActual behaviour
error is thrown
Not enough multisig transactions to merge. Need at least two
The text was updated successfully, but these errors were encountered: