4 ms·
I don't think those things are comparable. A blockchain is a data structure. A social network is a product involving (many) data structures, including graph-bas
by throwawaymath 8y ago
I don't think those things are comparable. A blockchain is a data structure. A social network is a product involving (many) data structures, including graph-based ones. If you talk about a social network I generally understand what you're talking about. Not so with the term "blockchain."
I think part of the parent's point is that, at their core, blockchains are really relatively simple. But because they're data structures and people confuse them with actual products built over blockchains, there is a lot of semantic overloading that goes on.
When people refer to blockchains they may be variously referring to distributed consensus, the cryptographic primitives, the proof of work, the Merkle trees, the cryptocurrency or the end product built involving all of these things. These are all components which can be decomposed from the blockchain, which belies a general ignorance and lack of critical engagement with the concept for many advocates.
To be clear I'm not saying blockchains don't have viable use cases. Rather I'm saying there is a lot of noise inherent to any discussion about them.
- whytaka 8y agoTo be fair, a blockchain is the data structure, the mining software, the client wallets, the protocol of broadcasting and collecting transactions, the network of computers to make this work, and the people who use them. Not to mention the various added value innovations to make a particular blockchain attractive and useful to some people.
- throwawaymath 8y ago> To be fair, a blockchain is the data structure, the mining software, the client wallets, the protocol of broadcasting and collecting transactions, the network of computers to make this work, and the people who use them. No, that's not really correct - and this is exactly what I'm talking about. Saying a blockchain is all of these things is like saying a website is the backend application, the client web browser, the TLS protocol and all the users who use the website. But most of those things aren't the website. When we talk about the architecture of any given web application, we decompose these interactions and distinguish between them. We generally even distinguish between backend, frontend, infrastructure and and middleware resources on the server side. This allows us to productively talk about things with precision. In contrast any discussion involving the term "blockchain" suffers because it means 10 things to nine different people. It's not even an issue of generality. It would probably be fine if the term "blockchain" referred to entire networks and protocols built over blockchain data structures. Then referring to a blockchain would be like referring to "the internet." The real problem is the lack of precision, because in conversation different people are crossing all sorts of layers of abstraction, each to varying degrees of knowledge and expertise. That makes ascertaining the accuracy of claims a murky business for those who aren't substantially well informed.