The cryptocurrency community has been discussing the Bitcoinsv network as a mining pool called Taal has well over 51% of the hashrate. Data from the analytical crypto website Coin Dance shows the mining pool Taal commands over 78% of the network’s hashrate during the last 24 hours. On Tuesday, the European cold storage provider, Gravity, says it has suspended bitcoinsv trading “due to several large exchanges disabling BSV deposits [and] withdrawals.”
Following Blockchain Reorganization Attack Last Week, Taal Captures Well Over 51% of the Bitcoinsv Network’s Hashrate
According to statistics, a mining operation called Taal currently commands well over 51% of the Bitcoinsv (BSV) network’s hashrate. On Wednesday, the mining pool Taal captures more than 78% of the BSV hashrate in terms of distribution among five known pools and 13% of unknown hashrate. Data from the web page sv.coin.dance/blocks indicates that during the trailing seven days, Taal commanded 69% of the network’s hashpower. Block details show that a great majority of BSV blocks have been found by Taal’s operation.
Data from the web portal sv.coin.dance/blocks on July 14, 2021.
Besides Taal’s hashpower, other mining pools mining the BSV chain include Viabtc, SBI Crypto, Btc.com, F2pool, and Svpool, at least for today. During the week, other known pools like Solomining, Hathor, and Matter pool have also found BSV blocks. Last week, the Switzerland-based global industry organization, the Bitcoin Association (for BSV), explained that the BSV network was being attacked by a malicious entity.
“A malicious actor has recently been carrying out block re-organisation attacks on the Bitcoin SV network,” the Bitcoinsv group noted on July 8. “[It] appears to be intentional acts in an effort to mask the illegal double-spending of coins. The Bitcoin SV Infrastructure Team have identified one of the addresses connected with the attack as being long associated with ransomware and other attacks on the BTC, BCH, and BSV chains – so the malicious actor is engaged in illegal activity which could involve also BTC and BCH, and not just the BSV network,” the BSV organization added.
Gravity Suspends Bitcoinsv Trading and 51% Attack Explanations
Following the attack, the Twitter account @dash_community tweeted that the Bitcoinsv chain should have had protections like Chainlocks, similar to what’s been implemented on the Dash network. “To prevent damaging block reorganizations like this one, BSV should implement Chainlocks, which Dash pioneered (but which other projects like [Firo] also use), which make reorganizations impossible. Evolve or die,” the account tweeted last week.
The Bitcoinsv (BSV) conversation has been a very topical discussion on Twitter.
After the reorganization issue, reports noted that the exchanges Huobi and Okex halted withdrawals and deposits for BSV. “Huobi Global [has] disabled BSV deposits and withdrawals; no advance warning was given. They are fighting BSV because they know it is the real Bitcoin,” one Bitcoinsv supporter wrote.
Then on July 13, the cold storage provider, Gravity, told its Twitter followers that it was disabling BSV trades.
“Urgent Notice,” Gravity tweeted. “Our liquidity providers have just informed us that, due to several large exchanges disabling BSV deposits [and] withdrawals, they are also suspending access to BSV liquidity until further notice. This means it will not be possible to trade BSV on Gravity at this time. We sincerely apologise for the short notice [and] will update you with more information when we have it. Trading of all other digital assets on Gravity remains unaffected.”
51% attacks are a trap to see if someone is an idiot and doesnt understand what proof of work is for in Bitcoin. If they are a dumb peacock they can enjoy getting attention of the tiger (law enforcement)
— BSV KING (@bitcoinkaiser) July 14, 2021
Meanwhile, the Coingeek streaming channel that focuses on Bitcoinsv (BSV) news coverage and the BSV ecosystem, also discussed the situation. Kurt Wuckert Jr. hosted the show and he responded to the criticisms that were being cast at the BSV chain. Wuckert Jr., also made similar statements the day prior on Twitter.
“51% attacks don’t really exist without the exchange-based bitcoin economy,” Wuckert Jr. tweeted. Huobi [and] Okex stopped withdrawals/deposits, but they will be back. Honest nodes reject malicious blocks, and then further attempts are waste. Things will be back to normal soon,” he added.
Commenting on the 51% attack discussion stemming from the Coingeek streaming channel video, the bitcoiner Theo Goodman wasn’t impressed by the host’s explanation of the events. When someone tweeted: “Watch this, Kurt explains what is happening at the start,” Goodman responded to the video content.
“He does explain it but then adds some opinion,” Goodman wrote. ‘There is no such thing as a 51% attack’ and from 9:14 he contradicts himself regarding trust. Then later he [basically] says not to worry unless you are in infrastructure they will figure it out.”
What do you think about the discussions revolving around the Bitcoinsv network? Let us know what you think about this subject in the comments section below.
Tags in this story
51%, 51% attack, bitcoinsv, Blockchain Reorganization, BSV, Calvin Ayre, Chainlocks, Coingeek streaming channel, dash, Gravity, Hashpower, Hashrate, Huobi, Kurt Wuckert Jr., Liquidity, malicious actor, Okex, reorganizations, Taal, Taal Pool, Theo Goodman
Image Credits: Shutterstock, Pixabay, Wiki Commons, Coin Dance, Twitter,
Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. Bitcoin.com does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.
(function(d, s, id)
var js, fjs = d.getElementsByTagName(s);
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = ‘https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v3.2’;
(document, ‘script’, ‘facebook-jssdk’));