Bitcoin Cash’s sudden announcement on Saturday that they’ll go ahead with a fork on August 1 caught a lot of people, including myself, by surprise. In this article, I’m going to explain what Bitcoin Cash (aka BCC) is, how it affects you and how you should prepare for August 1.
Bitcoin Cash?
Bitcoin Cash is peer-to-peer electronic cash for the Internet. It is fully decentralized, with no central bank and requires no trusted third parties to operate. The prominent use of “peer-to-peer electronic cash” is purposeful here. Bitcoin Cash is seeking to be a cryptocurrency that’s focused on transaction capacity.
Why is this fork a surprise?
Many people (including myself) thought that this fork would only trigger if BIP148 were able to split the network. In other words, many people thought Bitcoin Cash (and its client Bitcoin ABC) was just a credible threat to prevent a contentious user-activated soft fork (UASF).
So naturally, when BIP91 (first part of Segwit2x) locked-in and activated ahead of BIP148, which is scheduled for August 1, everyone pretty much assumed this would have prevented the so-called user-activated hard fork (UAHF) from triggering.
But, it looks like Bitcoin Cash supporters had other ideas.
Why should I care?
You should care because Bitcoin Cash is a permanent fork of Bitcoin. This means that if you own Bitcoin (that is, you control your own private keys) prior to the fork on 2017 August 1 12:20 UTC, you will have the same amount of Bitcoin and Bitcoin Cash after the fork.
Lest you think these BCC isn’t worth anything, BCC futures are currently trading at about $475 on ViaBTC.
What do I need to know?
First, you should know that many exchanges, including Coinbase, are simply not prepared for this event.
If I own Bitcoin, do I automatically own Bitcoin Cash too?
Yes. Because Bitcoin Cash is a fork of the ledger, that means you own the same amount of Bitcoin Cash as you did Bitcoin at the time of the forking block. However, if your Bitcoins are stored by a third party such as an exchange, then you must inquire with them about your cash. Exchanges or third-party bitcoin storage providers may or may not give you your Bitcoin Cash. It’s likely that third party services will try to do the right thing, but there’s no way to know if they can get everything set up in time to be able to give you the Bitcoin Cash you’re entitled to.
Second, all hard forks present two risks: replay and wipe out attacks. Wipeout is not a as much risk since this is a permanent fork (there are scenarios where one chain’s miners may attack the other, but this isn’t in play yet). Replay protection is provided as part of the Bitcoin Cash release as explained in the FAQ:
How is transaction replay being handled between the new and the old blockchain?
Bitcoin Cash transactions use a new flag SIGHASH_FORKID, which is non-standard to the legacy blockchain. This prevents Bitcoin Cash transactions from being replayed on the Bitcoin blockchain and vice versa.
Rest assured that as long as you control your own private keys, you should be able to use those keys to create transactions on either chain safely.
I thought Bitcoin solved scaling! Why is this happening?
Good question. After the scaling drama of the past few years, we finally made progress when BIP91 locked in on Thursday. Though Segwit increases transaction capacity, it’s not done so in a way that everyone is happy with.
BCC looks like an appeal to the segment of the Bitcoin users that don’t like Segwit. Since Segwit is getting activated on Bitcoin, this fork gives many of these people a place to go.
Why was a fork necessary to create Bitcoin Cash?
The legacy Bitcoin code had a maximum limit of 1MB of data per block, or about 3 transactions per second. Although technically simple to raise this limit, the community could not reach a consensus, even after years of debate.
