Bitcoin SV [BSV] gets hit with another reorg as multiple blocks get orphaned...

[dragononcrypto]

Bitcoin SV [BSV] gets hit with another reorg as multiple blocks get orphaned, including a 128 MB block

Bitcoin SV [BSV] and its proponents have been making headlines over the past couple of weeks, either due to developments or because of comments made by its major proponents, Craig Wright, the chief scientist at nChain, and Calvin Ayre.

The network was also hit with several members of the cryptocurrency community alleging that the cryptocurrency itself is a sham without any use cases, as evidenced by its delisting on several popular cryptocurrency exchanges like Binance, Kraken and Shapeshift.

The latest news added salt to BSV’s wounds after it was revealed that the network went through another blockchain reorganization on a 128 MB block. This fact was pointed out by Nikita Zhavoronkov, the lead developer of Blockchair, who had tweeted:

“Whoops! $BSV has experienced yet another reorg, this time 6 (six!) consecutive blocks were orphaned (#578640–578645), this chain included a 128 MB block #578644 🤦‍♂️ The network was basically stuck for 1.5 hours, and this shows that even 6 confirmations are not enough.”

Orphaned blocks are valid blocks which are not part of the main chain. There are ways that they can occur naturally when two miners produce blocks at similar times or they can be a result of an attacker with enough hashing power using it for nefarious activities like reversing transactions.

A major reason why this reorg event made news was that a major 128 MB block was stuck in transaction, something that was not supposed to occur according to the initial claims made by the SV camp. Supporters of the cryptocurrency, however, have stated that despite being slower than promised, the transactions on the block settled faster than that on a Bitcoin Core block.

One supporter of BSV, mboyd1, tweeted:

“Orphaned blocks are a feature, not a bug”

To this tweet, Zyo, another cryptocurrency enthusiast replied:

“yes, but orphaning 6 blocks in a row is not good, that means that 6 confirmations is not safe. It’s a bug because the 100+ MB take way too long to propagate and validate. There is a reason why BCH doesn’t have [yet] 100+ MB blocks.”

https://ambcrypto.com/bitcoin-sv-bsv-gets-hit-with-another-reorg-as-multiple-blocks-get-orphaned-including-a-128-mb-block/

[dragononcrypto]

On 18th April 2019, our Bitcoin Cash SV node experienced 2 block re-organisations. First a 3 block re-organisation, followed by a 6 block re-organisation.

The below graphic illustrates the events. It includes the block heights, block hashes & block sizes of the relevant blocks.

https://twitter.com/BitMEXResearch/status/1119197415804932096

No message really, just the facts. Others can interpret what this means.

For example, perhaps one could infer that:

* The Bitcoin Cash SV network is not reliable for payments
* The block size limit on Bitcoin Cash SV is too large
* Network latency on Bitcoin Cash SV is too high

https://twitter.com/BitMEXResearch/status/1119201352045998080