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
Proposal for a system of improvements to Bitcoin Cash #69
Comments
Concept ACK The BCIPS should not be located on any of the implementation repo, it should be a independent process for protocol development. Also, there are value able information and development made in the BIPS that were removed. I'd leave it there as informational only. |
@mpatc : Thanks for raising this topic. I agree with you about the importance of having a place where implementations can gather around new specifications (BCIPs is a decent name). And I agree very much with @checksum0 that this should be independent from any particular implementation. I will bump this topic to the bitcoin-ml mailing list since that's where the most "formal" discussion around future Bitcoin Cash protocol matters is happening now. Thread link: https://lists.linuxfoundation.org/pipermail/bitcoin-ml/2017-August/000115.html |
Agree with @checksum0 Closing this issue in favor of other groups currently attempting to organize this process. |
This touches some sources files, so the test plan covers more than just review. Note: src/rpc/register.h contains a comment associated with an interface that still has 'ABC' baked into its name. This has been left as-is pending a decision whether to rename this interface going forward, or leave the name. Author's opinion: Extending it while keeping it named after ABC would not be optimal. Test plan: - review the document / pure comment changes - do a full build and test with `ninja check` and `ninja check-extended`, all tests expected to pass. Closes Bitcoin-ABC#37, Related to Bitcoin-ABC#69
I see there isn't a formalized method in place to improve Bitcoin Cash.
I have forked the original bips repo and refactored it as followed:
each relevant, active or final bip becomes a BCIP
removed bips that have been withdrawn, or are no longer relevant to this project. Obviously, they can be resubmitted if need be.
changed file names and links from bip to bcip, for Bitcoin Cash Improvement Proposal
changed the mailing list for BCIP submission from bitcoin-dev to bitcoin-ml
small edits of the original bip texts to reflect current 8MB maxblocksize where needed
changed editor from Luke to myself
some links won't work because they are referencing a nonexistent https://github.com/Bitcoin-ABC/bcips repo that I am proposing here.
The bips I removed for various reasons are: 2 10 12 15 17 18 19 20 33 36 40 41 42 43 62 68 74 75 101 102 103 109 125 141 142 144 145
I won't go into my reasoning for each here, it should be self evident, and of course they can be readded if I removed in error.
I'm volunteering to be the BCIPs editor for now if that works for people, but no new bcips would be added before discussion and agreement, as in the bip process.
This is just a first pass, I'm sure there is stuff that's wrong, or is missing, or should be missing I will examine/fix later but in the meantime:
Please feel free to review, comment or make PR here: https://github.com/mpatc/bcips
The text was updated successfully, but these errors were encountered: