March 20, 2026

Capitalizations Index – B ∞/21M

Bitcoin Cash ‘Chain-Splitting’ Bug was Detected by Bitcoin Core Dev.

Bitcoin cash ‘chain-splitting’ bug was detected by bitcoin core dev.

Bitcoin Cash ‘Chain-Splitting’ Bug was Detected by Bitcoin Core Dev.


Coinbase bug cryptocurrency
Advertisement

It has emerged that the “unknown person” who notified bitcoin ABC developers of a vulnerability in Bitcoin Cash which would have resulted in the unintended split of the altcoin’s network is actually a bitcoin Core (bitcoin’s primary software implementation) developer.

In a Medium blog post, Corey Fields revealed that he was responsible for anonymously and privately informing bitcoin ABC of the SIGHASH_BUG in bitcoin Cash on April 25 this year. According to Fields, who works for MIT Media Lab’s Digital Currency Initiative, if the vulnerability had been successfully exploited it would have resulted in making bitcoin cash transactions unsafe, thus undermining the fourth-largest cryptocurrency by market capitalization. As CCN reported, the flaw was fixed early the following month.

bitcoin’s Biggest Threat

In the same post, Fields warned that the greatest threat facing bitcoin is related to software development.

“I’m often asked at conferences and workshops what I consider to be bitcoin’s greatest challenge in the future. My answer is always the same: avoiding catastrophic software bugs,” he wrote.

According to Fields, the threat posed by software bugs with regards to cryptocurrencies is underestimated and companies in the space must make adequate preparations for these kinds of threats. As an example, Fields narrated the hoops and loops he had to jump through before he could inform bitcoin ABC of the vulnerability.

Part of the problem was that bitcoin ABC did not have a responsible disclosure policy. Additionally, Fields could not find publicly available encryption keys for the lead developers at bitcoin ABC to whom he could send encrypted message informing them of the vulnerability without risking it being viewed by others.

‘People Have Been Killed for Much Less’

According to Fields, it was also important to remain anonymous for personal safety reasons just in case a malicious actor discovered the vulnerability and went on to exploit it before a fix could be rolled out. This would be problematic as suspicions could fall on Fields.

“Because I used my name for the disclosure, hard proof would exist that I had the knowledge and means to attack the network. I would have no way to prove that I was not the attacker. Then consider that, collectively, billions of dollars could have been lost as a result of this exploit. People have been killed for much less,” wrote Fields.

At the time when Bitcoin ABC announced that the vulnerability had been fixed, it was revealed that a reward would be given to the then-anonymous tipster once they went public. In his blog post, Fields did not disclose whether he has claimed the reward.

Featured Image from Shutterstock

Follow us on Telegram or subscribe to our newsletter here.
Join CCN’s crypto community for $9.99 per month, click here.
Want exclusive analysis and crypto insights from Hacked.com? Click here.
Open Positions at CCN: Full Time and Part Time Journalists Wanted.

Advertisement


Published at Sat, 11 Aug 2018 23:54:59 +0000

Altcoin News

Previous Article

Dynamic Trading Rights Price Prediction

Next Article

Charles Hoskinson Cardano Update 7 Aug 2018

You might be interested in …

Crypto Prizes On The Rise, Magical Marketing Or Another Scam?

Recent Uploads tagged cryptocurrency Crypto Prizes On The Rise, Magical Marketing Or Another Scam? Cryptocurrency Latest News posted a photo: from Cointelegraph.com News ift.tt/2J9QZjE | Get 3% OFF On #GenesisMining The Largest Cloud Mining Service […]

BIP 91 Has Activated. Here’s What That Means (and What It Does Not)

BIP91.jpg

It looks as if bitcoin is getting Segregated Witness.

Bitcoin Improvement Proposal 91 (BIP 91) just locked in. Up to 90 percent of all hash power signaled support for this soft fork, which implies miners intend, in turn, to trigger Segregated Witness (SegWit) activation. By extension, this should make BIP 148 obsolete and August 1 a non-event.

But SegWit is not certain. In fact, on a technical level, SegWit is not any closer to activation at all.

BIP 91

Segregated Witness, defined by BIP 141, locks in if at least 95 percent of miners (by hash power) signal support for the upgrade within a two-week difficulty period. To do so, miners need to embed a piece of data called “bit 1” in the blocks they mine.

Importantly, this is technically the only way for SegWit to activate right now. And this threshold has not yet been met.

But there are alternative strategies to try and reach this threshold “indirectly” — like BIP 91.

BIP 91 is a bitcoin Improvement Proposal proposed by Bitmain Warranty engineer James Hilliard. It is compatible with the New York Agreement and backed by a number of bitcoin companies and mining pools. It is also compatible with BIP 148, another strategy to meet the BIP 141 threshold indirectly.

Miners have been signaling support for BIP 91 over the past couple of days through another piece of data, “bit 4.” Once 269 blocks within a 336-block window include bit 4, this BIP 91 soft fork gets locked in. This threshold was just met.

This means that after another 336 blocks, a little over two days from now, all BIP 91–compatible nodes will reject any block that doesn’t include bit 1.

As long as a majority of hash power enforces BIP 91, this majority should eventually control the longest valid chain according to all bitcoin nodes. And as this chain consists of bit 1 SegWit-signaling blocks only, it would in turn activate SegWit on all SegWit-ready nodes.

In that case, BIP 141 should lock in by mid-August, and SegWit should be live on the bitcoin network after a two-week “grace period” by the end of that month.

If all goes well …

What Could Go Wrong?

Although well over 80 percent of hash power has signaled bit 4 for BIP 91 activation, this doesn’t actually guarantee anything. Most importantly, it doesn’t in itself mean that these miners will signal bit 1 for SegWit.

Indeed, so far, most miners don’t. Currently, the proportion of miners signaling bit 1 is still far lower than BIP 91 activation would suggest. It is even lower than 50 percent.

Moreover, BIP 91 is probably being enforced by hardly any economically relevant nodes; that is, nodes operated by users that accept bitcoins as payment. Almost no bitcoin users on the network recognize BIP 91 or its bit 4 signaling at all, and will therefore continue to accept blocks with or without bit 1.

BIP 91 is, instead, enforced by hash power alone. This in turn means that a majority of miners (by hash power) could back out of BIP 91 with little more than reputational damage. They could continue to mine blocks that do not signal bit 1, even after BIP 91 activates in a few days. As long as these miners are in a majority, they will still control the longest valid chain: valid according to most miners, and valid to most users.

Furthermore, any minority of miners and the few nodes that do enforce the BIP 91 soft fork would then be forked off the bitcoin network. In a few days from now, these miners would mine (on top of) blocks that almost only they themselves would consider valid, while most of the rest of the entire bitcoin network would completely ignore them. These miners would be wasting their own resources.

With this week’s bit 4 signaling, a majority of miners have effectively made a statement that they intend to start to activate the SegWit soft fork within a couple of days. But for now, that’s really all it is: a very public, blockchain-based statement of intent.

Actual SegWit activation should start next week, if miners stick to their stated intent.

The post BIP 91 Has Activated. Here’s What That Means (and What It Does Not) appeared first on Bitcoin Magazine.