-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2015-06-19 16:42, Eric Lombrozo wrote: > If we want a non-repudiation mechanism in the protocol, we should > explicitly define one rather than relying on “prima facie” > assumptions. Otherwise, I would recommend not relying on the existence > of a signed transaction as proof of intent to pay…
Again, I'm not talking about any changes to the protocol. The mining mechanism in the Bitcoin protocol is the fallback method of resolving fraud that isn't prevented or resolved via other mechanisms. There are plenty of other ways economic actors resolve their disagreements other than blockchain adjudication. Sometimes when both parties are identified and reside in the same legal jurisdiction, contract violations and fraud can be adjudicated in courts. In some situations, the parties involved may have access to private dispute resolution techniques. Sometimes the stakeholders in the network act to preserve the long term value of their investments, even if it means passing short-term profits. The more of those stakeholders there are in Bitcoin, the more effective it is to make the case for choices that are long-term beneficial. The degree to which anyone should rely on a signed transaction as assurance of future payment is not a question with a universal answer. It depends on the particular details of the situation, and the parties involved, and their own risk tolerances and time preferences. There's no right answer for everyone, which is why "let's break zeroconf because *I* don't think it's safe enough" is a kind of vandalism. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVhEkhAAoJECpf2nDq2eYj8qAP/0qYP7FJDjke1qNARGkySjC5 8fSuefu8bus/O2fNYsvPf0OcHeqepLUtQ/hgTml5AHaF1Fa9iZopVr8nZv0NFMuF sv9RfkBKvnnrLWre3e/kQIdKzdMXompEsDwGfIeM3qvVV9AD3mKrz/YNmjs60+hU rEdLCX8xw3ZvF3CGOzE1KnOMbADEd7i3E/Pm1n7pLVdRAg2CIU+w6mjErgucSdvB kQ9SNAVQngjhMJyVbxsQh/+/xgecdqeZ07aaGsLhiw6zML2Tz8KMhrjJ9xw9+7h0 Gze+JdqxpgH4QrvD8KMDnlZjM+cWDUGyoVfsRvrVvPdW6kejU1r1B5Pf6dJg9TwZ kK48RJFdd2rpAkz/kAbvQtoNMxSxhm2gKKFLEMi7g8MZUiGa/Rxj0tWL7OL9SA1U VfpUzgAovoat9lBQM92T5vcS6kfhiNgAmF24ULGGYIhts77Ae6h8Fl3TECtnR0dM 1U1yio4Im1TfUDfjqNSK+ZjVpzkQli0R057y6XzI9HWkSYo94WyjNVoUlUozuAam /2+tUMTrMYPeApRv+1nv13InYO8RZiFqs0E4w4TmB5V4Xt6uGUz4Olioyuo0NqMO lBZwa1ZWKw4fLgHHDu9FhTEOXsOcX5W0gEgcoqMlzTzyoapekk9Esd0pAFLYxYMY YQyAWtWUA4JBbgLxlB8Y =x8eh -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development