-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
wip: refactor payload processing #14589
base: main
Are you sure you want to change the base?
Conversation
/// | ||
/// # Transaction prewarming task | ||
/// | ||
/// Responsible for feeding state updates to the state root task. |
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.
also warming revm caches, right?
/// | ||
/// ## State root task | ||
/// | ||
/// Responsible for preparing sparse trie messages for the sparse trie task. |
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 see, so state root task will only spawn multiproofs and send results back to PayloadProcessor
, but PayloadProcessor
itself will send the state update + multiproof to sparse trie task?
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.
send results back to PayloadProcessor
send back to itself. PayloadProcessor is just some helper that spawns these 3 tasks
/// - externally cancelled (e.g. sequential block execution is complete) | ||
/// - all transaction have been processed | ||
/// | ||
/// ## State root task |
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.
let's rename this to multiproof task?
No description provided.