Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daemon does not want to accept any more blocks at height 166599 #67

Closed
minerrocks opened this issue Apr 19, 2018 · 3 comments
Closed

Daemon does not want to accept any more blocks at height 166599 #67

minerrocks opened this issue Apr 19, 2018 · 3 comments

Comments

@minerrocks
Copy link

Daemon does not want to accept any more blocks at height 166599

https://github.com/valiant1x/intensecoin/blob/e60b3da93e809446f545ace4ed0b112c8a214190/src/cryptonote_core/cryptonote_core.cpp#L1049

2018-04-19 21:33:58.639 [RPC0] ERROR cn src/cryptonote_core/cryptonote_core.cpp:1049 mined block failed verification

@valiant1x
Copy link
Collaborator

The daemon exploded at block 167000. It seems there is special logic every 1000 blocks to prepare some sections of the database. When it tried to prepare the previous batch of 1000 blocks at 167k, somehow it absorbed the v3 fork. It seems to have placed any databases that were active at that time into an unrecoverable and corrupt state, leaving them in an odd v4-v3 fork hybrid state. Popping the blocks does not work as the number of already generated coins became based on the old v3 chain, and therefore the v4 chain is unable to make new coins because the block rewards don't match up.

I believe this was due to the absence of checkpoints at 166134 or later. In the absence of definitive checkpoints, despite the software being instructed to fork v4 at block 166134, it took the liberty of reverting to v3 at 167k. I have updated the checkpoint file and corresponding hash in the code.

To resolve: You will need to git pull the latest commit (5688302) and rebuild. That should resolve issues with forking again at 167k.

For now, your blockchain is corrupt. I'm not sure if the database will autocorrect when the network reaches 167k again, but if you want to use the daemon between now and then, you will also need to completely wipe your database and either re-sync from scratch or sync the bootstrap/snapshot file.

@BKdilse
Copy link

BKdilse commented Apr 20, 2018

Just saw this today too.

After compiling new daemon, do I have to remove the blockchain, or only remove it if it does not progress further?

EDIT: Just tried, and it does not progress, so now synching from scratch.

@minerrocks
Copy link
Author

The issue is resolved as network goes further, it was not about syncing, but about daemon refuse mined blocks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants