pull down to refresh

Make no mistake, this egregious power grab is exactly that. It is a move that undermines consensus and breaks from Bitcoin’s foundational principles.
Core has gone rogue. This IS an attack on Bitcoin. This IS inside job. Do not upgrade your node. If possible, switch to Knots or another implementation.
Hold the line.
At the end of the day, my power is limited. But together, we choose. We will not bend the knee. We are Bitcoin, not them.
This is a call to arms. The line in the sand has been drawn.
Choose your side.
Did you read the entire thread here? #971277 I thought the questions that were asked, and there were many, were extremely well answered and overall very neutral. Very professional. Great presentation. Great use of risk management on display.
No-one knows the future, and risk management is impossible to get 100% right... but honestly I find the appeals to emotion on the part of the 'filterers' to be less convincing.
Please see GMaxwell's comments here:
An excerpt:
@wizkid057 I've carefully read your messages as wells as the other messages from your colleagues at ocean and I have failed to find any clear explanation of the harm we could expect to experience from removing this limit.
It's all well and true that NFT/shitcoin stuff is bad, but there is no reason to expect that this should increase that activity: Anything that can be done with op_return can be done just as well (for the data embedder) with 'fake addresses'. And fake addresses are both far worse for Bitcoin due to bloating the utxo set and are essentially impossible to block. Moreover, parties that want to bypass this limit at scale and particularly for abusive purposes have an easy avenue to do so by directly handing large miners the transactions, which is now a reliable method for getting transactions mined that violate policy.
I've also found no counter to the benefits of removing the behavior: that at least some of the fake address traffic has indicated it will switch, that any discrepancy between what nodes relay and what miners mine hurts block propagation which advantages large miners at the expense of smaller miners, that direct-to-miner relationships also favor large operations over small, that an incomplete mempool reduces your ability to look at it and tell what price may will get your transactions in the next block, and that a fruitless game of wack-a-mole trying to block transactions creates a dangerously muddled message about the ability of Bitcoin participants to blacklist transactions/addresses such as those on state set blacklists. And of course, simpler code with fewer options and thus combinations of options to test.
reply
He also gave some very clear answers here https://bitcointalk.org/index.php?topic=5539943.0
reply
171 sats \ 2 replies \ @ek 6 May
yawn
How many did even run the latest version of Core?
This whole debate feels completely overblown to me, in a few months it might look like a big nothingburger.
reply
yawn indeed
reply
How many did even run the latest version of Core?
the more people start running nodes, the more might download the latest Bitcoin Core version from the repository, unsuspectingly. must make more memes about 28 and Knots.
reply
reply
this should be the top comment.
Darth, are you the author? or did you copy from somewhere?
Great, either way.
reply
No is not mine. Is from nostr, I just share it here because I find it interesting. I will FW the sats to who made it.
reply
30 sats \ 0 replies \ @OT 6 May
This makes conspiracies about Core being compromised more persuasive
reply
Core gone woke
reply