Nostr Web Client

Still can't be pruned. Still has to be in a data structure that you need to be eventually able to search. There's no way to tell if pubkey will be spent on the future.

leadbyexample 2mo ago

I can produce another analogy 😊

Just kidding.

I played with AI to make some simulations.

So let's assume one could either store garbage at 1sat/vB, or at 10sat/vB (let's say it will be uneconomical to go beyond10 for sick shitcoinining spammers).

Let's also consider that while OP_RETURN has basically just its storage costs, using fake pubkeys carries larger overhead per unit of shitcoinery size, plus each fake pubkey output requires its dust limit 546sats to be locked forever, same thing as paying a fee.

Long story short, no matter the total garbage size (I queried for 1kb, 20kb and 100kb) at 10sat/vB, using fake pubkeys instead of OP_RETURN means spending about 3x the cost per shitcoin size unit, but other than that you're also paying 10sat/vB which is not cheap.

At 1sat/vB (more realistic at current feerates), using fake pubkeys costs a whopping 18x OP_RETURN.

I understand shitcoiners do not care about messing with the UTXO set, but they do care about spending as little as possible.

Are we sure it's a good idea to give them a cheaper, better alternative to do that, which was not available before?

Do you know what the cobra effect was?

Reply to this note

Please Login to reply.

Discussion

Juraj 2mo ago

Yes, I know the cobra effect.

Please remember the shitcoiners were happily paying a lot:

During the peak of Bitcoin ordinals and inscriptions activity in early May 2023 (particularly around May 7-9), the fee rates paid for transactions, including those for inscriptions and ordinals, typically ranged from approximately 100 to 700 sats per vByte.

While it's a good idea to increase the price to be just a bit cheaper than the worst option, the filters don't do that.

The criminal liability is mostly FUD. Node runners are not even held criminally liable for accepting sanctioned transactions as valid. And the 'it's continuous' is mostly bullshit. Also, it's not a real problem, no one really wants to store cp in Bitcoin. Why spreading the fud now? If it happens, you just prune it from your node or don't answer the request for that particular tx in p2p if it comes to that. It won't.