📅 Original date posted:2017-09-30
📝 Original message:10s of seconds if no further restrictions are placed. It would be trivial to include a new per input rule that reduces it to ~1s without cutting off any non-attack script (require sigops per input to be limited to witness/sig size). secp256k1 is now fast enough that we don’t need a separate sigop limit.
> On Sep 30, 2017, at 4:23 PM, Luke Dashjr <luke at dashjr.org> wrote:
>
> On Thursday 07 September 2017 12:38:55 AM Mark Friedenbach via bitcoin-dev
> wrote:
>> Tail-call execution semantics
>> BIP: https://gist.github.com/maaku/f7b2e710c53f601279549aa74eeb5368
>> Code: https://github.com/maaku/bitcoin/tree/tail-call-semantics
>
> Just noticed this doesn't count sigops toward the block sigop limit.
> Is that really safe? How long would it take, to verify a malicious block with
> only inputs such that there is nearly 4 MB of sigops?
>
> (I do already understand the difficulty in supporting the sigop limit.)
>
> Luke
Mark Friedenbach [ARCHIVE] /
npub1r3…48d0u
2023-06-07 18:05:38
in reply to nevent1q…435r
Author Public Key
npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0uPublished at
2023-06-07 18:05:38Event JSON
{
"id": "671e761a05c82414e169721342fcd76c193f78a4da24dd94bbe0b227e17634c2",
"pubkey": "1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069",
"created_at": 1686161138,
"kind": 1,
"tags": [
[
"e",
"0d97933d6393537f8afa1f55574e0ec2278e08b49a828e8a6bf1f6fff59c2613",
"",
"root"
],
[
"e",
"0722418e71458bbbac141f3924ec5aec2bd5656146d8d20493d9235149bd6b1a",
"",
"reply"
],
[
"p",
"5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803"
]
],
"content": "📅 Original date posted:2017-09-30\n📝 Original message:10s of seconds if no further restrictions are placed. It would be trivial to include a new per input rule that reduces it to ~1s without cutting off any non-attack script (require sigops per input to be limited to witness/sig size). secp256k1 is now fast enough that we don’t need a separate sigop limit.\n\n\u003e On Sep 30, 2017, at 4:23 PM, Luke Dashjr \u003cluke at dashjr.org\u003e wrote:\n\u003e \n\u003e On Thursday 07 September 2017 12:38:55 AM Mark Friedenbach via bitcoin-dev \n\u003e wrote:\n\u003e\u003e Tail-call execution semantics\n\u003e\u003e BIP: https://gist.github.com/maaku/f7b2e710c53f601279549aa74eeb5368\n\u003e\u003e Code: https://github.com/maaku/bitcoin/tree/tail-call-semantics\n\u003e \n\u003e Just noticed this doesn't count sigops toward the block sigop limit.\n\u003e Is that really safe? How long would it take, to verify a malicious block with \n\u003e only inputs such that there is nearly 4 MB of sigops?\n\u003e \n\u003e (I do already understand the difficulty in supporting the sigop limit.)\n\u003e \n\u003e Luke",
"sig": "f6b08ebc1c511071d15f67b19ec26392f3ad2b51fd5875e502d2d379627c5ad9c945879612e7a8fcb085f5c1f975a1fbb1aa6c192da808fa0c0070a1cc7d0887"
}