Skip to main content

Bitcoin - Money, Investment, Gold?


Bitcoin's a fascinating story. So much has happened in its short existence. Price explosions (and crashes), debates about the future of money, the emergence of an infinite universe of cryptocurrencies and crypto-related businesses. Despite Bitcoin's impact, I still have a hard time getting the point of it. 

Born in 2009, Bitcoin was a response to the Great Financial Crisis. Massive bailouts raised a lot of concerns about the stability of money. Backed by code and free from human messiness, it was supposed to be the new standard - decentralized and incorruptible. Unfortunately, it hasn't played out this way. 

Adoption's been weak. There's no incentive for businesses to accept it or for consumers to use it. Good ol' cash is easy, so why bother? 

Bitcoin is volatile. It's extremely inflationary and deflationary, able to move violently in either direction in moments. Money needs to be stable, no one can make rational spending decisions otherwise. 

Plus, it's technically limited. Bitcoin can only process about 5 transactions per second. In comparison, Visa can process 24,000. It's not fit for a widely used currency. 

Running up against these drawbacks, advocates have shifted Bitcoin's narrative from being money to being an investment or a store of value. Sadly, it doesn't do well here either.

The value of stocks and bonds comes from future cash flows - whether it is from owning a piece of a company's earnings or from being owe interest. Bitcoin has no cash flows. Its value only comes from what someone else is willing to pay for it. Purely speculative. 

As a store of value, it's too volatile (see above). You're not storing value if it can crash at any moment. 

I'm not anti-Bitcoin. I think it's really interesting. When you learn more about it, it's a technical marvel. Cleverly solving for decentralized trust, a problem that's stumped really smart people for a long time. However, from a financial use perspective, I just don't get it. 

























Comments

Popular posts from this blog

Today's Special: Humble Pie

You champion a project, fight for an idea, and then...reality sets in. That churning in your stomach isn't butterflies, it's the realization you've missed the mark.  Pride will puff up your chest, and kick in the "defend at all costs" instinct. But arguing with the umpire never changed a call. Admitting you're wrong isn't a sign of weakness. It can strengthen your professional standing. In a world obsessed with the illusion of infallibility, the courage to adjust course is a breath of fresh air. It shows you're confident enough to be wrong, and adaptable enough to learn from it. Do your research, think critically, and stand behind your decisions. But when the data whispers (or screams) otherwise, don't be afraid to swallow that slice of humble pie. Be the first to acknowledge. Don't wait for someone to point out your mistake. Be open, take responsibility, and most importantly, focus on what you're going to do to address it. Don't dwell ...

Starting Really Really Small

On your desk is one of the most intimidating sights known to man. A blank page. The prospect of filling it up with anything resembling decent seems insurmountable. Staring at the long road ahead fills you with anxiety and dread.  The first step is the most difficult. So we procrastinate. We " research ", we " prep ", we " plan ". We do everything except tackling the problem. We avoid the pain for as long as we can.  To make a blank page less intimidating. Tear it in half. There, half as scary, twice as easy. Still too much? Do it again. And again. Keep doing it until the task is so small that it's too easy not to do.  Getting starting is the hardest part. So make the hardest part as easy as possible. This doesn't guarantee amazing results, but it gets you in the game. You can't win if you don't play.  

Why We Shouldn't Be Afraid of Ambiguity

Ambiguity. That fuzzy monster that chases us down darkened hallways, whispering doubts about our roadmap and feature sets. You know the feeling. You constantly wrestle with unknowns: Will users like this? Is this the right direction? Frankly, if you had a nickel for every time the answer wasn't crystal clear, well, you might actually want to chase that ambiguity down the hall. But here's the thing: ambiguity isn't your enemy. It's your dance partner. Innovation rarely happens in a land of perfect clarity. Sure, there's a time for well-defined processes. But when you're creating something new, there are bound to be more questions than answers. The key is to learn to waltz with the unknown .  Embrace the experiment. Don't be afraid to throw some spaghetti at the wall and see what sticks.  Focus on outcomes, not outputs. Don't get hung up on features. What problem are you trying to solve? How will you measure success? Get comfortable with "go...