Bitcoin, blockchain, and what business actually needs from either

In December 2017 it is hard to ignore bitcoin. Its price is up roughly twenty times over the year, the news cycle is full of overnight fortunes, and almost every other conversation at business events veers toward cryptocurrency. This creates a lot of noise, and in that noise it is easy to lose a clear picture of what is actually happening.

I want to separate two different conversations that are currently being collapsed into one.

The first conversation: cryptocurrency as a speculative asset

Bitcoin and other cryptocurrencies currently function primarily as speculative assets. That is not an opinion - it is a description of what is happening. Most buyers are not buying bitcoin to pay for coffee or transfer money; they are buying it because they expect the price to rise.

Whether this is a bubble - I do not know. Nobody knows. Assets can rise to levels that seem absurd and then fall, or they can stabilise at some level. Financial market history has seen both outcomes.

For an executive the question is simple: if you invest in cryptocurrency, you are taking on speculative risk. Whether you assess that risk consciously is your business. But this is a different conversation, not a technology conversation.

The second conversation: blockchain as a technology

Blockchain is a distributed ledger with specific properties: records cannot be altered retroactively, it operates without a central administrator, and consensus is reached through defined mechanisms. Bitcoin uses blockchain as infrastructure, but blockchain is not the same as bitcoin.

This is where a more interesting and more complex conversation begins. Over the past couple of years, enterprise blockchain platforms have appeared - Hyperledger, Ethereum for enterprise scenarios, others. Large consortia are testing blockchain for trade finance, supply chain management, and interbank settlements.

What works and what does not?

Where blockchain solves a real problem

Blockchain solves a specific problem: when several parties that do not fully trust each other must share a reliable common ledger of transactions, and there is no neutral party that all of them are willing to trust to run that ledger.

That is not a very common situation. More often it turns out that:

• a central administrator exists and is trusted by all parties - in which case a normal database is cheaper and faster;
• the problem is not a lack of trust but inefficient processes - in which case automation is needed, not blockchain;
• performance requirements are incompatible with blockchain approaches.

Interbank settlements, trade finance involving multiple banks and jurisdictions, tracking complex multi-participant supply chains - these are genuine candidates. Internal corporate document management, CRM, employee directories - these are tasks where blockchain adds complexity without adding value.

How to think about this without the emotion

The question for any blockchain project is simple: "Why blockchain specifically, and not a normal database or centralised registry?"

If there is no answer, blockchain is probably not needed here. If there is an answer, you can proceed.

The filter:

1. Are there multiple parties with different interests who need to share data?
2. Is there no neutral party that all participants are willing to trust?
3. Is immutability of records required - and why specifically cryptographically verified immutability?
4. What is the actual cost of the solution with blockchain versus without?
5. Are there working enterprise blockchain projects in your industry whose experience can be studied?

Bitcoin will rise or fall - the market will sort it out. Blockchain as a technology will remain a niche but real tool for specific problems. Keeping those two conversations separate is already half of clear thinking on the subject.