Look into utilizing appHash to check state not alter after query

[hieuvubk]

Background

Another reference from 3001. Using state exported is the right way to check state alter after querying.
But for more accuracy, we should look into app hash verification in the future.

[hieuvubk]

@p0mvn @ValarDragon @mattverse Hello I got trouble when using app hash. The old hash & new hash is different after querying. Or I'm using the wrong func pls let me know.

[mattverse]

@hieuvubk aren't app hashes expected to be different after commit?

[hieuvubk]

@p0mvn @mattverse @czarcas7ic I checked and see that some module (slashing, distribution, downtimedetector, staking) always change their own commit_store_hash in each height => appHash change.
My suggestion is check commit_store_hash after query instead of app hash (since we also check query against each module).
Pls lmk what u think

[czarcas7ic]

@hieuvubk its expected that each height has a different hash for each module. I think the intent here was to run a test that goes through two blocks twice. On the first run there is no query and on the second run there is a query. With this setup, hashes x and x+1 should match between the two runs.