read.cash is a platform where you can earn money for your articles and comments. You can get paid upvotes
from other users or just earn points for writing articles and comments, which are converted daily to
Bitcoin Cash (BCH) cryptocurrency, which can be used on the Internet or converted to your local money.
Today, the lead maintainer of Bitcoin Cash Node took a technical step to address an important issue relating to the project's need for an accurate specification of its consensus rules for the 15 May 2020 network upgrade.
Since its creation in 2017, Bitcoin Cash has gone through regular network upgrades. These upgrades should be fully specified well in advance, to allow everyone to agree on, then implement and test the necessary changes.
For this reason, there is a "feature freeze" three months before a network upgrade. By that date, all consensus rule changes for the upgrade are supposed to be completely specified, reviewed and accepted.
The feature freeze for the May upgrade was on 15 February.
More than two weeks past that freeze date, there has been an inclusion of the so-called "Infrastructure Funding Proposal" (IFP) - a highly controversial consensus rule change which impacts the economic incentives of Bitcoin Cash. Not only was this feature strongly opposed by many in the community, it is not accepted by any other clients than Bitcoin ABC, who appear to be treating the specification as their sole property.
While strong opposition to the IFP has been expressed by the community, all protests about this unwanted feature have been ignored by the maintainers of the bitcoincash.org website which is incidentally hosted in the same repository that includes the upgrade specifications.
BCHN is committed to reducing the risk of a chain split by providing node software which does not include the IFP. Given this unacceptable treatment of the common BCH specification, Bitcoin Cash Node is forced to maintain its own version of the upgrade specifications to accurately reflect the consensus rules of its software (absence of IFP equals no change to current BCH protocol).
At the time of writing, the only specification differences to bitcoincash.org were:
removal of inaccurate element: Infrastructure Funding Plan (IFP)
increase of May 2020 specification version number to 1.0 (no longer DRAFT)
Please consult the README.md file in the above repository for up-to-date status.
No other changes to specification are planned by BCHN for May 2020.
The specification in this repository is not considered "prescriptive" for anyone besides the BCHN project.
It is considered descriptive and matches the upgrades planned by BCHN, and authoritative only for our project until such time as a good place can be agreed by the majority of BCH client projects for a common home to such "delta" upgrade specifications.
The upgrade specifications are to be considered in the context of the overall Bitcoin Cash specification that is being developed (see e.g. https://reference.cash).