-
Notifications
You must be signed in to change notification settings - Fork 20
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
Initialize storage on omni executor startup #3228
base: dev
Are you sure you want to change the base?
Initialize storage on omni executor startup #3228
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks
edition.workspace = true | ||
|
||
[dependencies] | ||
executor-core = { path = "../../executor-core" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you consider using workspace dep?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably should. I was just trying to be consistent with what we currently have. I'll update the dependencies 👍🏼
} | ||
|
||
async fn init_account_store_storage(client: &SubxtClient<CustomConfig>) -> Result<(), ()> { | ||
let storage_query = parentchain_api_interface::storage().omni_account().account_store_iter(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no concept of storage proof right? Like we don't have to verify anything that we downloaded
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it is still available in the legacy
modules. The rpc method to get the proofs is there and some types to verify the values. Do you think we need to do this? As long as we connect the worker to a node that we trust its ok
As topic, when starting the omni-executor it downloads the AccountStore from the parentchain and saves the in the storage.
Some modules have been reorganized for reuse.