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 a new baseapp is set from the contents of a fraudproof, when setting key/value pairs in the store of the baseapp, we start with an empty SMT with no predefined root. However, we must start with a deep SMT with a predefined root taken from the given fraudproof. This lets the new app's substore hashes to be the same.
Right now, since we load the key/value pairs on an empty SMT we don't get the same root as the pre-state root of a challenged transaction.
The text was updated successfully, but these errors were encountered:
Manav-Aggarwal
changed the title
Initialize the new app with a deep subtree instead of populating the empty SMT on startup
Initialize the new app with a deep SMT instead of populating the empty SMT on startup
Aug 20, 2022
Manav-Aggarwal
changed the title
Initialize the new app with a deep SMT instead of populating the empty SMT on startup
Initialize the new app with a deep SMT instead of populating the empty SMT
Aug 20, 2022
Currently, when a new baseapp is set from the contents of a fraudproof, when setting key/value pairs in the store of the baseapp, we start with an empty SMT with no predefined root. However, we must start with a deep SMT with a predefined root taken from the given fraudproof. This lets the new app's substore hashes to be the same.
Right now, since we load the key/value pairs on an empty SMT we don't get the same root as the pre-state root of a challenged transaction.
Starting point:
cosmos-sdk/baseapp/baseapp.go
Line 873 in aa56ce4
The text was updated successfully, but these errors were encountered: