Skip to main content

Segwit Activated on LiteCoin (LTC)

Perhaps the biggest problem with Bitcoin (BTC) is the ongoing argument about how to scale it.  The developers have been arguing about various approaches to scaling for a couple years now.  It used to be that BTC transactions were very cheap and would clear in a manner of minutes.

Now, although still cheap in comparison with traditional fiat currency fees, the BTC transaction fees have climbed while the transaction speed has decreased.  It is now common for it to take 20 minutes to an hour (sometimes hours) for a BTC transaction to be confirmed.

One of the main contenders for a solution to this is called Segregated Witness, or SegWit.  SegWit has been in the BTC code for a while now but BTC has been reluctant to roll it out to full production.  Now another large coin called LTC has rolled out SegWit and it has performed as designed.  With that happening it is much easier for developers to get on board with SegWit for BTC.

Should that happen, then likely the BTC price would soar.  See the accompanying article for more about that and the predicted $5000 BTC price in the near future...

https://cointelegraph.com/news/bitcoin-price-new-all-time-high-at-1442-bitfury-executive-predicts-5000

Comments

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

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