📅 Original date posted:2015-04-28
📝 Original message:> On 27 Apr 2015, at 21:21, Peter Todd <pete at petertodd.org> wrote:
>
> Even right now there are edge cases without
> good solutions, like how in a multisig environment any of the key
> holders can mutate transactions.
Can't we add requirement for RFC6979 signatures to mitigate this? Of course, multiple signers can still mutate transaction by choosing a different set (but not the order, thankfully) of signatures. Or when a single signer has multiple participating keys.
In some interesting to me scenarios mutation by signer is not critical: it is mutation by non-signers that creates a problem. Do you know of any edge cases when non-signers can mutate transactions which are not covered by BIP62? What would be a more robust approach than "whack-a-mole" to work around mutability? (Normalized tx ids?)
Oleg Andreev [ARCHIVE] /
npub13f…v7cz5
2023-06-07 15:32:34
in reply to nevent1q…uf4q
Author Public Key
npub13f3qkf0gj3zwnypll339zsjsjsw2xxxnm5m3xzyzrdxtuvxafq4qmv7cz5Published at
2023-06-07 15:32:34Event JSON
{
"id": "84bc31aa7df30fc3d077e1890ba8d8e48403c9b19b9662fd702252e3fce42f74",
"pubkey": "8a620b25e89444e9903ffc62514250941ca318d3dd371308821b4cbe30dd482a",
"created_at": 1686151954,
"kind": 1,
"tags": [
[
"e",
"8b8a2347eb8a1165154b18f1aa6b1f8a0b99712f1e1f9461e574d86e0b7c9986",
"",
"root"
],
[
"e",
"ef56c8658df9d95e007724c540671d475ef83c0d8025494dd7a13ba3fc6be64d",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2015-04-28\n📝 Original message:\u003e On 27 Apr 2015, at 21:21, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e \n\u003e Even right now there are edge cases without\n\u003e good solutions, like how in a multisig environment any of the key\n\u003e holders can mutate transactions.\n\nCan't we add requirement for RFC6979 signatures to mitigate this? Of course, multiple signers can still mutate transaction by choosing a different set (but not the order, thankfully) of signatures. Or when a single signer has multiple participating keys.\n\nIn some interesting to me scenarios mutation by signer is not critical: it is mutation by non-signers that creates a problem. Do you know of any edge cases when non-signers can mutate transactions which are not covered by BIP62? What would be a more robust approach than \"whack-a-mole\" to work around mutability? (Normalized tx ids?)",
"sig": "c5a05a6a545ce18737c258fbfff4cfe0eb73c7f80273add5766cfa62109f33c22230ed18879ef8531f118afef19854ed6d3154eaa490ef7c707c5da99255a321"
}