You’ll never believe this horrendous non-monetary spam someone permanently stored on bitcoin…
…a dozen years ago.

You’ll never believe this horrendous non-monetary spam someone permanently stored on bitcoin…
…a dozen years ago.

😂
The icing on the cake? Look at the mining pool.
Anyone remember what Luke's pool was back in the day before nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze was launched?
That's right... Eligius.
Adam Back pointed that out. It was hilarious.
Quite hilarious.
And I say that as someone who mines with OCEAN, running Knots and DATUM with filters on my mempool.
Ah, fuck. Send my zap back!
Just kidding, what you want to run is your choice.
I primarily went that direction because I believe allowing individual miners to create their own mining templates while still being able to participate in reward splits is a fantastic way to decentralize mining.
I do generally agree with keeping a default OP_RETURN limit, with the ability for node runners to change or remove it if they like, though. In short, node runners should choose what transactions they want to relay, and miners should choose what transactions they want to include in a block.
Bitcoin is resilient because there are enough people making their own choices about these things that your transaction WILL eventually make it into a block.
😅🤣
Good thing it’s easier to relay now and you don’t even have to overpay (x693 in your example) for non monetary data
Was it you?