Skip to content
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

Node: Rely on canonical affirmation map to know when to wait for anchor blocks #2724

Open
jcnelson opened this issue Jun 18, 2021 · 1 comment
Assignees
Labels
icebox Issues that are not being worked on

Comments

@jcnelson
Copy link
Member

This supersedes #2095.

  • We should update the Burnchain::sync() method to first compute the canonical affirmation map. This would mean downloading all burnchain block ops before downloading Stacks blocks, or possibly receiving it on the command-line as a hint.

  • We should remove the PoxSyncWatchdog, and have the main run-loop rely solely on the chains coordinator to block chain synchronization if we're waiting for a known-extant anchor block.

  • We may need to tweak the downloader so the run-loop can hint to the downloader that an absent but known-extant anchor block is blocking chain synchronization.

@jcnelson
Copy link
Member Author

Removing from the Stacks 2.1 project for now, since it can be implemented afterwards.

@jcnelson jcnelson added the icebox Issues that are not being worked on label Mar 7, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Stacks Core Eng Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
icebox Issues that are not being worked on
Projects
Status: Status: 🆕 New
Development

No branches or pull requests

2 participants