Spam filters mean there will be less spam.
If you're worried about side effects like centralization of mining or UTXO set bloat then let me know when you're ready to take those problems seriously instead of LARPing about it and nuking OP RETURN limits.
UTXO bloat and mining centralization are *serious issues* in Bitcoin.
You don't get to do absolutely nothing about them for years then invoke them when coming up for convenient excuses for killing datacarriersize.
Mining *is* centralized. There's no amount of bending over we can do relaying the stupidest trash possible around the network appeasing miners and scammers that can roll back the tide there just in the hopes that MARA becomes less motivated to maintain Slipstream.
Where have the serious people gone?
Thread
Login to reply
Replies (20)
The argument that this PR will reduce out-of-band payments is especially disingenuous. OP_RETURN usage will quickly max out, and then pools will go right back to taking these payments. Then we'll have two problems instead of one. I highly doubt spammers who have developed some process that depends on out-of-band are going to completely refactor and switch to OP_RETURN. They'll continue doing what works, especially when blocks are bloated with even more spam. Out-of-band payments will increase if anything.
People should consider this situation a remote parking lot in a national park. Typically, only a few hikers show up, but when the wildflower bloom occurs, the area fills up with cars. Volunteers, known as node runners, install a 7-foot clearance bar at the entrance. While sedans and SUVs can still pass through, larger RVs that want to camp for the weekend and occupy multiple spots for little or no fee cannot. Since the beam is permanently welded in place, any future volunteer, referred to as a miner, must enforce the same height limit. This system has no central authority; it relies on the structure that has been passed down.
In contrast, consider a scenario where a single volunteer bans gasoline-powered cars, blocking valid transactions. This personal choice can easily be reversed when the next volunteer allows gas guzzlers in, pocketing the parking donations. However, many supporters of Ordinals/BRC-20 are now confusing this height limit, which is neutral and equitable, with censorship, equating it to outright bans. This misunderstanding persists despite their earlier support for Marathon's real OFAC blocklistβfilters should not be mistaken for censorship.
Great analogy.
Many truths sincerely spoken my friend.
This seems to have turned out differently in other areas.

Are there any proposed solutions for the bloat of the UTXO set? If spammers attempt to make a UTXO un-spendable with a false receiver address but otherwise follow TX consensus rules, is there a way to stop it? Thanks and love & support what you do!
Nobody answers this, they just ignore the question.
I believe that Luke has a solution, but people wonβt listen because of ego.
Ok, thanks. Iβll be on the lookout for it.
Luke not only had 1 solution to the problem, it looks like he coded 3 solutions. Also had more options.

GitHub
Witness scripts being abused to bypass datacarriersize limit (CVE-2023-50428) Β· Issue #29187 Β· bitcoin/bitcoin
The datacarriersize policy option is meant to limit the size of extra data allowed in transactions for relaying and mining. Since the end of 2022, ...
Thanks KC. That was a long thread to get through and canβt say I understand much of the programming details but still good background info.
I found some of the counterpoints to be false arguments: Non Sequitors, Post Hoc Ergo Propter Hoc, etc. which leaves Lukeβs proposal still strongly logical and justified without strong counter arguments.
That makes 2 of us Delta Mike. I donβt wear the developer hat so I only understand it on the surface level. It sounds like Luke has a few answers that no-one is talking about so it must be political.
run Bitcoin knots. that's s it
Knots, Datum and mine on Ocean!
The serious people moved on to Monero a while ago.
The biggest problem on bitcoin is mining that is centralized. Everything else sounds like noise
The first thing I ask myself is qui bono? Who benefits? In this case is it the node runners (decentralized) or a group that wants control?
Centralization creeps while we fiddle with filters. Wake up before Bitcoin's freedom crumbles. βοΈ
All the core Devs are Bitcoin VC employees now
I don't know much about spam filters, but it look like it's only about mempool. Is possible for user to define spam filter in btc core? For example can i create script which not allow in my mempool inscriptions?