You could advocate for preventing easier spam on Bitcoin — but instead, you’re advocating a change that enables it further. How about leaving it alone? You’re proposing a major change, so the burden of proof is on you. We’re not obligated to follow, and we won’t.

Reply to this note

Please Login to reply.

Discussion

Leaving it alone incentivizes WORSE spam - flooding UTXO set!

Leaving the limit alone I mean. I’m not advocating ossification. I’m advocating a conservative approach when it comes to the changing the Bitcoin code.

Not really, the limit is actively harmful to bitcoin.

Why would the spam stop when it is not left alone?

The pull request links to a mailinglist post that explains all of this. You're not required to read it, but this "burden of proof" has been more than bet. On the flip side, those who oppose the pull request have not raised a single technically valid argument. And rather than just running Knots, many of them choose to harass developers and frustrate the Github repo.

* met

This is survivorship bias that valid arguments must only exist in their domain where they have the power to censor.

How convenient that you don't have to read anything!

Yes where I have a voice too.

Removing this limitation to enable BitVM or Citrea’s bridge doesn’t count as “proof.” As a node runner, I refuse to go along with changes that risk corrupting Bitcoin Core.

It’s arrogant to assume all risks have been accounted for. Just look at how Taproot unintentionally enabled spam via Casey Rodarmor’s Ordinals — a scenario developers didn’t foresee. That alone should be a cautionary tale.

The so-called “proof” in the mailing list isn’t convincing, and I’m far more concerned about the unintended consequences that often follow well-meaning but poorly considered changes.

Its the opposite. You suggested censoring people which is a form of harassment - first screenshot.

People gave you numerous technical problems with this PR and you were not able to give appropriate argument of why it will be good for Bitcoin network - second screenshot (and there are many more technical comments in the pr discussion although many were silenced like the Bitcoin Mechanic)

Would be interesting to see a response to this nostr:nprofile1qqsgdp0taan9xwxadyc79nxl8svanu895yr8eyv0ytnss8p9tru047qprpmhxue69uhkummnw3ezuumswfhhvmm0wd6zumnvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsqejfhn?

If you want to know why this pull request is very bad for Bitcoin you can watch the Bitcoin Mechanic video who was banned from the GitHub discussion for pointing out that sharing a conflict of interest is not against the rules of the discussion.

https://www.youtube.com/watch?v=15biQH1H140

> You suggested censoring people which is a form of harassment

It's complete nonsense and I don't have time to engage bad faith actors like "BitcoinIsFuture".

It was already multiple times on that pull request that conceptual discussion needs to happen on the mailinglist. Yet people ignore that instruction. And as I predicted, they kept doing so.

When people break into your office and start screaming at staff, sending them away is not "censorship".

* already stated

"Bad faith actor"? Look in the mirror. Clown🤡