@miladz68 reviewed 2 files and all commit messages, and made 1 comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on masihyeganeh, metalarm10, TxCorpi0x, and ysv).

a discussion (no related file):
I don't understand why a rollback would fix the issue. I think we should discuss what caused the problem.

@TxCorpi0x made 1 comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on masihyeganeh, metalarm10, miladz68, and ysv).

a discussion (no related file):

The error comes up when any of the node fails or has corrupted db, this error is the same error that we faced in the devnet, and two nodes failed because of lack of enough resource. In a normal chain, we need to use the rollback command of the cosmos-sdk appchain's binary to roleback one block and restart the node so it can catchup again with the recent network data.

So the same behaviour happened here, we rollback one block to make sure there is no failed storage read.

panic: version 1810 was already saved to different hash from 3D8D3DB7F429156B6BCD81232657AF5C1691B3234E9273A91C63BDD56DF3D7B0 (existing nodeKey [0 0 0 0 0 0 7 18 0 0 0 1]) [recovered]
	panic: version 1810 was already saved to different hash from 3D8D3DB7F429156B6BCD81232657AF5C1691B3234E9273A91C63BDD56DF3D7B0 (existing nodeKey [0 0 0 0 0 0 7 18 0 0 0 1])

@miladz68 made 1 comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on masihyeganeh, metalarm10, TxCorpi0x, and ysv).

a discussion (no related file):

Are we sure that the problem is caused by corrupted db ?

@TxCorpi0x made 1 comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on masihyeganeh, metalarm10, miladz68, and ysv).

a discussion (no related file):

This issue is random, in tests, this PR is to make sure this failure don't come up in the rest of the development and PRs.
But about the actual issue, I think we need to define an specific task to dig more into this issue, since I observed this issue after adding the PSE module, i am not sure which part of the code would cause this issue, but at least we should gain more info why this kind of error is apearing recently more often than before, these issues can be related:

1. PSE logic and end blocker
2. More repos (tx-xrpl-bridge and etc.) use the self-host runner recently, may be this happens when too many runs of different PRs are running.
3. The recent upgrades of sdk and dependencies might be the reason as well.

@miladz68 resolved 1 discussion.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on masihyeganeh, metalarm10, and ysv).