112 karma · joined January 25, 2014
I'm referring to a new way of constructing software, using a transactional database at the core and defining every event as a transaction between two parties. Today engineers usually think of the platform as a distribution medium for data, aka. client-server. In the BC world refining this so that any party can take on any role, aka. decentralized/distributed is challenging. I'm trying to explain that this go far beyond a new JS framework or (no-)sql database, in the BC environment the engineer must be able to define and code business rules.
> Since those [p2p] products all failed
I don't think p2p failed because of technology, but rather because mgmt/industry wanted to keep control. See e.g Spotify or Skype as examples, there are many other interests at play than pure technological.
> tax evasion (value added tax and in some case corp. tax)
I agree with your view, but if you examine today's platform economies this is exactly what they have done to a large extent. They give away "free" services only to cash in on your personal data from a near tax free country setup. Examples are FB, Google, Apple, Amazon..
Having studied the BC stack, I would say that the biggest obstacle will be to get engineers to dare try something new. To many SW-engineers on the web-side today, don't really have sufficient skills to understand BC-technology. I don't mean to offend, just state what I see. We saw the same thing with p2p-tech before that.
Solidity as a programming language is an interesting abstraction and perhaps lowers the barrier somewhat, but it will take many years before the skills available match that for what is required to gain momentum on a broad scale.
If you're an engineer and wonder why mgmt keeps bringing it up, its because this will potentially help them build a platform (two-sided) market. If that occurs and you constructed it correctly, your company may well be able to skip on taxes as well, as a side-effect.