add tc for working hash

[zsystm]

Description

• Before IAVL v1.1.4, calculating working hash at Init Genesis phase was in-correct. (for detail: debug notes)
  • expected: calculate working hash with initial height of Genesis.
  • real(bug): calculate working hash with zero.
• Added test case for checking calculating working hash at Init Genesis phase is correct.
  • Initially, I attempted to write test code for the following scenario, but encountered some trial and error and realized it would take more time. Therefore, I decided to hardcode the values (check below figure) obtained by running the node with a fixed genesis which has initial height 4 to perform the test.
    1. Create an app with LevelDB.
    2. Proceed through some heights to make the initialHeight of the genesis greater than 0.
    3. Calculate and record the working hash of each module just before exporting.
    4. Export the genesis.
    5. Import the genesis.
    6. Calculate the working hash of each module.
    7. Compare the values with those calculated just before exporting.

The values on the left side of the image are the working hashes of each module obtained when using the buggy version of IAVL, while the ones on the right are the correctly calculated working hashes after the patch.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• included the necessary unit and integration tests
• reviewed "Files changed" and left comments if necessary

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[dudong2]

Suggested change

	if key != nil && matchAny(key.Name()) {
	if matchAny(key.Name()) {

key is not pointer, so i think you no need to nil check

[zsystm]

@dudong2
key can be nil, it is declared as interface. I ran the following code and the result was 0x19.

	counter := 0
	for _, key := range storeKeys {
		if key == nil {
			counter++
		}
		if key != nil && matchAny(key.Name()) {
			kvstore := app.CommitMultiStore().GetCommitKVStore(key)
			require.Equal(t, storetypes.StoreTypeIAVL, kvstore.GetStoreType())
			iavlStore, ok := kvstore.(*iavl.Store)
			require.True(t, ok)
			workingHash := hex.EncodeToString(iavlStore.WorkingHash())
			require.NotEqual(t, workingHashWithZeroInitialHeight[key.Name()], workingHash)
			require.Equal(t, workingHashWithCorrectInitialHeight[key.Name()], workingHash)
		}
	}
	fmt.Println(counter)

[dudong2]

LGTM