Blog: add "Segregated Witness: Next Steps"#188
Merged
Conversation
|
ACK 8ae9da2 |
Contributor
|
@harding Thanks for stepping up to write the content based on the outline. |
Contributor
|
ACK 8ae9da2 |
|
|
||
| The following plan describes how segwit is expected to be deployed. | ||
|
|
||
| **Merge to master (without mainnet activation code):** after Bitcoin Core developers "ACK" (approve) the final segwit pull request, it will be merged into the Bitcoin Core master Git repository branch. The code that is being merged will include everything in segwit except for the activation code. This will make it easy for developers to test other features on top of segwit, such as compact blocks. |
Member
There was a problem hiding this comment.
Maybe add "on testnet" somewhere here, there is no activation for mainnet, but segwit can already be tested on testnet with 0.13/master from this point on.
Contributor
There was a problem hiding this comment.
probably worth saying segwit is active already on testnet and people can begin testing it immediately.
Member
|
Awesome writeup, hard to not get excited about all the new possibilities. |
Contributor
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
This adds a blog post describing the current state of segwit, how it is expected to be rolled out, and a few things that are possible in future Script upgrades. It is based upon an outline written (I believe) by @btcdrak and contains many suggested improvements to an earlier draft from a number of people. All remaining errors are entirely my fault.
A screenshot of the rendered post can be found here: https://i.imgur.com/NOhsA9i.png
The document is long, so time-pressed Bitcoin experts who only have time to review part of it are encouraged to start with the last two sections, "Schnorr" and "MAST", as those are the topics I knew the least about and which seemed to have the most significant errors found during first review.
I feel the MAST section is the weakest part of the blog post and could probably be rewritten to good effect (plus maybe crudely illustrated for those who don't understand merkle trees). I may attempt that tomorrow if there aren't too many comments on the main body of the text.
Although the post is probably already too long and detailed for many readers, if anyone thinks there are important (or really interesting) topics missing, I'm happy to add them over the weekend.
@btcdrak could you please review the YAML header's category and tags fields; I didn't know what to put there.