Peter Todd [ARCHIVE] on Nostr: š
Original date posted:2015-02-13 š Original message:On Thu, Feb 12, 2015 at ...
š
Original date posted:2015-02-13
š Original message:On Thu, Feb 12, 2015 at 10:13:33PM +0000, Luke Dashjr wrote:
> Where is the Specification section?? Does this support arbitrary scripts, or
> only the simplest CHECKMULTISIG case?
It might be enough to rewrite this BIP to basically say "all pubkeys
executed by all CHECKMULTISIG opcodes will be in the following canonical
order", followed by some explanatory examples of how to apply this
simple rule.
OTOH we don't yet have a standard way of even talking about arbitrary
scripts, so it may very well turn out to be the case that the above rule
is too restrictive in many cases - I certainly would not want to do a
soft-fork to enforce this, or even make it an IsStandard() rule.
--
'peter'[:-1]@petertodd.org
000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1
-------------- 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/bitcoin-dev/attachments/20150213/7fe200a5/attachment.sig>
Published at
2023-06-07 15:30:30Event JSON
{
"id": "6ae3e3c24bec5344203db17d007eb59dbcdebc96708de4e98bf2a8706b36aec2",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686151830,
"kind": 1,
"tags": [
[
"e",
"6fe38e9bdbfb8e7b265ec7455bb55fed00b8dc2d19b617d9c69ed81fe0cca2fa",
"",
"root"
],
[
"e",
"d0d79ed07f4899f284bedf0d28b492904a5c9256cc24628d2c4205557390f008",
"",
"reply"
],
[
"p",
"5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803"
]
],
"content": "š
Original date posted:2015-02-13\nš Original message:On Thu, Feb 12, 2015 at 10:13:33PM +0000, Luke Dashjr wrote:\n\u003e Where is the Specification section?? Does this support arbitrary scripts, or \n\u003e only the simplest CHECKMULTISIG case?\n\nIt might be enough to rewrite this BIP to basically say \"all pubkeys\nexecuted by all CHECKMULTISIG opcodes will be in the following canonical\norder\", followed by some explanatory examples of how to apply this\nsimple rule.\n\nOTOH we don't yet have a standard way of even talking about arbitrary\nscripts, so it may very well turn out to be the case that the above rule\nis too restrictive in many cases - I certainly would not want to do a\nsoft-fork to enforce this, or even make it an IsStandard() rule.\n\n-- \n'peter'[:-1]@petertodd.org\n000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1\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/bitcoin-dev/attachments/20150213/7fe200a5/attachment.sig\u003e",
"sig": "2c008d738a6a874ce411fceeee3e92a3ad650cd61b744da912f671e6cd34dc6ca50a59034f7dc899e70e00cae0bfdc953bbe0eafb82d15bfa0bf3f3c3563d9b7"
}