You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when exporting mainnet state, we do not export any kind of order metadata. When calculating the app hash by hashing the module hashes, this order matters.
Suggested Design
Export order metadata so we are constructing the Merkle tree in the same way we are on mainnet
Acceptance Criteria
TBD
The text was updated successfully, but these errors were encountered:
Is this about the order of modules when exporting? Currently OrderExportGenesis not be set, so when exporting state returns the modules in appModules order.
I don't know if the current way is correct for the Merkle tree we are using. So pls lmk what u think
We can't state export such that we can reconstruct the same tree unfortunately, based on how "state export" is defined in cosmos-land. This is because state depends on the tree structure of IAVL, which itself depends on insertion order.
So state sync snapshots do this, and we can maybe create some way to apply modifications onto a state sync snapshot, which is a true "state export", unlike what we typically do.
Background
Currently, when exporting mainnet state, we do not export any kind of order metadata. When calculating the app hash by hashing the module hashes, this order matters.
Suggested Design
Acceptance Criteria
TBD
The text was updated successfully, but these errors were encountered: