I use Monero 'Lithium Luna' (v0.12.3.0-release) CLI only.

I opened another thread that might or might not be related to this one.

I have 3 stagenet daemons running (for testing purpose, not on the same system), all running the version mentioned above.

2 of them show strange logging lines like these:

[ INC] Sync data returned a new top block candidate: 136994 -> 250777 [Your node is 113783 blocks (79 days) behind]

Strange thing about this message is, that it shows another block height. In between those messages I can find the real log info which says:

[ INC] Synced 137854/146135

When triggering the monerod status command both daemons show V1 (see the other thread). The stagenet daemon not producing such messages shows V7 instead.

This is one obvious difference I could find, but I am not sure what to do about it.

It keeps on displaying those logs even after completing the synchronization. That's why I started all over - to no avail.

Additionally every now and then the following message appears in the logs:

[ INC] peer claims higher version that we think (9 for 232290 instead of 7) - we may be forked from the network and a software upgrade may be needed

1 Answer 1


It looks like the daemons claiming to be 79 days behind have found a peer (or peers) which are running a modified version of the monero stagenet protocol, and are therefore unable to sync. They'll only be able to once they find a peer on the correct chain.

Alternatively, it might be a monero fork (since the P2P comms appear to be compatible) and they incompetently failed to modify the network ID.

To try to get out of this mess, you can try manually banning those peers that claim v9:


The IPs are in the messages.

One thing isnot clear: what makes you think some of the logs are not real ?

  • Sorry, real might not be the right choice of words here. I was referring to the actual syncing log messages including the correct block height.
    – rocksteady
    Commented Aug 23, 2018 at 9:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.