Quote from: RentaMouse on November 23, 2014, 02:02:10 AM

I've had a look through the daemon log on my node and I think I can see what has happened, but I cant offer much of a solution atm.

Problem starts with this node appearing on the network, at around 21:00GMT:

trying connection 46.105.118.15:16665 lastseen=365747.2hrs
connected 46.105.118.15:16665
send version message: version 70000, blocks=24624, us=81.107.175.74:16665, them=46.105.118.15:16665, peer=46.105.118.15:16665
Added time data, samples 15, offset +1 (+0 minutes)
nTimeOffset = -7 (+0 minutes)
Moving 46.105.118.15:16665 to tried
receive version message: version 70000, blocks=24568, us=81.107.175.74:63435, them=46.105.118.15:16665, peer=46.105.118.15:16665

At that point it is 56 blocks behind the rest of the network, but rather than get back in sync it starts broadcasting its own chain, which has a far higher trust than the existing one so it gets accepted as valid and replaces the existing chain.

For that to happen the node in question, or nodes connected to it and not the rest of the network, must be staking a much larger number of SPARK than the rest of the network put together. I've had a look through a few of the blocks produced and each appears to generate a stake interest of around 9SPARK, with an output of 1038SPARK to a wallet - I believe this is because a large wallet will split the coins into smaller chunks for staking. The outputs I checked all went to the same address:

SUpCAdvbrsmm99EPxr7ob8DWuLK2fT9Zpk

One other thing I can say is that the node in question hadnt updated to v1.3, as my node started rejecting its blocks after 24630 as they were using the new diff calculation. My node then started blocking it and other nodes pre1.3 as it assumed they were "misbehaving", so I cant tell whether the "problem node" is still on the network or not. Only other info is that the problem node IP address traces back to OVH server hosting in France, so its probably not a domestic holder, more likely a pool or exchange.

There weren't a huge number of txes in the 55 blocks lost, but that doesnt really matter, unless Bittrex have another way of seeing their withdrawals/deposits they cant be sure of making their books balance, which isnt a good thing for an exchange. I'm now looking to see if I have have a copy of the "old" blockchain backed up anywhere, if so it might be possible to do something with checkpoints and another wallet update....

...when I get peerlist from my 1.3 client (for the insight), it lists a lot 1.2 and 1.0 clients... and stops @ height 24630 ...for the moment.
my windows wallet (1.2 atm) actually went over 247nn somewhat and yielded a massive stake drop (and I just leaved 1/5th available for staking)...
I see if I get that 1.3 wallet to xcompile fine as one monolithic exe so we hopefully don't have trouble with missing deps anymore.

I'm taking the scenic road, thus also paying 'new ann thread with all the info plus further administrative stuff'-valley a visit while beating through coders gulch Wink