I used to mine bitcoins and stopped about two years ago. At that time I was using Bitcoin-QT 0.8.5 Beta. The computer has been powered off since then, and my wallet.dat is still on that computer.
Can I still use that version, or do I have to upgrade to the latest Bitcoin Core? Besides backing up my wallet, should I do anything in preparation before I reconnect the old computer to the Internet, or before upgrading software? It says the wallet is out of sync and the block is 95 weeks behind.
Any guidance will be appreciated.
Following a bitcoin core issue on
debian stretch which was resolved on the master branch, I am now running a pre-release test build. Each time I exit
bitcoin-qt, I have to wait about 5 minutes until final shutdown occurs. My debug file is showing:
2016-12-20 19:58:55 AcceptToMemoryPool: peer=3: accepted 2b8c3...5c14 (poolsz ... 2016-12-20 19:58:56 AcceptToMemoryPool: peer=3: accepted 4a3d1...7e0e (poolsz ... 2016-12-20 19:58:56 tor: Thread interrupt 2016-12-20 19:58:56 scheduler thread interrupt 2016-12-20 19:58:56 torcontrol thread exit 2016-12-20 19:58:56 opencon thread interrupt 2016-12-20 19:58:56 addcon thread interrupt 2016-12-20 19:58:56 msghand thread interrupt 2016-12-20 19:58:56 net thread interrupt
This is where it hangs for a few minutes, then:
2016-12-20 20:05:58 Imported mempool transactions from disk: 10932 successes, 476 failed, 0 expired 2016-12-20 20:05:58 Shutdown: In progress... 2016-12-20 20:05:58 Stop 2016-12-20 20:05:59 Erased 1 orphan tx from peer 5 2016-12-20 20:06:01 Dumped mempool: 0.063746s to copy, 1.55051s to dump 2016-12-20 20:06:01 Shutdown: done
I have not experienced this before ever on any system. I am not seeing a similar issue when shutting down
bitcoind (EDIT actually it does happen with
bitcoind at times). I am wondering if anyone is aware of any pending change (on master branch for future release) which would explain such behavior (I worry this may be related to
debian stretch, but my hardware is new, very cheap and hopelessly slow on known benchmarks, which may also be the cause of this).
To save time, I synced the blockchain on my laptop for import to my Raspberry Pi node. I had set txindex=1. When setting txindex=1 on my Raspberry Pi and pointing the data directory to my previously synced blockchain, launching bitcoin-qt warns me that reindex must be requested if txindex previously was set to 0.
This doesn’t seem right. I’ve already indexed these blocks. Is there a way for me to move my synced and indexed blockchain from one machine to another without having to reindex?
Hello I sent about $ 300 worth of BTC and it never got confirmed. I then used the –zapwallettxes=1 command to get the BTC back and resend with max amount of fees, but it still didn’t confirm on the other end. I tried this several times with different addresses, but nothing has worked. I am willing to pay somebody to help me retrieve this BTC. I can provide any details necessary to aid this process. Any help would be greatly appreciated!