Re:On the dangers of a blockchain monoculture
by murbard2 on Tuesday January 05, 2016 @02:53PM
(#10845540)
Blockchains can count, and thus handle mutations. That's the key difference:
https://medium.com/@arthurb/what-do-blockchains-accomplish-e...
On the other hand, if I have a transaction "Transfer 1 BTC to bitcoin.org" and you have a transaction "Transfer 1 BTC to mtgox.com", they don't necessarily commute or merge because of the double-spend problem: they might both be trying to spend the same 1 BTC.
There are a number of nifty decentralized systems you can build that don't have to think about double-spend problem, where all transactions commute/merge. Associating names with public keys seems to be one of them, as long as you allow a name to be validly bound to multiple keys. (A Keybase-style binding of external service usernames to public keys would permit this, since you simply have multiple valid Keybase proofs; the external usernames are arbitrated by the various centralized services. A Namecoin-style approach doesn't, since names are first-come-first-serve, and you don't want multiple people to be served the same name.)
There appear to be ways to make a money-transfer system avoid the double-spend problem: as I understand Stellar, it simply just makes the spending account legitimately owe both people money (and puts limits on how much each link can transfer at a time, so that the money is actually recoverable). But for non-money-transfer systems, if you can arrange your problem statement such that double-spending isn't a concern in the first place, you can use regular Merkle trees and avoid the entire proof-of-work overhead.