📅 Original date posted:2023-05-08
🗒️ Summary of this message: A validation check to reject witness scripts with arbitrary data between OP_FALSE and OP_IF could prevent network overload while still allowing taproot benefits.
📝 Original message:From what I understand, things like inscriptions can only be inserted between two specific flags - OP_FALSE and OP_IF. Having a validation check to reject witness scripts that have arbitrary data between these two flags could be used to reject inscriptions while still allowing all the benefits of taproot. This will prevent people from overloading the network with txns geared solely for ordinals and brc-20 tokens.
Is there a reason such a validation check is a bad idea? We already have OP_RETURN to store arbitrary data that is limited to 80kb. Was it an oversight that arbitrary data can be inserted between OP_FALSE and OP_IF when the size limit for witness scripts was lifted as part of taproot?
Thanks,
Moth
Sent from Proton Mail for iOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230508/777d31ac/attachment.html>;
Moth [ARCHIVE] /
npub14k…904u6
2023-06-07 23:21:40
in reply to nevent1q…fkgl
Author Public Key
npub14k7l962pdlv8ak76jh532mhcx8hy7cc0effr4my54vzacr5eyvhsq904u6Published at
2023-06-07 23:21:40Event JSON
{
"id": "478ebade2eb32cbbc1c22ac2e2884f1b62770968a7603d68bebe34fee6d5235e",
"pubkey": "adbdf2e9416fd87edbda95e9156ef831ee4f630fca523aec94ab05dc0e99232f",
"created_at": 1686180100,
"kind": 1,
"tags": [
[
"e",
"569649b072848a6174ed646c40966783da04cda4306ba021091a69ba13849827",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2023-05-08\n🗒️ Summary of this message: A validation check to reject witness scripts with arbitrary data between OP_FALSE and OP_IF could prevent network overload while still allowing taproot benefits.\n📝 Original message:From what I understand, things like inscriptions can only be inserted between two specific flags - OP_FALSE and OP_IF. Having a validation check to reject witness scripts that have arbitrary data between these two flags could be used to reject inscriptions while still allowing all the benefits of taproot. This will prevent people from overloading the network with txns geared solely for ordinals and brc-20 tokens.\n\nIs there a reason such a validation check is a bad idea? We already have OP_RETURN to store arbitrary data that is limited to 80kb. Was it an oversight that arbitrary data can be inserted between OP_FALSE and OP_IF when the size limit for witness scripts was lifted as part of taproot?\nThanks,\nMoth\n\nSent from Proton Mail for iOS\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230508/777d31ac/attachment.html\u003e",
"sig": "c127217bbe61f68fbcb1480201bb620a26cd518eb689384456f5d66cfc7da67084113216235ce1259acd58bee0dd7c94c5c8dd6c7362267efcf4d5002bc733d9"
}