Skip to main content

As the BTC Fork approaches, what about Bitcoin Cash?

As the November 16th Fork day for Bitcoin approaches I am getting more and more apprehensive about it. I really have a hard time seeing this fork go well. If you've been following me for the past year or so you'll know that's 100% different view from what I normally have.

I have already moved most of my holdings to cash (Tether) and for my BTC brethren I encourage you to at least consider sitting this one out. I don't know who is going to be the winner here, BTC, B2X, or some other coin, but I've been hearing more and more about maybe Bitcoin Cash (BCH or BCC) being in play as the survivor.

Here's a REALLY interesting article that talks about that possibility. I can't argue against any of what is in this article.

https://www.yours.org/content/predicting-the-outcome-of-the-november-bitcoin-fork-89914ce0e1f5/?utm_content=bufferf3dec&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

Comments

  1. UnknownMay 28, 2018 at 12:51 AM

    Nice blog. Unlike other cryptocurrencies, NEO works on a share-based system. So, when thinking about what NEO, it’s better to think of it as a security than a cryptocurrency. In fact, each NEO is considered by the “NEO Smart Economy” to be one share of the NEO blockchain. So, essentially, NEO is a portion of ownership! Learn more at: Neon Beginner

    ReplyDelete
  2. Coins ShieldOctober 5, 2021 at 5:26 AM

    It’s great to come across a blog every once in a while that isn’t the same out of date rehashed material. Fantastic read.Best best crypto trading platform service provider

    ReplyDelete

Post a Comment

Popular posts from this blog

Troubleshooting a Discourse Update on DigitalOcean: Resolving Unresolvable Errors

For the past three years, I've maintained a Discourse server on a DigitalOcean Droplet. Recently, I decided to update it with some of the latest Discourse features. What I anticipated to be a straightforward update process turned into several days of frustrating setbacks. The version of Discourse I was running was already three years old, so I assumed that running the built-in "Update" feature would suffice. However, after clicking the update button, the progress bar sluggishly crawled forward over the next half hour, only to display the dreaded message: "Error – Update Failed." The logs provided little to no help, but based on my experience with other software updates via GIT, I suspected that the failure might be due to the repository head still being called "Master." In recent years, there has been a shift away from using "Master" as the repository head, with "Main" becoming the preferred term. Despite trying several methods ...
Post a Comment
Read more

Ethereum Merge - So What?

Artwork by Steven Grundy The long awaited Ethereum "Merge" is finally upon us.  I've heard people say "So what".   So what?  I think they don't understand the implications of the merge.  Either that or they really are betting against Ethereum. I think this upgrade is probably the biggest thing for Ethereum since smart contracts first came out.  This change has the possibility of upsetting the apple cart in terms of Ethereum and BTC.  That's a big claim, but I really think it's possible. The Ethereum Merge has been set for the week of September 19th, 2022.  The merge is when the Ethereum execution layer will be joined with the new proof of stake consensus layer.  What does that mean and why should I care? What it means is that Ethereum will be changing from an energy intensive Crypto coin like all others to a 99% more efficient crypto coin like only a few have done.  Right now Ethereum is mined just like BTC and a host of other Crypto cur...
Post a Comment
Read more

Yelp api via Coldfusion and oAuth

What should have been a fairly easy implementation turned into several frustrating hours. I was using the old Yelp API that is accessed simply by passing your yelp key in the url. But, I wanted to take advantage of some of the new functionality only available in their API version 2.0. Unfortunately Yelp API v2 requires an oAuth key/signature type access. Having already written similar code to access the Amazon web services with a signature I thought this would be a simple as reusing some existing code. Man was I wrong. Turns out a "correctly" implemented version of oAuth is much less tolerant than AWS is. Simple things, such as what characters in the URL must be encoded, invalidated the Yelp signature. After much searching and screwing around with various proposed implementations it became clear that the easiest and best implementation was to use the Java library provided by Yelp and simply access it from Coldfusion. To make this process easier I've consolidated th...
Read more