Tag: Hard Fork

spot_img

Coinbase Clarifies its Position on the SegWit2x Hard Fork

Coinbase has made some interesting decisions regarding SegWit2x. More specifically, they first denounced this chain as a pure altcoin. This is still a valid...

No Exchange or Wallet Supports Bitcoin Gold 10 Days Before the Fork

A lot of people tend to forget there will be two Bitcoin hard forks in the next few weeks All eyes are on SegWit2x,...

Bitcoin Cash – Does It Have A Future?

On August 1st, at exactly 6:12 pm GMT, the first Bitcoin Cash block (block no. 478559) was mined by Viabtc's miners, announcing the birth...

An Imminent Fork, Bitcoin Cash and Possible Chaos – Are You Prepared?

    The bitcoin community has been on a state of turmoil during the past few months, and even though most bitcoiners felt relieved after the...

SegWit2MB Proposal Combines Segwit Activation With Predetermined Block Size Increase Date

Even though it sometimes appears as if we are getting closer to a bitcoin scaling solution, that is far from the case. Yet another...

Should Bitcoin Hard Fork To End The Block Size Discussion?

The ongoing Bitcoin blocks size debate remains a source of considerable controversy. Despite a meeting taking place between Bitcoin developers over the weekend, there...

Mounting Number of Bad Coding Mistakes Haunts The Ethereum Ecosystem

The ongoing debate over the Ethereum hard fork decision has brought some interesting concepts to light. Unfortunately for Ethereum investors and holders, it turns...

Double Your Bitcoins With The Coinbase Ethereum Exchange Bug

The launch of Ethereum Classic and its support by the community has raised a lot of questions. More particularly, what about the exchanges where...

Soft Forks, White Hats, and SEC Oh My!

The mess surrounding the DAO attack is not over. The majority of the Ethereum community seems to be leaning towards a soft fork in...

To Fork or Not to Fork: 24 Days To React

The past few days in the world of dApps and Altcoins has been quite eventful, to say the least. An attacker found a bug...