Topic: My Bitcoin-QT blockchain died. - page 3. (Read 6903 times)

Your browser has nothing to do with the operation of Bitcoin Core.

What are the specs of your machine? How does Bitcoin Core fail? What do you do that causes it to fail?

Please post your debug.log file.

More full nodes are better, but they do not contribute to the creation of blocks (aka confirmations). More full nodes will not help confirmations be faster.

But more full nodes would be better or not?  Do installations of Bitcoin-QT contribute to the confirmation process or not?

Probably not, I never had that problem. Have you think about the problem being with your computer? BSOD or improper shutdown can obviously corrupt the blockchain on your computer especially when you are synchronizing. Test your ram and your hardware for errors.
The backlog of transaction is not related to the client itself. The problem is with the blocksize and the transaction volume.

I don't know what exactly causes this. What exact bitcoin client are you using? Because bitcoin-qt is the name of the executable for BitcoinCore, BitcoinXT and BitCoin Unlimited. I know that if you switch from Core to an Unlimited Client like BitcoinUnlimited or BitcoinXT, using your same block source, you will need to reindex. And if you build and index the full blockchain with one, go to start the other, you'll be SOL and have to do it all over again. I had to reindex when I switched to the Unlimited Client 3 times. It kept getting to 99% and then quitting out. Luckily I have a fast PC and internet, so it was only a total of 24H wasted. I suspect data corruption in your blockchain data, try deleting and re-downloading the chain from scratch. If your set on becoming a full node, you can try running with these CLI options.... -par={TOTAL NUMBER OF CORES*THREADS} -discover=1 -dns=1 -forcednsseed=1 -listen=1 -listenonion=1 -maxconnections=128 -maxreceivebuffer=20000 -maxsendbuffer=4000 -peerbloomfilters=1 -timeout=2500 -datacarrier=1 -datacarriersize=172 -maxoutconnections=64

That will get you a ton of active connections to the network. Manually prune out any connections that don't provide any services (from the debug console.) That will allow you to maximize your download rate. -par set to the maximum number of logical cores will maximize your processing time. On some older OS's, that don't set affinities very well (like win7) I've found setting par to double your available logical cores can also help.

Now that network and CPU is taken care of, I find my biggest limiting factor is actually disk sequential read write speed. If you can, put the blockchain data on an SSD or RAID0 array. That will likely make it a lot faster to sync or index.

Once you've fully synced, you can use the -prune= to delete the older blocks and save space while still maintaining a full node.

I've been running Bitcoin-QT at night for months trying to build a blockchain.  I changed to 24/7 days ago and was up to July of last year.  Cold nights I started with Slush again after 2 years.  Running an S5, with a return of 45% of electric cost which makes it cheaper than propane.  I had an old address on Slush and tried to change it.  I use Firefox. Repeatedly for days with email exchanges with Slush the problem, mash the cancel the address change button (because it wouldn't change) and it would return to a login screen that doesn't work.  A Slush rep told me it might be my browser.  I upgraded Firefox to 64-bit from 32.  I soon got a BSOD on the Win7 machine.  Now after reverting to 32-bit Firefox, Bitcoin-QT won't run.  Rescan fails and am reindexing now.  And the Slush problem is unresolved.

Was this BSOD intentional by Mozilla?  BSOD seems to kill a blockchain with its abrupt termination making reindexing necessary.  Do they feel killing a blockchain is politically correct?  No wonder there's such a backlog of confirmations and long delays.  Nobody in their right mind is going to run Bitcoin-QT and contribute to the chain upkeep.

What's the solution?

soy