-
Notifications
You must be signed in to change notification settings - Fork 386
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
[0.17] Block v4 mandatory #470
[0.17] Block v4 mandatory #470
Conversation
48e6dcb
to
3a8dc50
Compare
Made the relevant changes and rebased over #452, having some trouble making tests work. Seems like making |
3a8dc50
to
5830808
Compare
note that this new method of activating new blocks is an attempt to use the starting block of various rules at block 0. This will need reasonable review but seems to be the simplest way to set mandatory block versions. |
For |
I believe this will get you to passing tests, but we'll need a test of our own setting them to zero:
|
5830808
to
dc1d832
Compare
- Reinstate Bitcoin BIP activation heights for tests - Add tests for block v4 after genesis block
dc1d832
to
e04f6c7
Compare
@instagibbs Added tests, lmk if you want something more extensive. |
unmarked WIP |
oh baby that test 🥇 I gotta learn that mininode stuff too. Not even a nit per se but why the CLTV test? To make sure that blocks are being made of v4? |
ACK e04f6c7 |
Yup exactly! 😄 |
I added a description to the OP |
Thank you sir! |
e04f6c7 Activate BIPs 34, 65, 66 at block 0 (Carl Dong)
By setting the BIPXX consensus fields to
0
we allow them to be enforced from genesis block by default.This means blocks will be required to be at least version 4 by default.
Also adds tests.
Todo for later:
BIP34_IMPLIES_BIP30_LIMIT
right now means all chains will slow down validation at height1983702
. We should prod upstream to do something smarter, or allow this to be set as an argument.