-
Notifications
You must be signed in to change notification settings - Fork 160
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
RFC36: remove header deps immature rule #240
Merged
doitian
merged 4 commits into
nervosnetwork:master
from
doitian:remove-header-dep-immature-rule
Mar 18, 2022
Merged
RFC36: remove header deps immature rule #240
doitian
merged 4 commits into
nervosnetwork:master
from
doitian:remove-header-dep-immature-rule
Mar 18, 2022
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
bors bot
added a commit
to nervosnetwork/ckb
that referenced
this pull request
Jul 5, 2021
2797: feat(hardfork): reject vm1 lock script before hardfork started to keep compatible with old clients r=doitian,quake a=yangby-cryptape ### Changes - refactor: merge time relative verifiers in ContextualTransactionVerifier Before this commit: - `TimeRelativeTransactionVerifier = MaturityVerifier + SinceVerifier` - `ContextualTransactionVerifier = MaturityVerifier + SinceVerifier + OtherVerifiers` After this commit: - `TimeRelativeTransactionVerifier = MaturityVerifier + SinceVerifier` - `ContextualTransactionVerifier = TimeRelativeTransactionVerifier + OtherVerifiers` - feat(hardfork): reject vm1 lock script before hardfork started to keep compatible with old clients Add `CompatibleVerifier` to `ContextualTransactionVerifier` to check compatible between different versions CKB clients. When a new client with hardfork features released, before the hardfork started, the old CKB clients will still be able to work. So, the new CKB client have to add several necessary checks to avoid fork attacks. After hardfork, the old clients will be no longer available. Then we can delete all code in that verifier until next hardfork. In current version, `CompatibleVerifier` only has one feature: - Reject vm1 lock script before hardfork started to keep compatible with old clients. 2798: feat(hardfork): remove the header deps immature rule r=quake,driftluo a=yangby-cryptape ### Changes - New hardfork Features - [CKB-RFCs PR 240: RFC: Remove header deps immature rule](nervosnetwork/rfcs#240) - refactor: resolve transaction with bitflags Co-authored-by: Boyu Yang <yangby@cryptape.com>
9262097
to
2f8b038
Compare
This was referenced Jul 23, 2021
e66a144
to
f31e93e
Compare
f31e93e
to
48a1d78
Compare
doitian
commented
Aug 13, 2021
rfcs/0036-remove-header-deps-immature-rule/0036-remove-header-deps-immature-rule.md
Outdated
Show resolved
Hide resolved
rfcs/0036-remove-header-deps-immature-rule/0036-remove-header-deps-immature-rule.md
Outdated
Show resolved
Hide resolved
Apply suggestions from nervosnetwork#240 (comment)
Apply suggestions from nervosnetwork#240 (comment)
malinoisls01
approved these changes
Nov 19, 2021
malinoisls01
approved these changes
Nov 26, 2021
malinoisls01
previously approved these changes
Nov 26, 2021
yangby-cryptape
previously approved these changes
Jan 4, 2022
zhangsoledad
reviewed
Mar 1, 2022
rfcs/0036-remove-header-deps-immature-rule/0036-remove-header-deps-immature-rule.md
Outdated
Show resolved
Hide resolved
rfcs/0036-remove-header-deps-immature-rule/0036-remove-header-deps-immature-rule.md
Outdated
Show resolved
Hide resolved
rfcs/0036-remove-header-deps-immature-rule/0036-remove-header-deps-immature-rule.md
Outdated
Show resolved
Hide resolved
zhangsoledad
previously approved these changes
Mar 1, 2022
janx
reviewed
Mar 1, 2022
rfcs/0036-remove-header-deps-immature-rule/0036-remove-header-deps-immature-rule.md
Outdated
Show resolved
Hide resolved
Co-authored-by: zhangsoledad <787953403@qq.com> Co-authored-by: busyforking <5958+janx@users.noreply.github.com>
1348ebd
Assigned reviewers: @janx @zhangsoledad |
zhangsoledad
approved these changes
Mar 4, 2022
janx
approved these changes
Mar 4, 2022
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.
The PR looks good. Don't forget to update repo README - can use a different PR to avoid merge conflicts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
b:consensus
Break consensus
ckb2021
Hard fork scheduled in 2021
hard-fork
s:fcp
Final Comment Period. PR is merged when there's no comments in 14 days.
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.
This document proposes removeing the loading header immature rule.
In the consensus ckb2019, the header dep must reference the block which is 4 epochs ago. After this RFC is activated, the transaction can use any existing blocks in the chain as the header dep.