-
Notifications
You must be signed in to change notification settings - Fork 39
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
Error: 3 INVALID_ARGUMENT: invalid transaction: Missing inputs. Code:-25 #136
Comments
Can confirm, this happens once in a while but not frequently, so if whoever tries to reproduce this bug can't do it in the first run, try e.g. waiting 48 hours and then retry it with the same mnemonics and/or addresses. |
confirmed after running above snippet |
Also, all UTXOs are reported as spendbable:
|
I have a script running right now with a mnemonic that throws this error. Feel free to use this mnemonic to reproduce and triage this issue: https://github.com/dashameter/dash-dapp-autofaucet/blob/sendTest/sendTx1.js#L36 |
please try retesting it |
failed retest:
|
Triage sheet updated. Thanks |
@dashameter @SamKirby22 should be solved from now - please double check (have a look at dashevo/wallet-lib#232) |
retest failed:
|
Hey @Alex-Werner @markin-io , chaining of transactions was supposed to help here. Could you please refer? |
Hey @dash-maverick @dashameter This seems to be the same situation like the one we debugged this week with @thephez As a result, we have a situation where the wallet tries to spend already spent UTXOs, because of the gaps in the TX list. My suggestion to @dashameter would be to choose a different set of @dash-maverick Also, it is worth investigating why the node which is out of sync is still considered a valid source of truth. |
@markin-io thanks for the hint. I actually haven't been using the dapiAddresses for the last test. I just re-ran the test a few times with and without the unsafeOptions and this is the error log I get now: https://gist.github.com/dashameter/7996c104ca3271c446b57d4ab3b04e97 Were you able to run the script successfully and have it send txs? |
@dashameter hey! Apologies for the late response. Just finished checking out these: I managed to reproduce the Those are "heavy" wallets with around 500 transactions, so I assume some of them are not making it to the wallet store, and hence we have incorrect UTXO selection. So, no matter what DAPI addresses are chosen, it will still be the same. Please, discard my original assumption about the node being out of sync. We are continuing to narrow down this problem. In the meantime, I'd suggest using a fresh wallet, because, from my current experience, problems start appearing if the wallet has more than 300 transactions in it. |
This is even a known workaround connected to the state of having > 300 transactions - that way metadata can be obtained without having the light client fully implemented. |
@dash-maverick can you share the known workaround ? |
I made a mistake in my previous comment and fixed that right now with a bit of more explanation |
As per triage, unable to reproduce. Agreed to retest. |
waiting for testnet to be online for retest |
Expected Behavior
Spend funds from an account with a balance
Current Behavior
Get error as per title
Possible Solution
Investigate generated transaction inputs / script
Steps to Reproduce (for bugs)
Your Environment
nodejs 12.16.2
dash@3.14.1
The text was updated successfully, but these errors were encountered: