{"type":"rich","version":"1.0","author_name":"npub1qf6k0f8p0h89d43l0vnx2xp5yrfgjyl8tg3hkg8jtyudrllgw2usdlfn9a","author_url":"https://nostr.ae/npub1qf6k0f8p0h89d43l0vnx2xp5yrfgjyl8tg3hkg8jtyudrllgw2usdlfn9a","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-19\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nOn 2015-06-19 16:42, Eric Lombrozo wrote:\n\u003e If we want a non-repudiation mechanism in the protocol, we should\n\u003e explicitly define one rather than relying on “prima facie”\n\u003e assumptions. Otherwise, I would recommend not relying on the existence\n\u003e of a signed transaction as proof of intent to pay…\n\nAgain, I'm not talking about any changes to the protocol. The mining \nmechanism in the Bitcoin protocol is the fallback method of resolving \nfraud that isn't prevented or resolved via other mechanisms.\n\nThere are plenty of other ways economic actors resolve their \ndisagreements other than blockchain adjudication. Sometimes when both \nparties are identified and reside in the same legal jurisdiction, \ncontract violations and fraud can be adjudicated in courts. In some \nsituations, the parties involved may have access to private dispute \nresolution techniques.\n\nSometimes the stakeholders in the network act to preserve the long term \nvalue of their investments, even if it means passing short-term profits. \nThe more of those stakeholders there are in Bitcoin, the more effective \nit is to make the case for choices that are long-term beneficial.\n\nThe degree to which anyone should rely on a signed transaction as \nassurance of future payment is not a question with a universal answer. \nIt depends on the particular details of the situation, and the parties \ninvolved, and their own risk tolerances and time preferences. There's no \nright answer for everyone, which is why \"let's break zeroconf because \n*I* don't think it's safe enough\" is a kind of vandalism.\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v2\n\niQIcBAEBCgAGBQJVhEkhAAoJECpf2nDq2eYj8qAP/0qYP7FJDjke1qNARGkySjC5\n8fSuefu8bus/O2fNYsvPf0OcHeqepLUtQ/hgTml5AHaF1Fa9iZopVr8nZv0NFMuF\nsv9RfkBKvnnrLWre3e/kQIdKzdMXompEsDwGfIeM3qvVV9AD3mKrz/YNmjs60+hU\nrEdLCX8xw3ZvF3CGOzE1KnOMbADEd7i3E/Pm1n7pLVdRAg2CIU+w6mjErgucSdvB\nkQ9SNAVQngjhMJyVbxsQh/+/xgecdqeZ07aaGsLhiw6zML2Tz8KMhrjJ9xw9+7h0\nGze+JdqxpgH4QrvD8KMDnlZjM+cWDUGyoVfsRvrVvPdW6kejU1r1B5Pf6dJg9TwZ\nkK48RJFdd2rpAkz/kAbvQtoNMxSxhm2gKKFLEMi7g8MZUiGa/Rxj0tWL7OL9SA1U\nVfpUzgAovoat9lBQM92T5vcS6kfhiNgAmF24ULGGYIhts77Ae6h8Fl3TECtnR0dM\n1U1yio4Im1TfUDfjqNSK+ZjVpzkQli0R057y6XzI9HWkSYo94WyjNVoUlUozuAam\n/2+tUMTrMYPeApRv+1nv13InYO8RZiFqs0E4w4TmB5V4Xt6uGUz4Olioyuo0NqMO\nlBZwa1ZWKw4fLgHHDu9FhTEOXsOcX5W0gEgcoqMlzTzyoapekk9Esd0pAFLYxYMY\nYQyAWtWUA4JBbgLxlB8Y\n=x8eh\n-----END PGP SIGNATURE-----"}