chore: bury rfc0044 deploy #4430
Merged
Conversation
This file contains 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
eval-exec
previously approved these changes
Apr 22, 2024
doitian
previously approved these changes
Apr 22, 2024
Closed
zhangsoledad
force-pushed
the
zhangsoledad/bury-rfc43
branch
2 times, most recently
from
34ca11a to
34a6433
Compare
eval-exec
previously approved these changes
Apr 23, 2024
zhangsoledad
force-pushed
the
zhangsoledad/bury-rfc43
branch
from
34a6433 to
746c4ba
Compare
|
off-by-one adaptation fixe #4255 |
eval-exec
approved these changes
Apr 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is changed and how it works?
This hardcodes RFC0044 activation epochs. makes it easier to understand light client protocol activation status, and reduces technical debt
Check List
Tests
Side effects
Release note