Earlier quoted context omitted.
I’ve said it before, and I’ll say it again: It’s because “blockchain” software is a thing that already exists, but its superclass, “distributed log of signed proofs” software, isn’t a thing that already exists (except in the form of the subclass, blockchain software.) There are tons of use-cases for which a “distributed log of signed proofs” is the perfect fit. Have you got an architecture where nodes independently m…
I am coming to think that it's precisely the "distributed" bit that nobody really wants. For example, distributed version control systems are often held up as an example of some form of precedent for blockchain-type technologies. But I've never actually seen a truly distributed (in the blockchain sense) deployment of Git. It's technically possible, but it just doesn't seem to happen. Similarly, I'm not sure people ac…
Distributed adds complexity but is pretty much essential for illegal activities which is why it is needed for cryptocurrencies which would otherwise be shut down for not KYCing everything and bittorrent which would be shut for copyright infringement. Otherwise centralized is usually easier.