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.

Sign up for GitHub

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

Jump to bottom

Improve resilience for when chain state becomes outdated #630

Open
smcclellan opened this issue Jul 29, 2024 · 0 comments
Open

Improve resilience for when chain state becomes outdated #630

smcclellan opened this issue Jul 29, 2024 · 0 comments
Assignees
@rafaelcr
Labels
enhancement New feature or request

Comments

@smcclellan
Copy link
Contributor

smcclellan commented Jul 29, 2024 •
edited
Loading

From this issue, we could encounter situations where the chain state becomes outdated. The system should recognize when this has happened and overcome it.

2 ideas:

  • Allow pulling missing blocks from Stacks API’s event_observer_requests table
  • Fix chainhook code when chainhook is ahead of stacks-node & creates extra forks
@smcclellan smcclellan added the enhancement New feature or request label Jul 29, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Jul 29, 2024
@smcclellan smcclellan moved this from 🆕 New to 📋 Backlog in DevTools Jul 29, 2024
@rafaelcr rafaelcr self-assigned this Oct 2, 2024
@rafaelcr rafaelcr mentioned this issue Oct 3, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafaelcr rafaelcr

Labels
enhancement New feature or request
Projects
DevTools
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rafaelcr @smcclellan