Brindrajsinh Chauhan

Github does not seem to let me assign it to myself, would be grateful if @non-fungible-nelson you could take that action. Will start investigating on this piece.

Hey sorry, have not been able to recreate this based on the scenarios you provided.

yes send a bunch of transactions to a smart contract with a few nodes down and then bringing them back up

Facing the same issue. An solutions?

Could you point with steps, settings you used to recreate this. That would be helpful. Thank you

@karalabe Thank you for the feedback. The pathDB part you mentioned would be referring to this right https://github.com/ethereum/go-ethereum/tree/master/triedb/pathdb. and the Issue mentioned here https://github.com/ethereum/go-ethereum/issues/28617. I can take a look at...

@karalabe @holiman Updated the implementation. Would be grateful if you could provide feedback on the same PathDB already had a parameter `force` [here](https://github.com/ethereum/go-ethereum/blob/master/triedb/pathdb/difflayer.go#L128) which has a similar purpose of bypassing...

@karalabe @holiman @rjl493456442 Would be very grateful to get your feedback on the updated logic to and resolve this issue. Really appreciate your support thus far. Thank you

Seeing similar issue, the node is not moving ahead with the synchronization process See these logs for a almost 24 hours. Finalized is moving up but not sure if it...