-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] run-block should support storage import #225
Comments
It's supposed to "replay" a block. Why do you need to override storage? |
I agree it is not very intuitive, but for the same as to why you want to override a wasm runtime, it is sometime important to see what would have happened to a block if your runtime or storage was different. In my specific case, I want to verify if a given smart contract (stored in the chain storage) could have worked properly if a given instruction was changed in its code. |
I see, yeah it's easy to implement it |
Btw we also have dry-run command which support |
Yes, that is convenient for single extrinsic, but sometime it is a combination of multiple factors included in a full block. |
Awesome, thank you :) |
Currently it seems that using the import storage is not compatible with
run-block
.I briefly looked at it and it seems to be because the import storage is actually applying the change on top of a block which might be incompatible with
run-block
.Not sure if you have an idea on how to support it before I dig into it
The text was updated successfully, but these errors were encountered: