Quote from: effort on August 08, 2014, 01:53:03 PM

Quote from: Biomech on July 29, 2014, 03:39:18 PM

Quote from: mikeyfinn on July 29, 2014, 02:47:15 PM

Quote from: effort on July 29, 2014, 02:42:43 PM

Quote from: corsaro on July 29, 2014, 06:21:10 AM

On my mac new mandatory update 1.0.3 works fine. If you note that 1.0.3 does not synchronize you are probably still on wrong fork due to a bad "blk0001.dat" file

1) close 1.0.3
2) make a backup of the file ~/Library/Application Support/Sync/wallet.dat
3) delete everything from ~/Library/Application Support/Sync/ except "wallet.dat" and "Sync.conf" (if Sync.conf is not present, create it)
4) check that "Sync.conf" contains only these official nodes:
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198
5) download bootstrap.dat from https://dl.dropboxusercontent.com/u/80376827/bootstrap.dat and place it inside ~/Library/Application Support/Sync/
6) open 1.0.3 and wait that bootstrap loads (be patient: it took on my mac at least 30 minutes)
7) as soon as bootstrap import ends, your wallet will synchronize fine

done all this yesterday and again this morning. Works exactly as you described, but the result is still negative. Two of Mined are 'Generated but not accepted Mined'.
v1.0.2 can see Mined and Received coins above them. If the last Received coins would be the wrong fork that would be understandable. But the Mined are credited over 12hrs earlier.

Is there way to fix 'blk0001.dat'? It would be a pity to give up now.
Let's imagine, tomorrow Sync is $10k and next wallet update will conflict couple of Syncs; that will bother a lot! Why Sync wallet is a puzzle? I have no assurance in it now. Take the Dogecoin walet, no puzzles and updates are easy peasy.

How many times must it be said? STOP USING 1.0.2!!!! It is the WRONG FORK!!! That means it is a fantasy world that has no basis in reality. Anything you think you earned there AFTER block 86400 DOES NOT COUNT. Stay on the right chain.

I'm seeing some confusion here. If I read this correctly, he was using 1.02 as a reference, showing a different balance before upgrading.

Still, It is likely the blocks were produced after the fork, so first off VERYIFY that. If it staked after the update on the wrong chain, well, you wasted some electricity. Not a huge deal, but I understand the annoyance.

However, if you are certain that you have transactions not confirming after the update that are BEFORE block 86400, you have some things to do.

First off, forget blk0001.dat. It's just a piece of the blockchain. It don't matter to recovering your coins. There is one file that you should be concerned with, and another you need. The first is wallet.dat THAT is the one that contains your private keys, and therefore access to every transaction you've made on the blockchain. The other is the configuration file. Get rid of everything else in your data directory and resync.

If that still don't work, use the dumpwallet command to export your wallet to a text file. Reimport it into a new wallet, and all will be well.

Hello Biomech,
Thank you for info. I didn't know about dumpwallet command, to be honest. I'm trying to find 'stepbystep' how to do it for the last 3 hours

, not much details of it available in the net. Please, can you help?
BTW, yesterday, my wallet got one more conflicted 'Mined'.
http://www.doipo.co.uk/wp-content/uploads/2014/08/sync_3q.png

Effort, this is called an "orphan". It means that someone else on the network generated a block that was accepted just before you generated your block. Therefore, the block you solved was rejected by the network, as it was based on stale work.

Don't worry, when you produce an orphan, you don't lose the stake. Your wallet will generate a stake in time worth equal to or more than the one you lost.