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

Determine cycle-number more robustly #13

Open
zone117x opened this issue Oct 28, 2024 · 0 comments · May be fixed by #15
Open

Determine cycle-number more robustly #13

zone117x opened this issue Oct 28, 2024 · 0 comments · May be fixed by #15
Assignees
@janniks

Comments

@zone117x
Copy link
Member

Current SQL queries determine cycle number using the the BlockProposals table.

These messages are somewhat lossy. Now that we have pox constants from #7 we can always calculate cycle numbers given a block burn height, and calculate block burn height ranges for a given cycle number.
@janniks janniks self-assigned this Oct 28, 2024
@janniks janniks linked a pull request Oct 28, 2024 that will close this issue
fix: update getRecentBlocks to use pox info from chain_tip #15
Open
@github-project-automation github-project-automation bot moved this to 🆕 New in API Board Nov 1, 2024
@smcclellan smcclellan moved this from 🆕 New to 👀 In Review in API Board Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@janniks janniks

Labels
None yet
Projects
API Board
Status: 👀 In Review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: update getRecentBlocks to use pox info from chain_tip hirosystems/signer-metrics-api
2 participants
@zone117x @janniks