Quote from: MinermanNC on September 13, 2015, 03:22:31 PM

So for those of us who killed siad using task manager, does this mean we have also lost our coins and any uploads stored in new wallet? Hard to imagine that.

Failing to save local blockchain database properly should only mean your local machine/wallet has inconsistent state (for example, no transactions seen, or no coins received).

The blockchain should be resynced (the old/corrupted blockchain databased should be removed) and the new/consistent blockchain state should reflect the changes made to your wallet/coins.

It is better to unlock your wallet only after the blockchain was synced.

Also, mind, one confirmation (one block mined) can take very long time. This would continue until the difficulty is recalculated for the current hashing power. And this should happen after some number of blocks (500 minus whatever # found so far) were mined.

Seems like some time ago, a lot of hashing power joined the network, mined a lot of coins, dumped some. The mining difficulty was raised, that hashing power left the network. The current hashing power is not enough to keep finding block every 10min. This should change when the difficulty is recalculated. That is just one unfortunate/ugly side effect of POW (proof of work) algorithm of securing the blockchain. Mining pools should scale this problem down.

fundomatic

Posts

Merits