Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 8
Generated: 07:54:00
Login to reply

Replies (8)

There is nothing in Bitcoin Core 30 that makes it harder to run nodes. (Also see nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzdmhxw309aex2mrp0yhx5c34x5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvyzvgs2's response.)
2025-11-12 07:54:16 from 1 relay(s) ↑ Parent 2 replies ↓ Reply
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”.
2025-11-25 03:22:02 from 1 relay(s) ↑ Parent Reply
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.
2025-11-25 11:28:10 from 1 relay(s) ↑ Parent Reply