📅 Original date posted:2015-05-15
📝 Original message:On Friday, May 15, 2015 9:54:55 AM s7r wrote:
> If you strip both the scriptSig of the parent and the txid, nothing can
> any longer be mutated but this is not safe against replays. This could
> work if we were using only one scriptPubKey per tx. But this is not
> enforced, ...
Assuming you mean one output per scriptPubKey (and not limiting tx to one
output), the alternative is essentially undefined, and creates real problems
for Bitcoin today. It's not something we should go out of the way to support
or encourage. Therefore, regardless of whatever other options are available, I
would like to see a scriptPubKey-only sighash type for strong safety within
all malleability situations (including CoinJoin and other sender-respends)
that more advanced wallet software could take advantage of in the future
(while strictly enforcing no-reuse on its own wallet to avoid known replays).
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 15:35:14
in reply to nevent1q…qcl0
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 15:35:14Event JSON
{
"id": "7952d8f4b7d9f7ea57c8afe2cd05101e0e9de44b1835d3137f77f5cb675b470a",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686152114,
"kind": 1,
"tags": [
[
"e",
"d4296383f49c1a9f727ee325cad107826210d0f0a44bfb48a025773c99b7560e",
"",
"root"
],
[
"e",
"534fec89cf555eabc4478a795b75a831d9249787fdef82e00ea310c6f2f58700",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2015-05-15\n📝 Original message:On Friday, May 15, 2015 9:54:55 AM s7r wrote:\n\u003e If you strip both the scriptSig of the parent and the txid, nothing can\n\u003e any longer be mutated but this is not safe against replays. This could\n\u003e work if we were using only one scriptPubKey per tx. But this is not\n\u003e enforced, ...\n\nAssuming you mean one output per scriptPubKey (and not limiting tx to one \noutput), the alternative is essentially undefined, and creates real problems \nfor Bitcoin today. It's not something we should go out of the way to support \nor encourage. Therefore, regardless of whatever other options are available, I \nwould like to see a scriptPubKey-only sighash type for strong safety within \nall malleability situations (including CoinJoin and other sender-respends) \nthat more advanced wallet software could take advantage of in the future \n(while strictly enforcing no-reuse on its own wallet to avoid known replays).\n\nLuke",
"sig": "f52c27375bc2d98854b6491d58ddb366f2dae6d545b4f018440f473a56ac8d22856ce5ce085d3b67bef1f9ef46befe7f5c0c1bbbca6f6548caa2c4f7d4bdb347"
}