Bitcoin Mining Difficulty Parameter Set to Increase for the First Time in 8 Weeks
Bitcoin’s hashrate has slowly crept back up between 85 exahash per second (EH/s) to 125 EH/s on July 14. The increase in hashpower has made it so the next mining difficulty change will increase for the first time in eight weeks. The four consecutive difficulty drops turned out to be the largest slide in Bitcoin’s lifetime, and that’s seemingly coming to an end in four days. Bitcoin’s Hashrate Moves Northbound
The price of bitcoin (BTC) dropped for a few consecutive weeks, and during the same time frame, China’s crackdown on bitcoin miners was also happening. On May 15, bitcoin’s price began sliding from just above the $50K handle to end up just above the $30K zone on May 19.
A price drop essentially removes revenue from bitcoin miners and when BTC started sliding on May 15, the mining difficulty had jumped two days earlier, up 21.53% higher than the adjustment before. Because it was over 21% more difficult for miners to find a block, the next two weeks were grueling. Bitcoin hashrate (90-day chart) on July 27, 2021.
On top of this, what followed was the Chinese government — in various provinces — cracking down on bitcoin miners and banning the act within specific areas. Miners taken by surprise were told they needed to shut down facilities by a certain date.
Prior to June 9, and two small dips to 137 EH/s, the hashrate managed to remain above 150 EH/s with the difficulty 21% higher. However, China’s actions had impacted Chinese bitcoin miners a great deal and on June 28, the hashrate was only 66 EH/s.
Luckily, bitcoin miners got the first downward difficulty adjustment on May 29 when it slid 15.97%. As the price of BTC got worse, making it harder for miners to profit, the entities that help secure the blockchain benefitted from three more downward difficulty drops. Difficulty Expected to Increase 3-5%
All four consecutive mining difficulty drops made it 54% easier to find BTC blocks over the last two weeks, in comparison to the difficulty height prior to May 13. The consecutive downward adjustments will likely change in four days with a possible increase of around 3-5%. Bitcoin difficulty on July 27, 2021, shows a possible increase of around 4.4% in four days.
If the estimate comes to fruition it will still be close to 50% easier to find BTC blocks than it was before mid-May 2021. However, it will depend on what happens within the next four days as far as hashrate is concerned.
If the hashrate increases a great deal from now until then, the difficulty could climb higher than 5%. If the global hashpower was to decrease dramatically, the estimated increase could get nullified and revert back to another decrease. At the current hashrate, a 3-5% increase is expected which shouldn’t be too grueling for miners to manage.
At the time of writing, the top bitcoin mining pool is Antpool with 19.26% of the hashrate and 19 EH/s. Antpool is followed by Binance pool (12.47%), F2pool (11.82%), Poolin (11.38%), and Viabtc (10.50%).
What do you think about the expected difficulty adjustment increase in four days? Let us know what you think about this subject in the comments section below. Bitmain to Host Miners in 180-Megawatt Data Center in Kazakhstan MINING | 3 days ago New York Town Bemoans Roadside ‘Littered’ With Bitcoin Miners — Officials Plan to Impose 90-Day Moratorium MINING | 4 days ago Tags in this story 16% drop, 2011, 2020, 27% drop, 4 times, 8 times, Block time, BTC difficulty, BTC.com, chinese miners, difficulty, Exahash, Hahspower, Hashpower, Hashrate, largest drop, Largest Drop in History, Mempool, Mining Operations, Mining Pools, network difficulty, Overall Hashrate, SHA256 Hashrate
Image Credits: Shutterstock, Pixabay, Wiki Commons, coinwarz.com, Btc.com, 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. Read disclaimerShow comments