Bitcoin Core

Bitcoin.org Maintainer Calls for the Removal of Cobra, Website Owner Then Fires Him

29/06/2020 by Idelto Editor

The infamous and controversial owner of the website bitcoin.org, Cobra, is under fire recently and a number of community members have asked to see the website removed from his possession. The initial argument was sparked by the website’s maintainer, Will Binns, who told the public that bitcoin.org was in “danger of being compromised.” Since then, Cobra has decided to fire Binns and the crypto community has been very focused on watching this quarrel unfold.

During the last few years, news.Bitcoin.com has reported on the curious case of Cobra, the peculiar anon with a lot of power. Just recently, bitcoiners have been arguing about Cobra’s ownership of bitcoin.org. Cobra has always been controversial and he’s asked the community to change the Proof-of-Work (PoW) consensus algorithm.

Cobra also asked the community and fellow bitcoin.org maintainers to change certain statements Satoshi Nakamoto made in the Bitcoin white paper. Five days ago, bitcoin.org maintainer Will Binns told the community via Github, that he believes Cobra is participating in compromising the website where the “latest version of Bitcoin Core software” stems from.

“Bitcoin.org, where many people also download the latest version of Bitcoin Core software, is now in danger of becoming compromised, if it hasn’t just happened,” Binns said.

“Cobra-Bitcoin has removed my access and seized control of the site and accompanying code repositories. I do not believe Cobra is the sole and lawful owner, nor does he have any right to do these things without just cause. Cobra has referenced recent messages I sent in regular conversation regarding my work and the management of bitcoin.org as reasons for my departure. This has been taken out of context in an attempt to manipulate public opinion and infringe upon my rights, along with the rights of others,” Binns added. The bitcoin.org software maintainer further stated:

I believe he is looking to illegally transfer ownership of the site without due process, and this may only be the beginning. I’m writing this message to request assistance setting up a legal fund and the help of experts, to help stop this. In the interim, the website’s treasury will be placed under the control of a trusted third party. The funds are safe, the site is not.

Cobra explained that he had “removed Will Binns as the site’s maintainer,” in another Github post called “Regarding Will Binns #3397.” “During a conversation on Twitter, he had claimed that his work contributing to bitcoin.org conferred on him more authority than what I had agreed with him. I won’t engage with him beyond attempting to retrieve the community’s donations from wallets he has control over,” Cobra told the community members on Github.

The website’s owner continued by stating:

This may seem harsh, but any further communication with him risks putting this project in an unfortunate situation. So I had to be brisk and terminate his relationship with us. I’ll be taking over the day-to-day activities on the site more actively from now on; if any contributors or translators are in any group chats with him, please make alternative groups so you can continue work on the site.

Interestingly the former Blockstream employee and Bitcoin Core developer, Gregory Maxwell, seemed to agree with Cobra’s stance. “Your position appears to be a misplaced and inappropriate response to Cobra suggesting that he was considering not handing you unilateral control of Bitcoin.org. I hope you reconsider your approach,” Maxwell explained in the post reply toward Binns.

Another software developer wrote: “From my experience, even though I’ve not always agreed with [Cobra] on certain things, I think he’s shown good character, and as others have stated, he has acted as a trustworthy steward over the years.”

Bitcoin Core developer, David Harding, stood up for Binns when Cobra called Binns a scammer. “I’ve been interacting with Will Binns for over six years now, first on Bitcoin.org and later as coworkers,” Harding wrote.

“We haven’t always gotten along, but I’ve never seen him try to scam anyone. Quite the reverse — I’ve seen him selflessly contribute to this project and others for no tangible return. I don’t know what’s happening in that conversation and I understand the need to be clear about who has what rights, but I don’t think a single confused conversation warrants the character assassination of a long-time contributor to multiple open-source documentation projects.”

Whatever the case may be, Binns has lost his position and there is literally ‘trouble in paradise’ when it comes to the web portal bitcoin.org. Cobra has always been a controversial figure and no one knows who he or Theymos is.

His sidekick Theymos is also an anon who once in a while participates in the bitcoin.org operations and discussions. Theymos also has complete control over r/bitcoin, the unofficial bitcoin wiki, and bitcointalk.org too. Both Cobra and Theymos, however, have been around since the early days. They both are mysterious and have maintained a lot of power, as far as bitcoin domain real estate is concerned ever since Satoshi left.

What do you think about the quarrel over bitcoin.org’s ownership? Let us know in the comments section below.

The post Bitcoin.org Maintainer Calls for the Removal of Cobra, Website Owner Then Fires Him appeared first on Bitcoin News.

Bitcoin Core 0.20.0 Released: What’s New

03/06/2020 by Idelto Editor

Today marks the official release of Bitcoin Core 0.20.0, the 20th major release of Bitcoin’s original software client launched by Satoshi Nakamoto over 11 years ago.

Overseen by Bitcoin Core lead maintainer Wladimir van der Laan, this latest major release was developed by over 100 contributors in a span of about six months. The result of more than 500 merged pull requests, Bitcoin Core 0.20.0 mostly cleans up and hardens the Bitcoin Core codebase, advances hardware wallet integration, improves network reliability and includes several other improvements.

Here are some of the more notable changes.

Further Hardware Wallet Integration in GUI

Bitcoin Core has been compatible with hardware wallets since version 0.18.0. However, users cannot yet make transactions with a hardware wallet from Bitcoin Core’s graphical user interface (GUI); they must instead use the command-line interface (CLI) to do that.

Bitcoin Core 0.20.0 is taking a step toward hardware wallet integration into the GUI. Users can now create a transaction without a signature in the Bitcoin Core GUI using the partially signed bitcoin transaction (PSBT) format, and copy it to their clipboard. Once copied, they can transfer the transaction to their hardware wallet to sign it — however, this transfer is not yet automated, and broadcasting the transaction still requires using the CLI.

Future Bitcoin Core releases will continue to advance hardware wallet integration.

Asmap for More Reliable Network Connectivity

Bitcoin Core connects to several peers (other Bitcoin nodes) on the Bitcoin network. Bitcoin Core maps other nodes based on their IP addresses, with the intent to establish connections with peers from various regions and Internet Service Providers (ISPs). If a node receives blocks and transactions from peers located all around the world, it decreases the risk that certain data (like a specific transaction) is withheld.

Bitcoin Core currently maps IP addresses by Network Operators’ Groups. However, several of these groups are actually part of the same Autonomous System (AS): clusters of Network Operators’ Groups that share key internet routes, and therefore potentially share the same routing bottlenecks where data could potentially be filtered.

Bitcoin Core 0.20.0 includes a new configuration option called Asmap, which maps IP addresses by Autonomous System Numbers (ASNs). This ensures that the node connects with peers from a range of different ASs, reducing potential network bottlenecks, thus further limiting the risk that specific data is withheld. (Mapping IP addresses into Network Operators’ Groups remains the default configuration for now, however.)

Removal of BIP61 Reject Messages

Reject Messages (BIP61) are notifications that a node returns when a transaction it received from a peer is rejected, and why. (Perhaps because the transaction is invalid, perhaps because it is considered not to include sufficient fee, perhaps there is another reason for the rejection.)

Bitcoin Core developers do not consider the reject messages very useful, however. Most importantly, peers shouldn’t be assumed to reliably return a Reject Message. In other words, if a node doesn’t receive a Reject Message, it doesn’t necessarily mean the transaction was accepted. This limits the usefulness of the messages, while there are better solutions to check that a transaction is valid and includes enough fees. Meanwhile, the messages were making the peer-to-peer protocol more complex, and were taking up bandwidth.

BIP61 Reject Messages had therefore already been disabled by default in Bitcoin Core 0.18.0. Bitcoin 0.20.0 has now removed the feature completely.

Removal of the BIP70 Payment Protocol (and OpenSSL)

The Payment Protocol (BIP 70) was designed several years ago to improve Bitcoin’s payment experience. A user and a merchant could communicate additional details about a payment, such as a human-readable destination address (the name of the merchant) and a refund address in case something went wrong with the purchase.

While Bitcoin Core integrated the Payment Protocol, the standard was never widely adopted. Instead, most wallets still use the more basic URI scheme (BIP21): The clickable link or scannable QR-code format that, for example, communicates the payment address and amount.

Perhaps more importantly than the lack of adoption, the BIP70 Payment Protocol suffered a number of security and privacy vulnerabilities over the years. Most notably, its dependency on the OpenSSL software library for cryptographic functions required a series of short notice emergency upgrades. Some Bitcoin wallets have, for these reasons, rejected implementing BIP70 altogether.

Bitcoin Core 0.19.0 removed the Payment Protocol from the GUI, but users could still compile their node with a special configuration to make use of the feature. Bitcoin Core 0.20.0 has now completely removed the Payment Protocol.

With BIP70 gone (and some other software tweaks to remove the dependency), Bitcoin Core has also been able to completely remove OpenSSL from its codecase.

Dumptxoutset As a First Step Toward Assumeutxo for Fast Bootstrapping

A new remote procedure call (RPC) lets Bitcoin Core 0.20.0 generate a snapshot of the UTXO set, which reflects the state of Bitcoin ownership as recorded on the blockchain at a specific point in time (block height). This snapshot can be shared.

Future Bitcoin Core releases will share such a snapshot when peers first join the network. This allows the new nodes to immediately start participating on the network from the point in time when the snapshot was made, while the entire history of the blockchain is checked in the background. (Like Assumevalid, a similar shortcut, Assumeutxo does come with trust tradeoffs before the entire blockchain is checked, and should until then be used with these tradeoffs in mind.)

For a more extensive list of upgrades, also see the Bitcoin Core 0.20.0 release notes.

Thanks to Sjors Provoost for information and feedback.

The post Bitcoin Core 0.20.0 Released: What’s New appeared first on Bitcoin Magazine.

Film Reels and Steel: Github Plans to Archive Bitcoin Code for 1,000 Years

01/04/2020 by Idelto Editor

The Microsoft subsidiary, Github recently revealed the “Archive Program,” an initiative that aims to preserve open source technologies for 1,000 years. The newly launched effort plans to store snapshots of open source technology 250 meters underground on the Norwegian island of Svalbard. The source code management and collaboration platform also plans to store the Bitcoin Core software. Archivists will etch the blockchain network’s code on film reels and encase the project in a steel capsule.

Also read: US Mortgage Industry Could Collapse as Housing Crisis Looms, Experts Say

Bitcoin Codebase and Other Open Source Crypto Projects Will be Stored Underground in a Time Capsule

Github plans to store the Bitcoin Core codebase within the depths of a mountainous region located in Norway. The project is a time capsule concept and Github is calling it the Archive Program. The program’s main goal is to store a number of open source technologies underground for 1,000 years so humans can access them in the future. Github says the mission of the program is to “preserve open source software for future generations.” The announcement reads:

The company is also partnering with the Long Now Foundation, the Internet Archive, the Software Heritage Foundation, Arctic World Archive, Microsoft Research, the Bodleian Library, and Stanford Libraries to ensure the long-term preservation of the world’s open source software. We will protect this priceless knowledge by storing multiple copies, on an ongoing basis, across various data formats and locations, including a very-long-term archive designed to last at least 1,000 years.

The Bitcoin Core repository will not be the only cryptocurrency-based repo added to Github’s time capsule initiative. A slew of other blockchain projects will be stored as well including the Ethereum and Dogecoin codebase and the Lightning Network. The company’s collaborating with Github believe in archiving software across various forms of ephemeral media and hosting platforms. The scheme is called “LOCKSS,” which stands for “Lots Of Copies Keeps Stuff Safe.” In order to ensure the safety and longevity of codebases like Bitcoin Core, the program will include “much longer-term media to address the risk of data loss over time.”

The Archive Program Hopes Future Historians Can Access Open Source Software Without Worrying About Lost Tech and Abandoned Code

There’s a significant history of events that show lost technologies and abandoned code can lead to catastrophe. The Archive Program aims to stop mistakes that society has seen in the past like the Saturn V blueprints, anti-malarial DFDT, and Roman concrete. “Like any backup, the GitHub Archive Program is also intended for currently unforeseeable futures as well,” the announcement highlights.

“Future historians will be able to learn about us from open source projects and metadata,” the Archive Program website reads. “They might regard our age of open source ubiquity, volunteer communities, and Moore’s Law as historically significant. We are already partnering with Stanford Libraries to help archive curated repositories along with the cultural and other context in which they are set, as key elements of wide-ranging historical and social research and analysis,” Github added.

After the announcement, software developers and cryptocurrency proponents discussed the topic on social media and forums. “[The Archive Program], and cockroaches, will be around long after the coronavirus kills us all,” one person jokingly tweeted. Seeing how the announcement was revealed on April 1, some people thought the news was an April Fool’s Day joke as well.

What do you think about Github storing the Bitcoin Core protocol for 1,000 years? Let us know in the comments below.

The post Film Reels and Steel: Github Plans to Archive Bitcoin Code for 1,000 Years appeared first on Bitcoin News.

Tron’s Steemit Acquisition Exposes Delegated-Proof-of-Stake Centralization

03/03/2020 by Idelto Editor

Tron's Acquisition of Steemit Exposes Delegated-Proof-of-Stake Centralization

The Steemit community is mired in controversy over the recent Tron takeover that managed to change the Steem blockchain’s governance. Steem witnesses attempted to soft fork the blockchain on February 24 to remove the powerful voting power Tron and Steemit hold. However, the soft fork wasn’t able to prevent the Tron takeover and Steemit community members are blaming Tron founder Justin Sun and three popular exchanges for gaming the outcome.

Also Read: Ethereum vs Tron: Comparing Data, Defi and Stablecoins from Both Chains After Viral Tweet

Tron’s Steemit Takeover Becomes Contentious

Steemit has always claimed to be a “decentralized blogging platform” but its decentralization and use of delegated-proof-of-stake (DPoS) have been controversial. Centralization concerns heightened after Steemit was sold to Tron. On February 14, former Steemit CEO Ned Scott tweeted: “Steemitans and Twitterers, after four beautiful years, I have sold Steemit to [Justin Sun].” Following the Steemit sale, a number of Steemitans were very upset with the decision and believed the acquisition would ruin the project.

The controversy prompted members of the Steemit community to invoke a soft fork that would reduce the voting power of the company Steemit Inc. and the Tron Foundation. However, the soft fork did not go as planned and on Monday, March 2, Steemit community members accused Poloniex, Binance, and Huobi of creating a “hostile takeover.” Reports detail that Steemit and Tron reversed the soft fork by leveraging over 42 million steem power (SP).

Your stake in Steem on centralized exchanges was just used to take over the Steem Blockchain https://t.co/AFn0LvEkUC

— Luke Stokes (@lukestokes) March 2, 2020

The reversal and the move to utilize 42 million SP caught the attention of the entire cryptocurrency community. Tron founder Justin Sun called the group of people who attempted to soft fork the Steemit chain “hackers.” “[Steemit] has successfully defeated the hackers [and] all funds are super SAFU. Steem Network and [the] Steemit community is now stronger than ever since we united [and] solved the difficulties,” Sun wrote. “On February 22, some malicious hackers froze 65 million steem legally owned by Steemit, the core steem developers,” Sun tweeted. “When we found out, the hackers already hijacked steem [and] threatened to nullify the existing steem. We had a difficult choice.”

Following the reversal and the statements from Justin Sun, Ethereum developer Vitalik Buterin commented on the DPOS incident. “Apparently Steem DPOS got taken over by big exchanges voting with depositors’ funds,” Buterin tweeted. “Seems like the first big instance of a “de facto bribe attack” on coin voting (the bribe being [exchanges] giving [holders] convenience and taking their votes).” The incident has started a debate about the vulnerabilities of the DPoS system and proof-of-stake systems in general. “The exact same thing occurs on EOS,” Youtube show host Colin Talks Crypto responded to Buterin’s tweet. “Just not as an extreme to an extent. This is why governance is important to nail down in DPOS — so a few huge exchanges don’t own your entire blockchain.”

Should an Exchange Use Customer Stakes to Vote on Governance?

Bitcoin Core Developer Jorge Timón also replied to Buterin’s criticism on Twitter and said that “DPOS is plutocracy voting.” “Not your keys, not your coins — This is not an attack, this is simply how [DPOS] works. [POW] is superior to both DPOS and ‘regular’ POS. POS is simply a bad replacement for [proof-of-work] — Eventually, you’ll have to accept this fact,” Timón stressed. Meanwhile, other crypto community members on social media discussed whether it was right to use customer stakes held on an exchange to leverage governance rights with a blockchain voting scheme. “The depositor may have a “balance” at the exchange, but do not have rights on that blockchain,” Bitcoin proponent Bob Loukas wrote on Twitter. Loukas added:

They exchanged that right for a paper guarantee, all for the purpose of speculation. If they had cared about the stake, they would have demanded that within their paper exchange.

“Na man, fork me? No, fork you.” #tron #steemit @justinsuntron pic.twitter.com/PEdPeE82Tj

— John Paul Faour (@olejpf) March 3, 2020

Steem Power Withdrawal Restrictions, Steem Developers Remove Apps, and Leaders Abruptly Resign

Despite the community outrage, what’s done is done and a recent blog post written by “the Tron folks and Steemit Inc. together” notes that the attempted soft fork was “maliciously structured.” “For the next 4-6 weeks, the Steemit team will be using the voting rights to resume the order of the community while having an open channel for meeting community members and Witnesses,” the post explains. The announcement also highlighted that Tron and Steemit wholeheartedly believe the soft fork attempt was “criminal and illegal.” “After the 4-6 weeks period, the Steemit team will give the governance back to the community when it’s back in order and mutual agreement,” the blog post states.

Members of the Steemit community are also upset because powered-up SP cannot be withdrawn for 13 weeks. Tron and Steemit also stressed that a hard fork would be taking place in order to change the power-down waiting period. The blog post notes it wants the “Steem blockchain running in parallel with Tron” and the team plan on providing more “rewards to witnesses.” In addition to this promise, the blog post claimed Steemit could acquire “more users” thanks to Tron’s “thriving ecosystem” and “active 15 million user community.” The post also added that the Steemit community would notice more development and developers from Tron contributing to the Steem network.

Still, the blog post doesn’t seem to be swaying the greater Steemit community and a few software engineers are removing their Steem apps from the ecosystem. Further, well known Steemitans like Andrew Levine have abruptly resigned from their governance duties.

What do you think about the recent incident with the Tron community and Steemit community? Do you think DPoS, or POS in general, can be gamed easily by exchanges? Let us know what you think about this subject in the comments section below.

Disclaimer: This article is for informational purposes only. It is not an offer or solicitation of an offer to buy or sell, or a recommendation, endorsement, or sponsorship 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.

Images credits: Shutterstock, Archive.org, Steemit, Twitter, Fair Use, Wiki Commons, Steemit and Tron logos,

Did you know you can buy and sell BCH privately using our noncustodial, peer-to-peer Local Bitcoin Cash trading platform? The local.Bitcoin.com marketplace has thousands of participants from all around the world trading BCH right now. And if you need a bitcoin wallet to securely store your coins, you can download one from us here.

The post Tron’s Steemit Acquisition Exposes Delegated-Proof-of-Stake Centralization appeared first on Bitcoin News.

Bitcoin Mining Investment Strong – BTC Hashrate Surpasses All-Time High

02/03/2020 by Idelto Editor

On Monday, March 2, miners processing blocks on the BTC network surpassed the network’s all-time high as the overall hashrate touched 136 exahash (EH/s). The record-breaking achievement happened despite the price of BTC dropping below the $9K region throughout the course of the last week. In four years’ time, BTC’s hashrate has risen over 13,500% and it doesn’t look like slowing up anytime soon.

Also read: 13 Crypto Debit Cards You Can Use Right Now

BTC’s Hashrate Between 136-145EH/s on Monday

Since the innovative payment network Bitcoin was invented, the hashrate has always been an indicator of security and the network’s overall wellbeing. Essentially, a hash is the output of a hash function applied to the Bitcoin software. When bitcoin miners are searching for blocks they leverage their processing power (hashrate) in order to increase their chances of acquiring freshly minted coins. The overall hashrate combined, meaning all the processing power between all the participating miners on the Bitcoin network, is basically the estimated measurement of how many hash functions are used in order to find a block. At the end of January 2016, the BTC network touched one exahash per second (EH/s). Since then, the hashrate has increased exponentially capturing 136EH/s on March 2, 2020. Blockchain.com and Fork.lol charts show BTC’s hashrate averages to be between 136 to 145EH/s.

In the last few years, Bitcoin mining investments have been strong and there’s been a number of new mining data centers added worldwide. For instance, the Peter Thiel-backed mining operation Layer1 recently started mining in West Texas. The company raised more than $50 million from investors like Peter Thiel, Digital Currency Group, and Shasta Ventures. Layer1 aims to scale operations to 200MW this year and there are many others in Texas mining as well. Last year, Bitmain revealed it would build a 300MW facility in Rockdale, Texas and started operations with 25MW.

During the second week of February 2020, Riot Blockchain revealed it had purchased 1,000+ Bitmain miners for its data center in Oklahoma. Riot Blockchain’s mine aims to capture 300MW of hashpower as well and the firm said the new batch of miners would be turned on immediately. Even smaller operations are investing in the industry, as this February Xtra Bitcoin announced the creation of a 2.5 MW facility with plans to increase to 10MW. Digihost claims to have a 70,000 square foot operation in Buffalo, New York with 12,895 bitcoin mining rigs (17.5 MW of computing power). New mining operations are popping up in Central Asia, the U.S., Canada, and many other nation-states which are fueling the rising hashrate.

Additionally, other SHA256 networks have seen an increase in hashrate, as Bitcoin Cash (BCH) has jumped from 1EH/s to 3.5-5EH/s, gathering a 400% increase since December 2018. Bitcoin SV (BSV) had around 1.3EH/s in December 2018 and that has expanded 130% to roughly 2.5-3EH/s in 2020. All three of these networks make up the overall SHA256 hashrate, which is one of the largest computational networks ever created. Satoshi Nakamoto launching the BTC network in 2009 has led to the significant advancement in Exascale computing. But people often wonder what an exahash is and all the other funny terms bitcoiners use like kilohash, megahash, gigahash, terahash, and petahash.

The Exahash Era Continues

A kilohash (1 kH/s) is 1,000 hashes per second, one megahash (MH/s) is approximately one million hashes per second, a gigahash (GH/s) is one billion hashes per second, a single terahash (TH/s) equals one trillion hashes per second, and one petahash (PH/s) is a quadrillion hashes per second. When we start measuring the hashrate in exahashes per second (EH/s), it is approximately one quintillion hashes per second. Right now, BTC’s network hashrate is roughly less than a quarter of the way toward reaching the zetahash (ZH/s) era, which is a whopping one sextillion hashes per second or 500 exahash. At 140EH/s, every second of the day the BTC network hashes 20x the number of grains of sand on earth, which is roughly estimated at 7.5 quintillion grains.

The 136-145EH/s record is quite a milestone and every time the network’s hashrate grows larger it makes it much harder to cheat the system. For instance a few minutes ago the mining operation Poolin found block 619845 and if a malicious miner wanted to alter block 619800, the miner would have to work on altering 45 blocks of extremely expensive computing (Proof-of-Work) with a one-hour attack cost of $775,936 at the time of writing. The malicious miner would need to expend around $18,622,461 during the course of a 24-hour period and meanwhile competing against all the honest miners processing the next blocks. Every time an honest miner finds another block it puts the attacker behind significantly, making it very expensive for miners to deviate from the rules.

Many speculators believe that the increased hashrate means that miners wholeheartedly believe in the future of SHA256 networks like BTC. Miners dedicate significant amounts of money to validate transactions in order to acquire 12.5 bitcoins and all the fees tied to the block’s transactions. In two months, all three SHA256 networks will see the network’s block subsidy chopped in half and miners dedicating hash toward BTC, BCH and BSV will only get 6.25 coins plus the fees.

The increase in combined computing power shows these entities have a lot of skin in the game, especially when estimates say BTC miners will need prices to be over $12,000 per BTC after the halving. So far, the BTC network has seen a natural progression of miners increasing the hashrate and there hasn’t been a major miner capitulation in over a decade. After the BTC halving occurs, all eyes will be watching the hashrate going forward as the metric has always been a solid indicator of the network’s overall security and growth.

What do you think about BTC’s hashrate touching between 136-145EH/s on March 2? Let us know what you think about this subject in the comments section below.

Image credits: Shutterstock, Bitcoin.com, Fork.lol, Fair Use, Bitmain Miners, Coin Metrics, Bitinfocharts.com, Coin.dance, Pixabay, and Blockchain.com charts.

Did you know you can earn BTC and BCH through Bitcoin Mining? If you already own hardware, connect it to our powerful Bitcoin mining pool. If not, you can easily get started through one of our flexible Bitcoin cloud mining contracts.

The post Bitcoin Mining Investment Strong – BTC Hashrate Surpasses All-Time High appeared first on Bitcoin News.