Post
Topic
Board Announcements (Altcoins)
Re: ★[ANN] [NAV] NAV COIN - ANONYMOUS TECH. ● NAV 2.0 SOON ● NEW ROADMAP ● CHAT ●
by
soopy452000
on 03/05/2016, 09:36:19 UTC
I'm trying to download the whole blockchain using last commit from github in Linux (ubuntu).

I was stuck at block 2271722. It was not possible to download more blocks as the checkpoint gives an error:

Quote
ERROR: AcceptBlock() : rejected by hardened checkpoint lock-in at 2271723
ERROR: ProcessBlock() : AcceptBlock FAILED

OK, so I look at the source at:

https://github.com/navcoindev/navcoin/blob/master/src/main.h#L101

And I find the following checkpoints:

Quote
static const uint256 CheckBlock43 ("5f24d8893ab34814b691245e5bdac14f06867d9a9b7016a5d64a2e8e4d571b1c"); // Checkpoint at block 2271723
static const uint256 CheckBlock44 ("6afa0ca1da91252d17efaab0eabdb7deff60d80684e12d6045c3766dcc00d0f7"); // Checkpoint at block 2586565

Now I go to the blockexplorer at http://navcoin.org/block-explorer, and I see that the checkpoints that are hardcoded at the source code are wrong!!

http://www.navcoin.org/abe/block/28fe0c8048a2464cac916d2a699f8f7ce3a7d0facfc1c0001cef83b6a2b4b52b

Block 2271723 has a hash value of 28fe0c8048a2464cac916d2a699f8f7ce3a7d0facfc1c0001cef83b6a2b4b52b !!

Same thing happens with block 2586565.

After I removed these checkpoints from the published sourcecode, I am able to continue downloading the blockchain.

Can someone explain me how is possible that these checkpoints are wrong??

Thanks


Hi Mate,

It is indeed surprising that this is the first time we were reported of the same and ofcourse thank you very much for pointing the same. I will publish a new client fixing the issue mate.

And also investigate further why the checkpoint hash is wrong as well as why it came up now.

Thank you very much.

Warm Regards,
~SoopY~