Etherum on the Move...

Ethereum depicted as a rocket blasting off

Artwork by Steven Grundy

What, more Crypto talk? Yes, sorry, more crypto talk, but I'll try to keep it short. Back on July 16th I said that I thought the bear market had ended that day and we were starting a new bull market. Only time will tell if I was right because we haven't had enough time to call it a bear market.

But, in that time, Ethereum, the bellwether coin that we measure with, is already more than 50% from that date and 120%+ since June 16th (2022). There are a lot of coins that did better than that, but for a "safe" bet like Ethereum, that's a really nice move.

But, it's not too late. Ethereum makes a change on September 26th that will dramatically improve it's capabilities. I think we are going to fairly quickly see ETH return it, and pass it's all time high of $4891.70, maybe even before the end of the year.

Now there is always the chance that ETH, and all coins, will turn around and head back down for a test of the low of $876.54. But, each day that goes by, and every new resistance point we move through makes me feel better about being right about that day in June being our low.

If ETH goes where I think it is going to go, it's not too late to get in. As always, don't invest any money in Crypto that you aren't prepared to lose. There is a very real risk involved with the wild swings of Crypto, including the chance that you could lose it all. But, if you do have some "spare" change sitting around, now might be the time to put that change to work for you.

Comments

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 ...

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...

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...

Search This Blog