3 ms·
Only in a crazy loose sense. Git histories do not have enforced immutability or trustlessness. And they are really merkle trees, which have been around for deca
by UncleMeat 8y ago
Only in a crazy loose sense. Git histories do not have enforced immutability or trustlessness. And they are really merkle trees, which have been around for decades. If blockchains (as described in this manner) are so amazing, why wasn't there hype for merkle trees in 1995?
- pdpi 8y agoI think you misunderstood my point — The reason I distinguished between blockchain-the-data-structure and blockchain-the-trustless-consensus-protocol is precisely because the word used to mean specifically the former but got coopted to refer to the latter. The blockchain data structure has been around for decades, and a Merkle tree is precisely the tree analogue to a blockchain's linked list. Trustlessness is a property of Nakamoto consensus, not of the blockchain data structure, but the combination of the two (or something that bears passing resemblance to that combination) is what usually gets called a "blockchain". Unfortunately this usage of the word is borderline useless because people keep loosening the requirements of the system so as to allow their harebrained setups to count as a "blockchain".