📅 Original date posted:2015-06-20
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2015-06-20 18:20, Jorge Timón wrote:
> On Fri, Jun 19, 2015 at 6:42 PM, Eric Lombrozo <elombrozo at gmail.com>
> 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…
>
> Non-repudiation can be built on top of the payment protocol layer.
Non-repudiation is an intrinsic property of the ECDSA signatures which
Bitcoin uses - it's not a feature that needs to be built.
There's no way to accidentally sign a transaction and accidentally
announce it publicly. There is no form of third-party error that can
result in a payee receiving an erroneous contract.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJVhfkXAAoJECpf2nDq2eYjTwIP/ApsURTKJgAsSYb4/lvoujAE
EhOUBfmb+WkrEceASWGgmXFfQBQW7c99sT46cA1HdCPLZMtYhZYPubtYRouSupfF
vOfeKLsZsUXCadeLuzxP7av3PJhmvB1CO1Rv8CLBQptKUFkzyM3CypBviNTy33X6
KL2zyAMERpCVOejg7MSP3IUXIjgG1ayEm+mzwqi4j2Ms0h+oT6I/krAKV0J9SwJC
PtLq/JRRriVtb2FE+biEqYRYfeOcZDYNbr+/y0HPtqqMxg6azNwx1z2aG5A+ziCd
EvVqVJXU3TAINQdIvVS4ACF1J+ttMJ99r8VW0yN7o3fEckuRr3pyymx4I+XExSX5
ujflqadRGUS8ZenUPTPUbLfhARnmBwLM94L+xiQvIwiinxxtOKn3WW1oDv9FNp0l
99fkv9mbV5RnYlkMfWMn2AcwcBv7TSgpFGsZY4wBn/mgFh1PotGc2tA5kU79cz8R
+F/k49+GwfgTPML7UhIGtjQjPreeqDyHNtv9XHtyp8LF5vO1na4oHSO6SeU4rIXH
4oIjw+Q6X/2L/fp8QNLB+onmKWobcl1Ec+0H+ZfQBujtew5BHFwcPwFmlC4tofiJ
7r8QjoPsRhJmaxm+MJOK/BIzhZErkMz26AQ/tfY4jtJCuLbEDdMLtC9hYVuiDHIb
HBxxif83dALjX1Sgid66
=o9dG
-----END PGP SIGNATURE-----
justusranvier at riseup.net [ARCHIVE] /
npub1qf…lfn9a
2023-06-07 15:39:10
in reply to nevent1q…x6tt
Author Public Key
npub1qf6k0f8p0h89d43l0vnx2xp5yrfgjyl8tg3hkg8jtyudrllgw2usdlfn9aPublished at
2023-06-07 15:39:10Event JSON
{
"id": "a116afc15e322c95ef3388f8011fbe9f75121f6e1b5528038fd2e4fa305cf128",
"pubkey": "027567a4e17dce56d63f7b2665183420d28913e75a237b20f25938d1ffe872b9",
"created_at": 1686152350,
"kind": 1,
"tags": [
[
"e",
"6b4025f674cbd304cabd44490b09b3ceb927f752f6a9f4513b25fefc95bdc008",
"",
"root"
],
[
"e",
"5aa2794117d9b3fb5642a272dfadbcc73f9aac75172f471e100d60407410e7e5",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2015-06-20\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nOn 2015-06-20 18:20, Jorge Timón wrote:\n\u003e On Fri, Jun 19, 2015 at 6:42 PM, Eric Lombrozo \u003celombrozo at gmail.com\u003e \n\u003e wrote:\n\u003e\u003e If we want a non-repudiation mechanism in the protocol, we should \n\u003e\u003e explicitly define one rather than relying on “prima facie” \n\u003e\u003e assumptions. Otherwise, I would recommend not relying on the existence \n\u003e\u003e of a signed transaction as proof of intent to pay…\n\u003e \n\u003e Non-repudiation can be built on top of the payment protocol layer.\n\n\nNon-repudiation is an intrinsic property of the ECDSA signatures which \nBitcoin uses - it's not a feature that needs to be built.\n\nThere's no way to accidentally sign a transaction and accidentally \nannounce it publicly. There is no form of third-party error that can \nresult in a payee receiving an erroneous contract.\n\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niQIcBAEBAgAGBQJVhfkXAAoJECpf2nDq2eYjTwIP/ApsURTKJgAsSYb4/lvoujAE\nEhOUBfmb+WkrEceASWGgmXFfQBQW7c99sT46cA1HdCPLZMtYhZYPubtYRouSupfF\nvOfeKLsZsUXCadeLuzxP7av3PJhmvB1CO1Rv8CLBQptKUFkzyM3CypBviNTy33X6\nKL2zyAMERpCVOejg7MSP3IUXIjgG1ayEm+mzwqi4j2Ms0h+oT6I/krAKV0J9SwJC\nPtLq/JRRriVtb2FE+biEqYRYfeOcZDYNbr+/y0HPtqqMxg6azNwx1z2aG5A+ziCd\nEvVqVJXU3TAINQdIvVS4ACF1J+ttMJ99r8VW0yN7o3fEckuRr3pyymx4I+XExSX5\nujflqadRGUS8ZenUPTPUbLfhARnmBwLM94L+xiQvIwiinxxtOKn3WW1oDv9FNp0l\n99fkv9mbV5RnYlkMfWMn2AcwcBv7TSgpFGsZY4wBn/mgFh1PotGc2tA5kU79cz8R\n+F/k49+GwfgTPML7UhIGtjQjPreeqDyHNtv9XHtyp8LF5vO1na4oHSO6SeU4rIXH\n4oIjw+Q6X/2L/fp8QNLB+onmKWobcl1Ec+0H+ZfQBujtew5BHFwcPwFmlC4tofiJ\n7r8QjoPsRhJmaxm+MJOK/BIzhZErkMz26AQ/tfY4jtJCuLbEDdMLtC9hYVuiDHIb\nHBxxif83dALjX1Sgid66\n=o9dG\n-----END PGP SIGNATURE-----",
"sig": "8def843da895c2b72415a4d46e3fa98354a05a69b85bc76b1da6eba0a3a6085fa76cb07abd2d713fc3758e285ef51d82ec3614e3ed0f54d536ceebb867bcb67e"
}