Replying to Avatar RealJohnDoe

https://youtu.be/N03EumFv4kY?si=SJmFi0ZhQIIm2w_D

$boost

I support what #Knots and #Ocean are doing. If you're a #Bitcoin #loyalist you should run Knots and point your Miners at Ocean.

I'm not concerned about fees that are the results of a natural organic process of supply and demand. Unfortunately current bitcoin #fees are the result of market #manipulation and #fraud that has to end. Or at least be aggressively opposed.

I don't mind the expense and burden of blockchain bloat that's the result of legitimate Bitcoin #financial transactions. But not bloat that's the result of market manipulation and fraud.

I would also like to see a third leg of Bitcoin #code maintenance and development aggressively focused on Bitcoins virtue and purity. I think nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk is doing a good job. But he can't carry that torch alone. And shouldn't have to.

So that's my 2ยข

It would be helpful for node runners without hash-power to know what, if anything, they can do, to participate in this action.

My understanding is that switching to Knots or running the Ordisrespector patch will slow the propagation of 'Ordinals', at the P2P layer, but won't stop them eventually finding their way in to blocks.

Is this still a meaningful way to register ones opposition to Ordinals?

If the exploitation of witness data is patched, at a broad level, would those dumping jpegs into blocks pivot in some way, and would this be a more or less favourable situation vs where we currently stand?

tagging nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk

Reply to this note

Please Login to reply.

Discussion

I think anything we can #safely do will help, and should be done. Like the above.

If that's not enough we may have to up the stakes..๐Ÿ’€๐Ÿ˜ฉ๐Ÿฆ๐Ÿ˜‚๐Ÿงก๐Ÿ˜Š

I already run BitcoinKnots for the reasons you stated

The more people who deploy a fix, the more effective it becomes