-
Notifications
You must be signed in to change notification settings - Fork 813
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
BTC that are send to change addresses don't show up in walletbalance or coins #498
Comments
debug.log after a rescan: https://gist.github.com/gnorbsl/e3a2a33d7b6ae49d671eef5158b6932d I created a new account and imported the public key from the broken account:
I noticed that the changeDepth is one less than on the original account but I assume it has to be higher or at least the same? Also it shows the funds as confirmed but they are unusable because I cant access the coins |
I found that the bug is reproducible. I first create a wallet and then I create a second watch only wallet with the public key from the first one. then I create raw transactions with a receiver and the generated changeAddress in the sendTo array and sign/send it. As soon as the changeDepth reaches 12 the change becomes unusable. |
This should be fixed with these changes: https://github.com/bcoin-org/bcoin/pull/503/files Thanks to @nodar-chkuaselidze for fixing it so fast. |
@gnorbsl Are you still seeing an issue with the fix? |
@tuxcanfly No this fix solved the problem described in my issue. |
Hi,
I use
var changeAddress = await wallet.createChange('default');
to generate change addresses that I use for raw transactions. It seems that sometimes those addresses are not recognized by the wallet and the funds that are send to the change address are not usable anymore.One example of my console output:
The Transaction is created and signed successfully, the transaction in the chain:
https://live.blockcypher.com/btc-testnet/tx/3283380520b41eaf2e7a62e15801bfb0ba2372890a0cf304823e4f9996d148ed/
The output of the default account of this wallet after the transaction was made:
The Node is fully synced and previous transactions with the same method worked too, a rescan of the block with the transactions and previous blocks didn't change the balance.
Thread on Slack for more information:
https://bcoin-dev.slack.com/archives/C4VSMQNFJ/p1529502702000257
The text was updated successfully, but these errors were encountered: