The thing is I believe we're in a catch-22 situation where an actual supermajority of node runners want to filter inscriptions from their mempools but they don't know how to do it (because BC devs and most node distros aren't making it easy), or they don't even realize they can do it. If I'm right and the situation ends resolving this way the patch will be no more and no less effective than minrelaytxfee. There are 0-fee txs from time to time but they aren't half of the mempool space.
Regarding other Bitcoin Script opcode sequences to embed arbitrary bytes in tx: I don't think they even need to be patched. If the network coordinates to reject this first kind of txs it should discourage spammers from trying much further. Detecting these patterns and patching them out is orders of magnitude easier than finding them, then it's just a matter of how fast most nodes patch them out.
I won't tell you what to do with Raspiblitz. But your users are sovereign to filter inscriptions, and some of them want to do it. They placed their trust in you, and you can either respect that sovereignty or you can try to get in the way of it. That's just the way it is.
Unhosted Marcellus
npub100…dfyy5
2023-03-21 12:35:04
in reply to nevent1q…5zmr
Author Public Key
npub100mahqlhxg50thmt5dyynu40nl25hat9kkkknzk8pqjfkvgq0xsqtdfyy5Published at
2023-03-21 12:35:04Event JSON
{
"id": "7ae32d6cf5dda20bd7ccc813fe3173714cb04b31bf159b28c3afa3c35d12ed47",
"pubkey": "7bf7db83f73228f5df6ba34849f2af9fd54bf565b5ad698ac708249b310079a0",
"created_at": 1679402104,
"kind": 1,
"tags": [
[
"e",
"21918a0d894af5dd9d255b01fb469e64b7e47bd4ca2abfbaaf97f4fbb886697e"
],
[
"e",
"b4804448542baa7e628efdbaf1b4b772c7a3ec82de7178e5acb7391dd8ad2dfb"
],
[
"e",
"8aa584c3c85e61660b1af3f5132410004931ad4fbed74ff88a0344b582391698"
],
[
"p",
"7bf7db83f73228f5df6ba34849f2af9fd54bf565b5ad698ac708249b310079a0"
],
[
"p",
"efc19139d25c06d59347b9f1a9a52f011efc68980b1dcb09c5eb1c62a370b6a8"
],
[
"p",
"ea2e3c814d08a378f8a5b8faecb2884d05855975c5ca4b5c25e2d6f936286f14"
],
[
"p",
"b17fccdf07ba2387f038b34426720cd68d112df923bca2bed8f8c309b7211155"
],
[
"p",
"6fd3915a55ad0c2eae64e2b818acbbae9c6b3d9b5ee44e19aa040fb09f0d3cdd"
],
[
"p",
"7bf7db83f73228f5df6ba34849f2af9fd54bf565b5ad698ac708249b310079a0"
],
[
"p",
"efdd75e5bda78d9678eb43acaeb7e2aeef52ce2c1442cbce375a358ec1dd2628"
],
[
"p",
"aac07d95089ce6adf08b9156d43c1a4ab594c6130b7dcb12ec199008c5819a2f"
]
],
"content": "The thing is I believe we're in a catch-22 situation where an actual supermajority of node runners want to filter inscriptions from their mempools but they don't know how to do it (because BC devs and most node distros aren't making it easy), or they don't even realize they can do it. If I'm right and the situation ends resolving this way the patch will be no more and no less effective than minrelaytxfee. There are 0-fee txs from time to time but they aren't half of the mempool space.\n\nRegarding other Bitcoin Script opcode sequences to embed arbitrary bytes in tx: I don't think they even need to be patched. If the network coordinates to reject this first kind of txs it should discourage spammers from trying much further. Detecting these patterns and patching them out is orders of magnitude easier than finding them, then it's just a matter of how fast most nodes patch them out.\n\nI won't tell you what to do with Raspiblitz. But your users are sovereign to filter inscriptions, and some of them want to do it. They placed their trust in you, and you can either respect that sovereignty or you can try to get in the way of it. That's just the way it is.",
"sig": "70240950ba0dc625d6852b83c5c4fd020a46bbe30c689ff439c762e21aac1167ada809336f2b620cc1f28587256dff145c7272e8e12943775f5e3537810edd6e"
}