RFC(0053): CKB Hardfork #442
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
15 tasks
quake
previously approved these changes
Oct 26, 2024
eval-exec
approved these changes
Oct 26, 2024
zhangsoledad
force-pushed
the
zhangsoledad/Hardfork
branch
from
3a6ae4f to
acd071e
Compare
zhangsoledad
force-pushed
the
zhangsoledad/Hardfork
branch
from
3c16eec to
5a0e339
Compare
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.
CKB has lacked an overview document on hardforks. This RFC aims to fill that gap by introducing a new naming convention for hardforks, while also organizing previous naming schemes and clarifying the relevant timeline policies and processes.
preview