-
Notifications
You must be signed in to change notification settings - Fork 65
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
Imported a private key, the balance shows correct but can't send funds #202
Comments
#182 this pr should fix it. |
in which version this fix to be expected? I'm hesitant to run 8.x.x-RC |
actually I looked at the commit, looks like an easy fix, I'll just for from 7.17.3 and build my own with this fix. Thank you |
This fix is in RC4. |
Are we able to close this issue? |
yes |
Should not have closed that, the 7.17.3 does not even have a variable |
@Jongjan88 there is no RC4 as well... no wonder DGB has hard time to grow in price if things are broken for so long (sorry to say) |
@skironDotNet it only affects old wallets. Coins in blocks older then 9999999999 so the problem is not that old. but will be fixed in rc4. You can build DigiByte 8 dev branch. |
So the Dev is stable enough to just send funds? Many thanks |
It is rc3 with some small changes. Make first good backups off your private key. And first test small amount. |
I just complied develop and tested, and it works. I would not close the issue until RC4 is released. But feel free to close, since this is technically fixed via #182 |
Digibyte-qt v7.17.3 for Linux
After importing a private key with confirmed balance, the balance is shown but coin control window shows no inputs.
When trying to send, the wallets displays "The amount exceeds your balance." when clicked "Use available balance" it turns entry field to 0.
The chain is synced. In debug console list-unspent shows nothing.
Can this be related to the fact now HD wallet is forced in this version to must be enabled and the coin control or otherwise UTXO check doesn't include imported keys?
The text was updated successfully, but these errors were encountered: