-
Notifications
You must be signed in to change notification settings - Fork 37.8k
Release notes: add info about segwit and null dummy soft forks #8943
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
Conversation
harding
commented
Oct 17, 2016
- Segwit text primarily from https://bitcoincore.org/en/2016/06/24/segwit-next-steps/
- null dummy text partially from BIP147
benefits to Bitcoin users. | ||
|
||
Activation for the segwit soft fork is being managed using BIP9 versionbits. | ||
The earliest activation date is set to 15 November 2016 (UTC) and |
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.
That's not technically correct, as it requires a signalling period and a fallow period (both 2016 blocks) after the start time (unless you assume 4032 blocks can be mined within 24 hours).
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.
Oh, indeed. What was I thinking. I'll edit.
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.
Nov 15th is the earliest date that signalling can start. Earliest activation is likely to be ~28 days/4032 blocks from the next retarget after 15th Nov (estimated to be 20th Nov). I would hazard to be so specific.
its versionbit is bit 1. | ||
Activation for the segwit soft fork is being managed using BIP9 | ||
versionbits. Segwit's version bit is bit 1, and nodes will begin | ||
tracking which blocks signal support for segwit on 15 November 2016 |
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.
Still not technically correct. Tracking will start from the first retarget after the 15th.
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.
Ok. I'll edit again. Sorry.
(Please feel free to squash at merge time, or let me know and I'll squash everything on this branch.) |
Thanks for writing this! ACK |
ACK |