This is a difficult conversation. I disagree with the decision to merge the Bitcoin Core pull request that removes OP_RETURN limits, especially given the ongoing controversy around it. Fortunately, I have options. I can choose not to upgrade or migrate elsewhere, such as to nostr:nprofile1qqsg3mj8tuxhxvy5w0qt9altpgcrqttdfxg9glvsdfhkpa3plcxfudgpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctckum9s8.
I will wait and will not update my core. Did not invest my money into my node hardware to support useless storage capacity. Btc nodes are there to validate the blockchain, all Node runners are doing this to support the transaction network, not to save spam on their block chain copy.
Bitcoin knots, OK, but isn't there only one developer involved?
That's why there's a discussion. The spam will be there either way. Running Knots won't practically change that BUT it might show a strong signal that we oppose the decision.
This has no bearing on your nodes storage capacity...
One developer. Who's keys have been breached in the past and who doesn't even hold their own keys anymore because of it.
