I'd like to engage with you in good faith here. I hope you don't block me as a filteroor.
If the majority of the non-financial data (I like that terminology, by the way) is using some kind of exploit (OP_FALSE OP_IF or baremultisig, for example) then why is it bad to simply fix the exploit? These were not intended features, and in some cases the potential for abuse was raised ages ago.
I really don't see what the problem is with making arbitrary data as expensive as possible. Encode what you want in pubkeys, I guess. Pay full price for it. No discount. No multisig optimization.
I just don't buy that we have to stick to the existing consensus rules just because they are the existing consensus rules. If something is being abused, why can't we change it?
Again, I hope you take this reply in good faith.
lukedewolf / Luke de Wolf
npub1fk…jcwld
2025-10-29 12:47:13 UTC
in reply to nevent1q…egrp
Author Public Key
npub1fk8h6g8zhftw8c7pga2zjd84p2z949up5lc3qdchm9v4m0q7mwws7jcwldPublished at
2025-10-29 12:47:13 UTCEvent JSON
{
"id": "f97c859d2970acd8b224d241bd5b3d7b5e7da5ae22e3ad6df8e8a1110ad38060",
"pubkey": "4d8f7d20e2ba56e3e3c147542934f50a845a9781a7f1103717d9595dbc1edb9d",
"created_at": 1761742033,
"kind": 1,
"tags": [
[
"e",
"4459ab16b3928ff5b6eef6381d2949814def02bf0fea79b4d80a1933a43ede88",
"wss://relay.primal.net",
"root"
],
[
"p",
"dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6"
],
[
"r",
"wss://filter.nostr.wine/"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.land/"
],
[
"r",
"wss://nostr.wine/"
],
[
"r",
"wss://premium.primal.net/"
],
[
"r",
"wss://purplepag.es/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.nostr.band/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://relay.snort.social/"
],
[
"r",
"wss://purplerelay.com/"
],
[
"r",
"wss://nostr-relay.bitcoin.ninja/"
]
],
"content": "I'd like to engage with you in good faith here. I hope you don't block me as a filteroor. \n\nIf the majority of the non-financial data (I like that terminology, by the way) is using some kind of exploit (OP_FALSE OP_IF or baremultisig, for example) then why is it bad to simply fix the exploit? These were not intended features, and in some cases the potential for abuse was raised ages ago. \n\nI really don't see what the problem is with making arbitrary data as expensive as possible. Encode what you want in pubkeys, I guess. Pay full price for it. No discount. No multisig optimization. \n\nI just don't buy that we have to stick to the existing consensus rules just because they are the existing consensus rules. If something is being abused, why can't we change it? \n\nAgain, I hope you take this reply in good faith. ",
"sig": "12ee1ce45c28f339a6608a949f8ba78fb6a532cd2d8724548600bb42202dce6b9ea855c493e531c0351f10baf661d1f7ac57d7478c4032204a09dc910a3a8440"
}