Replying to Avatar Jerome Powell 21iQ 40TPW

They could work together. Luke submitted a PR to add the same inscriptions hack fix that Knots uses. Instead of merging the fix, they changed the definition of datacarriersize to turn it from a bug to a feature. Their words and actions made it clear they support spam on the blockchain. This makes sense considering they are financially incentivized by Citrea, Taproot Wizards, etc.

They claim it's impossible to stop, and filters will have to be updated daily from a centralized server. The filter is simple, look for instructions in OP_RETURN that are being abused to embed data in code. It doesn't need to be updated daily. If all nodes were doing this (currently only Knots) and running sane default size limits (all current nodes except LibreRelay) the only way around would be miners using tricks like Slipstream. Core's argument ignores the fact that Slipstream and all sane miners have Terms of Service that prohibit illegal and questionable data submissions. This fixes 99.99% of the problem. It also sends a message to the companies building inscriptions garbage on Bitcoin to go do it on Ethereum, Solana or any other shitcoin.

#Enshitcoinification

Running #Knots

#MBDA
Avatar
mike 3mo ago

See, that's sensible talk. We need more of this.

Yes, most of the time, in most arguments, both sides agree more than they disagree. In battle, opponents choose to focus on the small differences, not the massive similarities.

Reply to this note

Please Login to reply.

Discussion

Avatar
Jerome Powell 21iQ 40TPW 3mo ago

It's unfortunate that the current Core regime has decided to ignore Luke's patch, call the bug a feature, ban folks like Mechanic, and launch a campaign of personal attacks against them. I believe Luke and Mechanic are acting in good faith, for the benefit of Bitcoin. I don't see that from Core. I see them acting for the benefit of their employers. Fiat financial incentives strike again.

I would like to see more decentralization. btcd and libbitcoin should be used more. Not the current "one node implementation to rule them all."

#Enshitcoinification

Running #Knots

#MBDA

Avatar
mike 3mo ago

I've stopped listening to the discussion because it's descended into name calling, but I wrote my reasons for running knots here, and it's nothing to do with either sides arguments:

nostr:naddr1qvzqqqr4gupzp6pmv65w6tfhcp73404xuxcqpg24f8rf2z86f3v824td22c9ymptqqxnzde4xuergvfjx5urwvehyldpv2