inconsistent challenge status (no bad consequences)

[botnumberseven]

It's an example of how node handles changing on-chain data.
Unlike #4026, this one does not have any negative consequences, apart from polluted logs and some incorrect data in operationaldb.

Relevant log - log_1.txt

What happened:

1. activeProofPeriodStartBlock=10384800 worked just fine
2. activeProofPeriodStartBlock changes to 10385100. Node creates challenge and submits proof.
3. Then it checks the score for this proof and the result is 0 - getNodeEpochProofPeriodScore(identityId=77, epoch=7, proofPeriodStartBlock=10385100) call has been successfully executed; Result: 0; RPC: https://astrosat.origintrail.network/.
4. Then node tries to resubmit proof multiple times and fails because the proof was actually accepted. All subsequent submit proof fails with This challenge has already been solved
5. Once activeProofPeriodStartBlock switches to the next one everything gets back to normal.

That looks like a chain reorg related issue, although it does not do any harm really.
But it would be nice if node stop trying to solve the challenge, when it gets a clear response This challenge has already been solved

[Mihajlo-Pavlovic]

Hey thanks for reporting, we will investigate