Bitcoin Core devs have been co-opted by unethical bullshit. I'm running knots already on my full node. Consider doing that too. Arbitrary data below 83 bytes is fine by me, though my settings are at 42 to prevent Ordinals. Any more than that and I think you should be paying significantly more bitcoin to get it done.
Bitcoin Core Going Rogue?
https://blossom.primal.net/84a48874e563ed3373810b6b6a4ed763cd3d64b982d6b1ac3b6e46fa24e924c8.mp4
Discussion
I'll keep running core because I believe it's a non issue.
If they don't let you pick OP_RETURN limits at all, I think that's a significant issue. Of the core instances I've got, I'm not gonna update them to something including this pull request.
And who the fuck bans someone for legit discussion?
If anyone had bothered to actually look at the pr you would see it's open as we speak and the person banned was not just having legit discussion. You should probably verify more and trust less.
You don't have to trust what I'm saying here. I'm short on time and trying to have a discussion about it.
If this PR goes through, you can still set a limit on OP_RETURN data and you would still be in concensous.
While using the updated version of Core with the PR? It sounded like they're removing it completely. My Core nodes are using default settings for OP_RETURN
They are removing it but it can still be added in in a fork like knots and you can run that and be in concensous. The change just doesn't give everyone a fence by default and lets users pick their own fence if they feel it's necessary.
Yeah I know, I'm already doing that. I'm not worried about falling out of consensus. I'm trying to help everyone see the apparently intellectually dishonest shit the Core team seems to be doing and make sure they know they are enforcing the rules they want to enforce.