feathercoin chain stuck at 33582

[normunds0ch]

are there any problems for the new users? I cannot find anything, but yesterday I downloaded a new (seemingly latest) wallet (version v0.8.6.1-beta) on Windows 7 and it does not download past block 33582.

I also downloaded the source code and compiled daemon on Linux - same thing.

I've tried deleting data and restarting - it stick again on the same block.

Apart from this block number being in a fork abandoned during 2013 June attack, I have not found any other significance of this number. Could I be landing on the wrong fork?

I'm running a number of other coin daemons and feathercoin is the only with this kind of problem.

[1715347661]

1715347661

[1715347661]

1715347661

[1715347661]

1715347661

[1715347661]

1715347661

[sumana]

what the developers says about this  ?

[normunds0ch]

Considering how FTC is at block 198171, I would say something is wrong on your end.


~BCX~

Definitely, that's why I'm asking - but if it is recent code fix (I looked at the latest commit and nothing there looks suspicious), or (?)

If I check peers, I see them having normal number of blocks. However for some reason they do not land in my blockchain.

When looking at log I see such entries:
2014-04-13 05:56:02 received block 44f36ca4115dae3ed9c73cf3cb10ee7deef36d0cb12477a080ee0f1db550e691
2014-04-13 05:56:02 ERROR: AcceptBlock() : block's timestamp is too early
2014-04-13 05:56:02 ERROR: ProcessBlock() : AcceptBlock FAILED

This (block 33583) looks like to be a valid block, but corresponds to the attack timeframe and therefore might contain some timestamp manipulation. Could it be that the current code denies such blocks as invalid, however historically they have been accepted and now are part of the "official chain"?

[stokecrypto]

update ur wallet

[rikkie]

Have the same problem.

[normunds0ch]

update ur wallet

can I kindly ask you which version are you running? I downloaded it yesterday and as far as I tell there are no later versions than 0.8.6.1; I downloaded the source code as well (and compiled Linux version that also stays on the same block); code also has not been changed yet.

Well, talking about latest changes - there is one that could affect:

-    enum { nMedianTimeSpan=11 };
+    enum { nMedianTimeSpan=13 };

The AcceptBlock() routine uses median time span to decide if timsetamp is valid or not. I assume changing it might affect certain blocks with not fully cosher timestamps.

Edited: that was it - I changed it back to enum { nMedianTimeSpan=11 }; re-compiled and it works now. Do not want to compile QT client on Windows, but at least Linux version is on the way of getting the full chain now... Thanks guys for inspiration to look around 

[ieike]

I've met the same error yesterday.  At that time the commit hash was fc929ab2c910af1c4b69b5dc4e7540ba78a48df4.

https://github.com/FeatherCoin/Feathercoin/commit/fc929ab2c910af1c4b69b5dc4e7540ba78a48df4

On the latest commit (hash is cf7c8fe19b0ec5eddfe783345c62883bf9afcf4c), it has been fixed!

https://github.com/FeatherCoin/Feathercoin/commit/cf7c8fe19b0ec5eddfe783345c62883bf9afcf4c