$66.5 billion worth of Bitcoin lost forever

Blockchain intelligence firm, Chainalysis, recently gave insight into the value of Bitcoins lost forever, revealing that about 3.7 million Bitcoin worth about $66.5 billion is lost forever and will remain unavailable to any buyer.

The report also discussed why the bullish run is far different from the crypto asset bubble seen in 2017.

From high-profile investors like hedge fund manager Paul Tudor Jones, who compared buying Bitcoin to investing early in Apple or Google, to corporations like Square, which invested $50 million or 1% of its total assets in Bitcoin, mainstream companies, and financial institutions are turning to Bitcoin.

The institutional move into cryptocurrency appears to be driven by a desire to hedge against macroeconomic uncertainty, which of course hasn’t been in short supply this year.

Jones himself put it well, saying, “Back in March and April, it became really apparent, given the monetary policy that was being pursued by the Fed, the incredible quantitative easing they were doing and other central banks were doing, that we were in an unprecedented time…one had to begin to think about how you defend yourself against inflation.”

What this means

Such macro, is partly responsible for the bullish run prevailing in the world’s flagship crypto market, taking into consideration that an estimated value of 77% of the 14.8 million has been locked up for more than five years. This means that there is just 3.4 million Bitcoin available for institutional and retail investors rushing to buy the prized crypto asset.

What you should know

A few months ago, Bigwig FX revealed how about 4 million BTC (worth some $30 billion at current prices) was lost as a result of the owners dying, and their next of kin not having access to such BTC wallets.

Bottom Line

As BTCs and cryptos become more prominent in daily activities, the volume of BTC being lost forever is likely to surge.



guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Inline Feedbacks
View all comments