What's nonsense? I feel like missed something. Granted have been working a lot.
Login to reply
Replies (8)
What's nonsense I feel
like missed something Granted have
been working a lot
This haiku was found in the wild by npub1halkcws4lz49fdcznckk9unhsfh8yd6n6n7cnl68alkej7qptmxqjk60zq
Read the origin of this art: https://njump.me/df521e4374361491ef451a3717ecca57b3422e77dca54e8b84e839677b18149c
There is nothing in Bitcoin Core 30 that makes it harder to run nodes.
(Also see nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzdmhxw309aex2mrp0yhx5c34x5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvyzvgs2's response.)
Disagree. Maybe JB is referring to pruned nodes.
What he’s saying is that op returns will be more convenient for spammers and said spam can be pruned, a pruned node is not a fully validating node. So hopefully the spammers or attackers will use prunable data. Thats wishful thinking imho.
If spam is the concern we need to fix the segwit discount.
I don’t think spam is the cause for the change in v30. I think this change was pushed bc people want bitcoin to do ethereum like things 🚩
Removing limits altogether seems like the incorrect thing to do regardless, especially if cores intention was to “unify the mempool”.
There is nothing to disagree on, it’s a fact. You’ve been misinformed.
Correct
Murch explained it.. I don’t think he misinformed me.
Not correct. Large OP_RETURNs not only do not fix anything because inscriptions are still possible,
they add another place to put more spam. Gigabytes upon Gigabytes of spam and waste in the valuable Bitcoin Monetary space,
That waste requires more resources to store and process.