📅 Original date posted:2016-02-09
📝 Original message:> 2) In order to prevent significant blowups in the cost to validate
> [...] and transactions are only allowed to contain
> up to 20 non-segwit inputs. [...]
There is two kind of hard fork, the one who breaks things, and the one who
does not.
Restricting the non-segwit inputs would disrupt lots of services, and
potentially invalidating
hash time locked transactions, which is a very bad precedent.
So I'm strongly against this particular point.
> scriptPubKeys are now limited to 100 bytes in
> size and may not contain OP_CODESEPARATOR, scriptSigs must be push-only
> (ie no non-push opcodes)
Same problem for native multisig, however potentially less important than
the previous point.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160209/a04a4478/attachment.html>;
Nicolas Dorier [ARCHIVE] /
npub1hu…9q4u3
2023-06-07 17:48:59
in reply to nevent1q…67tq
Author Public Key
npub1huz53hq26gu7nc0qhw3uj6tr9hk5q2ngpywduxep5zy4ay9unftsm9q4u3Published at
2023-06-07 17:48:59Event JSON
{
"id": "9e3b6f5a20d755403f2145533bef4308f224fc7b7010bf1d15b99449c2ca9d3c",
"pubkey": "bf0548dc0ad239e9e1e0bba3c969632ded402a68091cde1b21a0895e90bc9a57",
"created_at": 1686160139,
"kind": 1,
"tags": [
[
"e",
"8c25de74ae7131786de7d5ab012e48bad7eff95963972248b7442bdb60a9ffb5",
"",
"root"
],
[
"e",
"7678c7f305538fccc39910a793d0bf7eb12b96200e34d8721a5cf9531ba44907",
"",
"reply"
],
[
"p",
"1bd05a5503fb6854f03714081df3970b79306bc9f28bd4ec35add5b3317755d7"
]
],
"content": "📅 Original date posted:2016-02-09\n📝 Original message:\u003e 2) In order to prevent significant blowups in the cost to validate\n\u003e [...] and transactions are only allowed to contain\n\u003e up to 20 non-segwit inputs. [...]\n\nThere is two kind of hard fork, the one who breaks things, and the one who\ndoes not.\nRestricting the non-segwit inputs would disrupt lots of services, and\npotentially invalidating\nhash time locked transactions, which is a very bad precedent.\nSo I'm strongly against this particular point.\n\n\u003e scriptPubKeys are now limited to 100 bytes in\n\u003e size and may not contain OP_CODESEPARATOR, scriptSigs must be push-only\n\u003e (ie no non-push opcodes)\n\nSame problem for native multisig, however potentially less important than\nthe previous point.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160209/a04a4478/attachment.html\u003e",
"sig": "51435cf889f5be53f80417652bed15478af48df4beaa7ed8bd270dd6121a5d23de2b0f35d909a89a6efb642c034817574a7c8051dfb18bc8fa989be5c1141c29"
}