chore!: modify getTreeKeyHash to use hashCommitment

[kevaundray]

Supercedes #24

Once the go-ethereum PR has been merged, we can merge this

[holgerd77]

Updated this PR to take the merged WASM path fix into account (needed a conflict resolution).

[kevaundray]

gballet/go-ethereum#401 (comment) has been merged which unblocks this PR

[acolytec3]

LGTM

[acolytec3]

@kevaundray I'm assuming we need to do an updated release on this one, right?

[kevaundray]

@kevaundray I'm assuming we need to do an updated release on this one, right?

Yep! This is a breaking change for downstream

[acolytec3]

And just to confirm my understanding, this also changes how the stems are computed so we should expect different outputs from getTreeKey, right? Just want to make sure since I need to update the tests for the downstream code in @ethereumjs/verkle

[kevaundray]

And just to confirm my understanding, this also changes how the stems are computed so we should expect different outputs from getTreeKey, right? Just want to make sure since I need to update the tests for the downstream code in @ethereumjs/verkle

Yep, exactly -- this changes getTreeKeyHash which is used by getTreeKey