-
Notifications
You must be signed in to change notification settings - Fork 671
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
/v2/info only updates on burn block #4351
Comments
Yup, that's the current design. |
You can fix it by checking the canonical stacks tip instead of the burnchain tip when determining whether or not the state for /v2/info needs to be reloaded. Unfortunately I'm too behind on the network state machines to do this right this second, but if you don't feel comfortable doing it, I can fold it into one of the PRs. |
Yup, I can take this one when I have some time. |
PR sent |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
In running the managed testnets, we realized that the /v2/info endpoint does not stay up-to-date with the current Stacks tip height. Instead it is only updating when a new burn block is processed.
The text was updated successfully, but these errors were encountered: