As expected, Bitcoin Cash hardfork has activated, on August 1, as a result bitcoin blockchain has split into two chains. There is also a new digital asset that has a common history with bitcoin and traded under ticker BCC (BCH).
The activation of client Bitcoin Cash scheduled for 12:20 UTC, but there were some technical difficulties and inconclusive communications. Last block before the chain split was block 478558, and at 13:30 UTC on the resource btcforkmonitor.info there was information that the Bitcoin Cash nodes are operating order:
Soon found block 478559, and ironically it extracted by ViaBTC, the main supporter of Bitcoin Cash. But this block also has mined in the original chain of bitcoins.
Leading representatives of cryptocurrency ecosystem could not restrain their emotions about this, having published ironic posts in Twitter.
— Bobby Lee – Ballet: World's EASIEST wallet! (@bobbyclee) August 1, 2017
The representative of Samourai Wallet noted at the same time that the ViaBTC nodes came into conflict with each other.
Fresh from the press: ABC nodes banning each other on their own network. Mempool empty
— F (@fahmyeu) August 1, 2017
At the same time, as CnLedger pointed out, the ViaBTC pool directed Bitcoin Cash 82P for processing power, which, as noted by Charlie Schrem, is 1.2937% of the total bitcoin hash.
1.2937% of Bitcoin's total hashrate. We're gonna be here for a while folks https://t.co/myPmPFWTO7
— Charlie Shrem (@CharlieShrem) August 1, 2017
— cnLedger (@cnLedger) August 1, 2017
At the same time it is reported that Bitcoin Cash nodes do not accept block 478559, and fork, therefore, officially activated…
On the eve Bitcoin Cash fork, more majority exchanges, bitcoin wallets and other services has suspended operations and deposit and withdrawal ability.
Blockchain Bridges As Way Of Interaction Through Cryptocurrency Networks
Research: Ethereum, Cardano and IOTA Lead in Developer Activity
Monero Devs To Refuse Triptych In Favor Of Easier Solutions
Central Banks Of France And Switzerland To Test Cross-Border Transactions With CBDC