Request for comments: An evidence-based process for Bitcoin Cash

9 872
Avatar for mtrycz
Written by
4 years ago (Last updated: 3 years ago)

中文

This document is a DRAFT or Request for Comments. Check out also a more detailed writeup, and the accompanying decentralized cooperation proposal and writeup.

Scope

The scope of this process is explicitly consensus changes for Bitcoin Cash.

Non-consensus protocol changes are possible candidates, but not necessarily.

Explicitly not in scope is non-technical discussion.

Process

A person or group willing to spearhead a consensus change will nominate themselves as the leaders of that initiative. They will assure open communication of the following points.

These are not to be interpreted as a step-by-step process, rather as a checklist - for a proposal to be valid, all of them these need to be completed, not necessarily in-order and possibly with iterations.

  • (Objective) Define what the change it aims to achieve or what problem it needs to solve

  • (Solution) Provide a solution that's a clear improvement for the objective

  • (Specification) Provide a clear spec, which might initially be a draft

  • (Implementation) Provide a reference implementation for testing

  • (Burden of proof) Provide a clear case in favor of the change and reproducible evidence (possibly a test suite)

  • (Feedback) Gather feedback to improve all of the above

  • (Evaluate) Allow reasonable time for people to evaluate and propose alternative solutions

23
$ 14.21
$ 5.00 from @JonathanSilverblood
$ 5.00 from @BitcoinOutLoud
$ 1.22 from @molecular
+ 5
Avatar for mtrycz
Written by
4 years ago (Last updated: 3 years ago)

Comments

I support this process.

$ 0.00
User's avatar btcfork
This user is who they claim to be.
We have manually verified this user via some other channel.
3 years ago

I recommend you use bitcoincashresearch.org for this specific purpose.

My feedback:

  1. There must be a social contract firewall between this process and the protocol itself. Wiring it up in a mechanical way to the protocol will create a much lower barrier to gaming the whole process. It also reduces the need for social contract commitment to actual collaboration as opposed to leaning on / gaming whatever mechanism was created.

  2. Just like the original BIP process, I think it misses an explicit call for RFC and explicit consideration of costs (as well as benefits). Burden of proof is a much larger issue than just testing and technical feasibility.

$ 0.00
4 years ago

nice article!

$ 0.00
4 years ago

Thank you

$ 0.00
4 years ago

nice article!

$ 0.00
4 years ago

thanks bro for sharing this article.

$ 0.00
4 years ago

I will like you to write more on this.

$ 0.00
4 years ago

nice article. keep it up

$ 0.00
4 years ago

same as the BIP process, it is missing the last and critical part - https://read.cash/@tula_s/briefly-on-governance-ff06770f

$ 0.00
4 years ago