Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix: circular deps finalized head #35
fix: circular deps finalized head #35
Changes from all commits
ffcea68
3c177a4
4a40c4d
1b23efa
353ecc6
e60a22e
0215d28
a8905ef
7b09dc3
3110e9a
88b5825
d3c04fb
4e79917
d294ff8
94662b6
93ff4e0
f361f09
e840f8a
62752d5
c32bf01
829f2ee
c21cc6d
b19c286
eeffbec
e4e4059
95b3da8
da09e72
3239860
8ef172b
a164918
0430d35
9a820aa
c53d102
7247af0
ab1ddac
a9f148c
ae8d80f
d29abad
6a4c287
0a26e66
b58f7db
a467d81
3d85e2f
0409cd8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible that block
h
is finalised but blockh+1
is not? I think it's not possiible as BTC staking enforces consecutive finalisation. So wdyt of maintaining the last finalised height in DB and accessing that value, instead of iterating over all these blocks?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no it's not possible (we can enforce it in bbolt.go as well but can go into another pr)
good point. we already maintain fist and last finalized heights. we can use them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if using last finalised height then the logic can be greatly simplified. Can be done in a separate PR though