CoinGeek’s Calvin Ayre Explains Craig Wright and Bitcoin Satoshi Version Support with BCH Hard Fork
On the 15th of November, a hard fork of Bitcoin Cash is expected. Unfortunately, it is not expected to be smooth or easy. There are two warring factions looking to stamp their authority on the Bitcoin Cash network features. One is led by Jihan Wu, the founder of Bitmain while the other is nChain’s chief Scientist Craig Wright.
Craig has been claiming to be Satoshi Nakamoto, the mysterious founder of Bitcoin. However, without any tangible evidence such as private keys, he has little to back up this claim. He has been hard at work to ensure that Bitcoin Cash follows his vision and allows for changes that will apparently revert the network back to how Satoshi had originally intended it to be. His support base is composed of many who are disgruntled by the current version that they feel is restrictive due to its block size caps. Furthermore, there are numerous complaints that core developers do crash ideas as they arise.
As an avid supporter of Bitcoin Satoshi Version, the owner of CoinGeek, a large Bitcoin Cash mining pool, Calvin Ayre has made it clear where he stands. His reasons for supporting Bitcoin Satoshi Version (Bitcoin SV) are clear.
A New And Improved Bitcoin Cash Network
Calvin is insistent that his team is only trying to improve the protocol. He claims that millions have already been put into a range of projects such as Terab and Cash Shuffe. All this so that their mining power can be built and deployed for the Bitcoin cash network.
He is a staunch defender of the hash rate and says “The hash rate not only protects the network, but provides CoinGeek with an economic voice to vote for or against proposals. It is in this case that we disagree with the fundamental direction of ABC. We do not agree that there needs to be a rushed transactional ordering change in blocks, and we do not agree on the introduction of other opcodes providing that Bitcoin script can attain the same function.”
He feels hash rates offer the sort of democratization that is needed for stakeholders to be able to air their views about different proposals. His team doesn't support Canonical Transaction ordering in blocks and the activation of operation codes due to the Bitcoin script that executes this.
Ensure The Implementation Of The Original Protocol
In an uncompromising tone, Calvin confirmed that Bitcoin SV is not looking to add anything to the original version of Satoshi’s Bitcoin implementation. The idea is to go back to the future and restore the implementation of the supposed original protocol. He adds:
“We would like to see the original implementation restored in its entirety, first and foremost. I have invested heavily in infrastructure to support BCH from the ground up. The countless hours of effort and millions of dollars spent have been with one goal in mind. To make Bitcoin BCH the leading cryptocurrency in the world, and to have it working as global money for the entire world.”
Bitcoin Cash Is A Developers Preference
A system is only as good as the team that utilizes it. Thus a system is powered by economic incentives and interest from different developers who work on it. Bitcoin Cash has been a global phenomenon with developers interacting with exchanges, wallet providers and even other developers working on different protocols, all this derived from the Bitcoin Cash blockchain.
Thus the network just needs to be robust enough while the technical infrastructure is being put into place for longevity. He proudly states, “We have already had glimpses of BCH’s prowess. Numerous projects are rolling in demonstrating its capability in smart contracts, tokenization, social media, private messaging, and much more. It’s clear that Bitcoin BCH outperforms Ethereum and any other crypto for scalability and workability.”
Disagreements are always healthy as more thought is put into a problem and this usually means more innovative solutions. This case with the impending fork, however, seems to be slightly different. It will be interesting to note if the two development teams can find any common ground before the deadline date of November 15.