|
I really wish I could remember where I read this so I could give proper credit -- Somewhere I read a helpful way to rephrase "blockchain" that really helps cut to the heart of the issue when you're dealing with technical questions like this: A blockchain is just an ordered series of files, each of which contains a hash of the previous one in the series. So, when you've got someone saying, "What if we use blockchain?", just mentally substitute the suggestion as, "What if we store the data as an ordered series of files, each of which contains a hash of the previous one in the series?" Any bits of the proposed system that aren't impacted by the decision to store the data as an ordered series of files, each of which contains a hash of the previous one in the series, also don't have anything to do with whether or not it needs to involve a blockchain. (Yes, I realize there are additional questions around trust and proof of work and whatnot that come into play when you're talking about blockchain-as-in-cryptocurrency, but, as far as I can tell, it's a rare case that proposed use cases for blockchain in business are ones where anyone even wants trustlessness. See, for example, Walmart trying to use a centralized blockchain to manage their edible leaf supply chain.) |
Mentioning the hash is an implementation detail -- it is what gives blockchains their immutability property.
So I'd say even simpler: a blockchain is merely an append-only register that can be used by multiple parties.