📅 Original date posted:2015-11-22 📝 Original message: On Thu, Nov 19, 2015 at ...

Peter Todd [ARCHIVE] /

npub1m23…2np2

2023-06-09 12:45:11

in reply to nevent1q…gzw8

📅 Original date posted:2015-11-22
📝 Original message:
On Thu, Nov 19, 2015 at 11:12:24AM -0800, Tadge Dryja wrote:
> I've joked that BIP62 is the "whack-a-mole" BIP in that it addresses many
> vectors for txid malleability, but maybe there are more. And more
> importantly, it addresses 3rd party malleability. It's not helpful in the
> context of lightning channel creation because ECDSA sigs are inherently
> malleable. You can always re-sign the same message with a different
> k-value and get a different signature.
>
> The functionality that's needed is to be able to reliably spend from
> unconfirmed transactions. Segregated witness can accomplish that, but it
> quite a large hard-fork change. sighash_noinput can also accomplish that:

It's definitely not a hard-fork change.

In fact, I'll point out that in general it's actually pretty hard to
come up with features that absolutely must be implemented as hard fork
changes.

--
'peter'[:-1]@petertodd.org
000000000000000001a06d85a46abce495fd793f89fe342e6da18b235ade373f
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 650 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20151122/1959b3ec/attachment.sig>;

Author Public Key

npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2

Show more details

Published at

2023-06-09 12:45:11

Kind type

1 Short Text Note

Event JSON

{ "id": "8e7c58ffa57908f5f5e7344f133718f109f3ecbe72db62bf98048d64663ab7bc", "pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa", "created_at": 1686314711, "kind": 1, "tags": [ [ "e", "1af72c6403b0bf6c208cd96111979b74febacb268ea0e46444fb1495c20b46af", "", "root" ], [ "e", "4e609b0eb5e66abb0fbc642a8e40d48ada92c4cf0bb406fd1a25718669788653", "", "reply" ], [ "p", "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425" ] ], "content": "📅 Original date posted:2015-11-22\n📝 Original message:\nOn Thu, Nov 19, 2015 at 11:12:24AM -0800, Tadge Dryja wrote:\n\u003e I've joked that BIP62 is the \"whack-a-mole\" BIP in that it addresses many\n\u003e vectors for txid malleability, but maybe there are more. And more\n\u003e importantly, it addresses 3rd party malleability. It's not helpful in the\n\u003e context of lightning channel creation because ECDSA sigs are inherently\n\u003e malleable. You can always re-sign the same message with a different\n\u003e k-value and get a different signature.\n\u003e \n\u003e The functionality that's needed is to be able to reliably spend from\n\u003e unconfirmed transactions. Segregated witness can accomplish that, but it\n\u003e quite a large hard-fork change. sighash_noinput can also accomplish that:\n\nIt's definitely not a hard-fork change.\n\nIn fact, I'll point out that in general it's actually pretty hard to\ncome up with features that absolutely must be implemented as hard fork\nchanges.\n\n-- \n'peter'[:-1]@petertodd.org\n000000000000000001a06d85a46abce495fd793f89fe342e6da18b235ade373f\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20151122/1959b3ec/attachment.sig\u003e", "sig": "6f1c09558c6c9b2780b787e8d889484ae28272a68e7efb58a20a21a8e2b2a850024f107d4af79b851a7e7285e5eb567c0571b1841d5cf97234b6d4da6fda5c30" }