2016 was the year of creating frameworks and filters to determine if a business problem was worthy of a blockchain-based solution. Often, the frameworks would declare inappropriate potential use cases as ripe for blockchaining, as the frameworks were often designed by blockchain vendors or consultants to let as much through as possible. However, many of the proofs of concepts built in 2016-17 have not become industrial solutions. Why?
Two main reasons are:
- The technology didn’t meet the requirements of the use case
- The use cases themselves were selected badly
This post discusses what went wrong with use case selection, and presents two new and better questions for use case selection.
There is a lot of misleading commentary about smart contracts, leading to confusion about what they are and what they can do. Here are three of the most common myths that I have noticed. This builds on a previous piece, a gentle introduction to smart contracts.
Myth: Smart contracts are self-executing bits of code
Following on from the “Blockchain is a solution looking for a problem” narrative of 2016, distributed ledger technology has evolved.
Distributed ledgers – databases with shared control over what and how data is added – can be seen a strategic solution to the “reconciliation” workaround that we have had to put up with until now. This strategic solution is applicable to all industries, not just financial services.
I enjoyed listening to Episode 151 of the podcast “Epicenter” (previously “Epicenter Bitcoin”) featuring Ian Grigg, inventor of Ricardian Contracts and blogger at Financial Cryptography. Here are my notes – part transcription, with some edits. This one is a goldmine and covers many topics: bonds, contracts, cash, Chaumian e-cash, DigiCash, financial cryptography, Ricardian contracts, digital signatures, smart contracts, dispute resolution, Ethereum, triple entry book-keeping, oh my!
Misunderstandings and paraphrasing errors are entirely mine.
This gets fairly technical; if this is hard to follow, it may be helpful to read my introduction to smart contracts first. Hmm, if it’s still hard to follow, also read about blockchains and bitcoin and Ethereum, and digital tokens.
This post tries to describe two very different uses for blockchain technology: Digital Token Ledgers that record ownership changes of digital tokens, and Activity Registers that record timestamped proofs of existence of data or agreements about data. Bitcoin is used for both.
Over the past year I have come across many blockchain ‘proof of concepts’, that take existing business ideas or challenges and apply a specific technical design (blockchains) to the solution. The usual problem/solution decision process has been turned on its head:
Is blockchain solutioning from Fear Of Missing Out?
I enjoyed listening to episode 112 of the podcast “Epicenter Bitcoin” where Casey Kuhlman, CEO of Eris Industries was interviewed. Here are my notes on parts that I found particularly interesting. Misunderstandings and paraphrasing errors are mine.
If this is hard to follow, it may be helpful to read my introductions to blockchains, bitcoin, digital tokens, and smart contracts first.