BitcoinUser2016
commented at 1:14 am on March 15, 2016:
none
Hi,
I run a bitcoin server which have acting strange the latest 3-4 days. For some reason the unconfirmed balance when running bitcoin-cli getunconfirmedbalance shows up as 50.589243 BTC which of course isn’t true.
How do I reset this? Why did this occur? Tried both v0.12 and v0.12.99, same problem.
Thanks in advance,
Nori
kirkalx
commented at 7:10 am on March 15, 2016:
contributor
Are you sure the value is wrong? What sort of result are you expecting?
jonasschnelli added the label
Wallet
on Mar 15, 2016
MarcoFalke
commented at 11:19 am on March 15, 2016:
member
Did you try listunspent 0 to see if there is anything suspicious.
BitcoinUser2016
commented at 12:30 pm on March 15, 2016:
none
Yes. I’ve never had this problem before. The volume is exactly the same. It’s been stuck at 50+ bitcoins for about 5 days now. There is no way 50 bitcoins have been sent to my wallet.
For example: When someone sends 1 bitcoins getunconfirmedbalance will show as 51 BTC and then go down to 5 BTC again once its confirmed.
Yes. Iv’e tried listunspent. Lists lots of transactions saying “confirmations: 0” which already have thousands of confirmations. Some dated 2015 with over 25.000+ confirmations and still says “confirmations: 0”. Like this one:
https://www.blocktrail.com/BTC/address/16F4Bzkk6xaFktqSopACKn18rCRWCWgdW3/transactions
“txid”: “a34a18358937a5b9a9fff8281491de57a9c7942217d43bb469eef5d5113d50fc”,
“vout”: 1,
“address”: “16F4Bzkk6xaFktqSopACKn18rCRWCWgdW3”,
“account”: “usedaddress”,
“scriptPubKey”: “76a91439811d6af01a4337137356cb88488f9f1b6348ed88ac”,
“amount”: 0.23509566,
“confirmations”: 0,
“spendable”: true
It all started around 3 days after I’ve upgraded from 0.11 to 0.12. My wallet is around 20 MB. Should I rescan?
MarcoFalke
commented at 12:37 pm on March 15, 2016:
member
Conflicted transactions count toward the unconfirmed balance, IIRC.
sipa
commented at 12:41 pm on March 15, 2016:
member
That transaction is a double spend that did not make it into the block
chain. 0.12 deals differently with those; see the release notes for more
information.
Running with -rescan once will fix the problem, by explicitly marking it as
conflicting with the block chain. After that, you can choose to remove such
transactions from the wallet with abandontransaction.
BitcoinUser2016
commented at 12:47 pm on March 15, 2016:
none
How and why does a transraction become conflicted? Will do a rescan then. Any idea how long this can take?
sipa
commented at 12:56 pm on March 15, 2016:
member
You always had these conflicting transactions in your wallet. Up to 0.11
they were just not counted towards your balance, as a heuristic was
determining they couldn’t be accepted (they were not accepted into your own
mempool). Due to the large changes that the mempool underwent in 0.12, that
heuristic is no longer usable, so the wallet now tracks conflicts by
itself. A rescan will let your wallet go through history and gather that
information.
BitcoinUser2016
commented at 1:00 pm on March 15, 2016:
none
The transaction remains in listunspent, and the balance of ‘getbalance “*” 0’ remains the same. I confirm that I have run -rescan already on this wallet.
Any ideas what could be going on here? It’s remained in this state at least for 8 hours so far.
laanwj renamed this:
saved
unconfirmedbalance shows fake amount (50.xxxxx btcs)
on Mar 17, 2016
laanwj reopened this
on Mar 17, 2016
laanwj
commented at 2:31 pm on March 17, 2016:
member
@morcos ^ Abandontransaction returns nothing, but still it seems that the transaction is not abandoned, any idea how to further troubleshoot this?
morcos
commented at 3:38 pm on March 17, 2016:
member
issue identified, working on a fix
morcos
commented at 2:55 pm on March 18, 2016:
member
@bittylicious#7715 should fix your issue. getbalance "" 0 and getbalance "*" 0 are unreliable and are not fixed. But you can use getbalance and getunconfirmedbalance. listunspent should also be fixed.
laanwj closed this
on Mar 23, 2016
BitcoinUser2016
commented at 0:19 am on April 30, 2016:
none
@morcos Wow, I am truly impressed by your commitment. Ever since I created this thread (and the weeks before that) I had to accept that I will always see a buggy unconfirmedbalance for some reason. Nor did a rescan or reindex work which was a pity since it took quite some time to redownload the blockchain. So, by coincidence I read the changelog for the latest version 0.12.1 and I saw this thread embedded.
Haha TL;DR: Thanks for solving this!!! I now have 0.000000 as unconfirmed balance because of your fix :D Finally!!! Keep up the good work guys. What you do for this community is truly amazing. Much love to you all. Take care!
MarcoFalke deleted a comment
on Dec 25, 2018
MarcoFalke deleted a comment
on Dec 25, 2018
markaw67
commented at 3:48 am on December 26, 2018:
none
You had better be sure you can prove that that balance was fake.I happen to no that it wasn’t and why would someone question someone else’s information without consulting with the owner first makes sense doesn’t it yes it does.
borisdon32
commented at 8:33 am on December 26, 2018:
none
Please I’m in need of a fake generator . That can send coins to your block chain and it will show up and later disappear
This is a metadata mirror of the GitHub repository
bitcoin/bitcoin.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2024-11-17 18:12 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me