-
Notifications
You must be signed in to change notification settings - Fork 19
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
omni-executor
init
#3122
omni-executor
init
#3122
Conversation
tee-worker/omni-executor/parentchain/artifacts/rococo-omni-account.scale
Outdated
Show resolved
Hide resolved
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.
Super! LGTM
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.
Thank you, generally the skeleton looks good
tee-worker/omni-executor/executor-core/src/sync_checkpoint_repository.rs
Show resolved
Hide resolved
/// in case of substrate chain it is BLOCK_NUM::EVENT_NUM | ||
pub trait Checkpoint { | ||
// determines whether checkpoint is a whole block or not | ||
fn just_block_num(&self) -> bool; |
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.
I find just_block_num
a bit confusing :D
Does it make sense to have a CheckPointType
type?
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.
I was thinking about it, but since it's trait we only assume there is something like 'block'.
The other improvement could look like this:
- remove
just_block_num
- after restart always start syncing from
get_block_num() - 1
but skip already processed events
Initial code for
omni-executor
offchain worker.Adds: