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
As part of #135 and preceding PR's we disabled state root validation as we were running a node client with a MPT state root implementation against blocks that have a state root associated with a bmpt. This is being done in preparation for the migration from bmpt to mpt for scroll. After the migration to mpt is complete we should re-enable state root validation. This should be done by introducing a threshold for the mpt hardfork block number. We should not validate the state root for any blocks prior to the hardfork but we should validate for blocks after the hardfork. This will allow us to remove the skip-state-root feature gate.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature
As part of #135 and preceding PR's we disabled state root validation as we were running a node client with a MPT state root implementation against blocks that have a state root associated with a bmpt. This is being done in preparation for the migration from bmpt to mpt for scroll. After the migration to mpt is complete we should re-enable state root validation. This should be done by introducing a threshold for the mpt hardfork block number. We should not validate the state root for any blocks prior to the hardfork but we should validate for blocks after the hardfork. This will allow us to remove the
skip-state-root
feature gate.Additional context
No response
The text was updated successfully, but these errors were encountered: