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
Claim/proof improvements #36
base: main
Are you sure you want to change the base?
Claim/proof improvements #36
Changes from all commits
b463731
7d36132
e39eba1
7268c56
2672335
86193db
4887770
7b8706e
e2497e4
0f3fe41
5a29d15
75f8ece
e783046
c99cc89
71687c9
11ffee7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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.
True, we can probably remove it.
The ONLY thing I haven't thought through is how to handle changes in the number of blocks per session while a session is active.
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.
Had some thoughts about this. We could have a map of previous session numbers with their heights each time gov. changes this parameter (à la protocol upgrade).
Then if we want to check the height of a session we should calculate it using this map, eg.
If after session height 15, we have 5 blocks per session and we are at block 20 we do 40 + ((20 - 15) * 5) = 85 which is the block height for session 20. (don't mind off-by-one errors in the example if there are)
It also let us calculate the block height of any past session.
We may have a slightly more complex structure if we want different
blocks_per_session
per service.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.
Let's leave this for a post-alpha discussion and just assume a constant (governance-driven) parameter for now. What you're describing will work but I want to see if we can make it simpler.