> It moves it into trusting the protocol design, trusting the implementation of the clients, trusting your local hardware and OS to not be compromised
These are not central parties and they present risks with anything one does with a computer on a network.
> what to do if a transaction goes badly. In the cryptocurrency case, for the most part you're SOL, because cryptocurrencies by design don't allow anyone to e.g. void a transaction.
Transaction finality is a feature not a bug. Whatever conveniences that are enjoyed int traditional banking can be implemented in a layer on top of the base protocol.
> These are not central parties and they present risks with anything one does with a computer on a network.
If someone compromises my OS and steals my credit card details, the bank sends me a new card and handles the fraudulent charges on my behalf. I'm not out any money
If someone compromises my OS and steals my bitcoin private key, they can drain my entire wallet and I've lost everything, and have zero recourse.
If I'm a merchant and someone uses a stolen or cloned credit card, or simply performs a charge-back, they get my goods for free and I have basically zero recourse.
If I'm a merchant and someone pays me with bitcoin, I'm not out any money regardless, nor do I have to expend time/money/legal resources to ensure I keep that payment.
These are not central parties and they present risks with anything one does with a computer on a network.
> what to do if a transaction goes badly. In the cryptocurrency case, for the most part you're SOL, because cryptocurrencies by design don't allow anyone to e.g. void a transaction.
Transaction finality is a feature not a bug. Whatever conveniences that are enjoyed int traditional banking can be implemented in a layer on top of the base protocol.