Skip to main content

Antshares Update - Up 80% in the past 2 months

In my June 28th post "Ants in the Pants - Jumping the gun with my NEOs coin purchase" I touched on why I like Antshares (ANT).  As a quick review here, Antshares can be looked at as a Chinese version of Ethereum (ETH).  Antshares has the addtional benefit of paying dividends in the form of Antcoins (ANC).

At the time, ANT was trading at about 0.0018 BTC, or about $7.50 per share.  As of today, ANT is trading at 0.0042, or about $13.50 per share.  That's an 80% increase in about 20 months, nothing to shake a stick at.  But, I see ANT potentially trading at close to the ETH price, which right now is $250 per coin.  ETH has been trading as high as $400 per coin in mid June.

If ANT were to approach those prices, that's at least a 20-fold increase over it's current price. Needless to say, ANT remains one of my favorite ALT coins in terms of "Home Run" potential.

Note: ANT doesn't trade on Poloniex but it does trade on Bittrex.  Also check out my earlier blog entry because it talks about ANT's pending name change.

Comments

  1. NEO, or AntShares as most people still know it as, is an open-source blockchain platform fully developed.The company has its own currency, which is found on most exchanges as ANS -the switch to NEO will happen later this year- and seems to be doing well. This upcoming rebrand from Antshares to NEO is part of a bigger move to put blockchain technology in spotlight.
    neo web wallet

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

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