0.7.6 Failed to accept block

[nxkoil]

started from height 70281 and continues on and on...

[2014-02-19 19:26:53.562] DEBUG: Failed to accept block 6543017927152953068 at height 70281 received from 109.230.224.65, blacklisting
 ...
  ...
  ...

[2014-02-19 20:52:50.703] DEBUG: Failed to accept block 15118384075972710084 at height 70336 received from node59.nxtbase.com, blacklisting


How to fix? or does it need a fix?

[Shin]

It's been there since I don't know when. There are more people having the same issue including me. Have posted everywhere tried to get the attention of the developers but alas, no response. Can we safely ignore this DEBUG message? Maybe I am missing the post with the answer somewhere. =/

Look at these posts:
- https://nextcoin.org/index.php/topic,4049.0.html
- https://bitcointalk.org/index.php?topic=345619.msg5225870#msg5225870
- https://nextcoin.org/index.php/topic,3950.msg37297.html#msg37297
- https://nextcoin.org/index.php/topic,1675.msg37159.html#msg37159

I mean, if there's going to be a fork, especially when it's just a couple of thousands block away (it was block 70.000 btw, which has already past), we need to get informed on HOW TO DETECT if a client we are using is running on a fork, HOW TO RESOLVE it, and finally HOW TO PREVENT this from happening again in the future. Think about how many uninformed users who are working on this fork and are doing transactions on it? what if that user is an exchange?

[nxkoil]

yes, more information would not harm. Even to ensure the users that those failures are not a problem.

Anyway, 0.7.6 seems to find more blocks  etc. than 0.6.2 yesterday:
 Accounts:23820 Blocks:66985 TXs:124854

Now 0.7.6: Accounts:24515 Blocks:70354 TXs:129281