locked & compressed data chains #177
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
r? @frabrunelle |
Contributor
|
Number 41 is used by the Low Level API RFC. So this RFC would need a new number (e.g. 44). |
Member
Author
|
Ah no worries @frabrunelle I am happy if you wish to move this to 0043 (I have another one for 42 I need to commit this weekend) |
Contributor
|
42 and 43 are also used 😛 So you could use 44 and 45. |
Member
Author
|
Ah I will do thanks @frabrunelle |
|
Swap the "Motivation" and "Summary" titles, maybe? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
A proposal to enable chains to lock in place and remove block proofs on churn event agreement. Will require some testing and perhaps team discussion on accumulating agreement on blocks, but this is not a huge issue, more one of implementation options.
This change is