-
Notifications
You must be signed in to change notification settings - Fork 95
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
feat(zebra-scan): Connect scanner with zebrad for block processing #7908
Comments
What about verified blocks that are already in Zebra's cached state? We also need to scan them with every key (and re-scan with each new key we get). Can we open tickets to decide on a scanning strategy for cached blocks, and add that implementation in another scanner task? (We want the incoming task to wait on new blocks, so it's tricky to have it handle cached blocks as well.) |
@mpguerra I think that running the scanner in |
Hey team! Please add your planning poker estimate with Zenhub @arya2 @oxarbitrage @teor2345 @upbqdn |
It's not clear that this needs to be in the MVP, unscheduling |
Are we going to run the scanner as a separate binary? That seems more complicated than running it from inside |
As an alternative, we could remove "incoming blocks" from the scope of this ticket? |
We excluded #7905 from the MVP, so we should remove that item from the scope of this ticket. |
This task involves connecting the scanner task with
zebrad
, ensuring that it is initiated from withinzebrad
and that all incoming blocks are correctly routed to the scanner for processing.To complete this task, we need to:
zebrad
start command, ensuring it is triggered and operates in coordination with thezebrad
node.zebrad
are sent to the scanner for further processing.The text was updated successfully, but these errors were encountered: