Wallet halted temporarily

After an upgrade to the latest version of bitcoind, the wallet suddenly has a book keeping problem. It’s not the first time Bitcoin Core fails at balances (this happened during the first malleability issue). Right now it’s claiming the balance is “-120? instead of “120?. No need to worry of course, we have the full wallet and the unspent coins are there, but the software is buggy.

We’re currently looking for a workaround, in the worst case we will re-build the whole wallet manually, from scratch, and then resync the blockchain. That would take a long time, so we are rather focusing on a quick solution. For now.

(ps. before I even started working on this, I manually sent coins for all pending withdrawals from my personal Trezor - there shouldn’t be any pending outgoing transactions)

Thanks for your patience, more updates will be posted.

Estimate: right now it’s hard to know, because it depends on which idea works, and how long they take to implement. If none of them do, we might be looking at 24 hours at least.

The current plan is:

1) Try -rescan. This is where we’re at (unless I’m busy working on the issue and haven’t updated the blog entry yet).

2) Try -upgradewallet (and then -rescan maybe).

3) Give up, rebuild the whole wallet from scratch, making sure all deposit and archived addresses are included, while old change addresses are thrown out.

(1) It worked!!!

Now if only we can get rid of this ‘transaction not final’ problem. Light at the end of the tunnel.

Noone seems to know whether it’s possible to tell bitcoind not to send RBF-able transactions, Google didn’t help either other than to say this is normal, and transactions will be recognised by blockchain.info after one confirmation. Trading has been re-enabled.

Update on the nLockTime / RBF issue (a non-issue, unless you’re looking at blockchain.info to try to view a 0-confirmation transaction):

[01:02] <Luke-Jr> BB-Martino: nLockTime did not change in 0.12.x that I recall[01:02] * Luke-Jr checks[01:03] <BB-Martino> Luke-Jr: I’m just stating the facts. I upgraded from 0.11.x to 0.12. Since the upgrade, transactions are claimed to be ‘rejected’ by bc.info. So clearly it changed somewhere in between.[01:04] <Luke-Jr> I’m wrong[01:04] <Luke-Jr> <0.12 did current minus 10 blocks[01:04] <Luke-Jr> 0.12 does current[01:04] <BB-Martino> any way to configure it?[01:04] <Luke-Jr> no, but you can hack src/wallet/wallet.cpp[01:04] <BB-Martino> ummm… thanks.[01:04] <Luke-Jr> find txNew.nLockTime = chainActive.Height(); and change it to txNew.nLockTime = chainActive.Height() - 10;[01:05] <BB-Martino> Thanks.[01:05] <bounce> that’s computer hacking. a felony.