Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-graphql domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/stas-backend/public_html/bitcoinsv_io/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/stas-backend/public_html/bitcoinsv_io/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/stas-backend/public_html/bitcoinsv_io/wp-includes/functions.php on line 6114
The BSV blockchain & False Reports of a “Three-way Fork”

My Blog

The BSV blockchain & False Reports of a “Three-way Fork”

In recent days there have been a couple of articles which incorrectly suggest that the BSV Blockchain has suffered from a “three-way fork”

In recent days there have been a couple of articles which incorrectly suggest that the BSV Blockchain has suffered from a “three-way fork” over the last few weeks. These articles seem to stem from the same source, a tweet from BitMEX Research. Here are the facts. 

The BSV Blockchain had a planned hard-fork upgrade on 24th July. This upgrade increased the maximum block size from 128MB to 2GB. Unfortunately, despite publicity and announcements over a two month period, a minority of node operators did not update their software. These nodes, that had not updated their software, forked onto a new and incorrect chain after the upgrade. This is a natural consequence of how Bitcoin works: if the software is not aligned with the majority, it will create a “fork” in the blockchain. 

Shortly after the hard-fork, several 256MB blocks were produced on the BSV Blockchain. The size of these blocks caused some minor issues for some service providers. These issues were resolved quickly by the service providers. 

Ten days later, on 3rd August, a member of the Chinese BSV blockchain community initiated their own stress test on the BSV Blockchain. Over 2 million payment transactions were blasted onto the BSV blockchain network over a short period which resulted in two large blocks: a 210MB block containing 808,633 transactions, and a 183MB block containing 702,999 transactions. Unfortunately, some of the nodes on the BSV blockchain network were running on small systems that were unable to cope with this flood of transactions. These systems failed. They did not create a third fork, they simply stopped working. 

These are the facts. There was no “three-way fork”. There was a single fork in the blockchain on July 24th due to out-of-date software, a normal occurrence that affects all blockchains that use Nakamoto consensus. Ten days later, there was a group of nodes that failed because they were using sub-standard equipment and could not keep up with volume of transactions that BSV blockchain is designed to accommodate.  

The BSV blockchain functioned as normal, and continues to function as normal, reliably processing huge numbers of transactions. BSV blockchain is evolving and professionalizing Bitcoin, moving Bitcoin from a prototype supported by hobbyists to a professionally supported system capable of meeting global demand for an immutable blockchain. Inevitably, this does mean that the requirements for systems which participate in the network will increase. The BSV Node implementation team has recently published recommended system requirements and we strongly urge node operators to follow these recommendations. 

Daniel Connolly

admin