Adam Watson 22,781
However, Electron Cash developer Jonald Fyookball wrote a case for adding CTOR to the BCH protocol this week. Of course, early on Bitcoin ABC has published some opinions as to why the development team believes CTOR should be added to the BCH codebase. Another post on r/btc, written by Mark Blundeberg, gives a comprehensive technical dive into canonical transaction ordering, and the BCH mining pool Rawpool has also given an objective evaluation towards CTOR. The Bitcoin Miner Jonathan Toomim also added some information to the mix with his block propagation data that stemmed from BCH stress tests that took place few of weeks ago.
“During the stress test, blocks propagated through the non-China mainnet at around 300–1000 kB/s – This is pretty slow, and would cause problems with orphan rates if block sizes were frequently larger than 8 MB unless we improve our block propagation algorithms,” Toomim explains in his recent post.
Jonathan Toomim’s propagation delay vs. block size chart.
The Pros and Cons Concerning the OP_Code
Then there are many discussions concerning the OP_CHECKDATASIGVERIFY (DSV) feature Bitcoin ABC wants to add.
Craig Wright said that “DSV opens many issues” and others have disagreed with the idea of adding DSV as well. One Github repository details another option the community could use instead of DSV called recursive smelting. Then Nchain’s senior researcher Owen Vaughan recently published a paper called “Rabin Signatures in BCH.” The paper posits the belief that “arbitrary messages can be signed and verified directly in BCH script without introducing new opcodes.”
Mark Blundeberg has written another extensive post that shows the benefits of DSV called “Pay To Identity” – a proposed use of “OP_CHECKDATASIG”. Moreover, another post published on Yours.org by a writer named Perica argues that DSV is already in the codebase, and has been there since the creation of the Bitcoin version 0.1 release.
Perica’s paper claims the current DSV model, that’s already baked into the original code, is a “more powerful form than the one proposed by various developer teams.” Perica’s paper claims there already is a DSV model that’s baked into the original code that’s “in a more powerful form than the one proposed by various developer teams.” BCH Supporters Discuss Over the Next Few Weeks Before the Fork
There’s been so much to discuss its hard to trust the fork may happen this November but right now both camps seem pretty adamant an upgrade will take place. Further people can stay rather neutral and run either Bitcoin XT or the Bitcoin Unlimited clients, as those teams plan to allow the decision to be ultimately made by majority hashrate.
The stress test, although remarkable, offered insight for some of the problems introduced by exceeding blocks larger than 8MB. There’s also a lot of bickering between community members over the 128MB increase and whether or not the chain should upgrade the block size now. Nevertheless, a slew of big block advocates believe the network can handle super large blocks and some think the limit should be removed entirely. .
