📅 Original date posted:2023-02-17
🗒️ Summary of this message: A proposal was made to statically analyze inscription scripts to ensure they are "plausible" and increase their space cost by requiring OP_DROP to be added multiple times. The percentage increase is unknown.
📝 Original message:On February 18, 2023 1:35:34 AM GMT+02:00, Andrew Poelstra via bitcoin-dev
>You could try statically analyze `<anything>` to determine whether the
>IF branch could ever be taken. For example there is no path through
>the "inscription script" that would result in all the crap being dropped
>by the end of the script, violating the CLEANSTACK rule.
>
>This sort of filtering, assuming it could be reliably and efficiently
>done, would at least force inscription scripts to be "plausible", and
>would greatly increase their space cost by e.g. requiring OP_DROP to be
>added somewhere hundreds of times.
"greatly increase their space cost"?
Tell me, what is the actual % increase to adding OP_DROPs like you propose?
Peter Todd [ARCHIVE] /
npub1m2…a2np2
2023-06-07 23:19:36
in reply to nevent1q…rv4n
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 23:19:36Event JSON
{
"id": "ed88d0cc8380a9b29027be2a0886774a958653b2f9577dfb001a0296efc097f4",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686179976,
"kind": 1,
"tags": [
[
"e",
"7807d3e04dc01ad8077ddad8da65b8db69c52be6b75b739ede7749117e75dd4a",
"",
"root"
],
[
"e",
"9d9cc59c9942e8b30ad637d427e696b2e023225cddc794ffccacd9226a5e5ddd",
"",
"reply"
],
[
"p",
"6b8e77368804013d7126ba4b77c7963bcfeff909135791531097d7a0f03ca85d"
]
],
"content": "📅 Original date posted:2023-02-17\n🗒️ Summary of this message: A proposal was made to statically analyze inscription scripts to ensure they are \"plausible\" and increase their space cost by requiring OP_DROP to be added multiple times. The percentage increase is unknown.\n📝 Original message:On February 18, 2023 1:35:34 AM GMT+02:00, Andrew Poelstra via bitcoin-dev \n\u003eYou could try statically analyze `\u003canything\u003e` to determine whether the\n\u003eIF branch could ever be taken. For example there is no path through\n\u003ethe \"inscription script\" that would result in all the crap being dropped\n\u003eby the end of the script, violating the CLEANSTACK rule.\n\u003e\n\u003eThis sort of filtering, assuming it could be reliably and efficiently\n\u003edone, would at least force inscription scripts to be \"plausible\", and\n\u003ewould greatly increase their space cost by e.g. requiring OP_DROP to be\n\u003eadded somewhere hundreds of times.\n\n\"greatly increase their space cost\"?\n\nTell me, what is the actual % increase to adding OP_DROPs like you propose?",
"sig": "3f12ec1d8107115184fb4124892edc986bd6cd195b1690a2c502c9783cab299595630b3b6e87fe84f885f0bc04fc874ada550d5e6d6e79082dfdf4f85a0ffcd8"
}