Bitcoin Mechanic's avatar
Bitcoin Mechanic
npub1wnlu...n3wr
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
Spam filters mean there will be less spam. If you're worried about side effects like centralization of mining or UTXO set bloat then let me know when you're ready to take those problems seriously instead of LARPing about it and nuking OP RETURN limits. UTXO bloat and mining centralization are *serious issues* in Bitcoin. You don't get to do absolutely nothing about them for years then invoke them when coming up for convenient excuses for killing datacarriersize. Mining *is* centralized. There's no amount of bending over we can do relaying the stupidest trash possible around the network appeasing miners and scammers that can roll back the tide there just in the hopes that MARA becomes less motivated to maintain Slipstream. Where have the serious people gone?
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
Core have given up trying to deny users the ability to configure datacarriersize - definitely stepping back from the ledge so that's progress. What remains is a new default that will be 2,500x the size of what it is currently. Remains ridiculous, sorry. Core nodes should not - by default - cause users to relay more non-monetary activity around the network than necessary as it is obviously not in their interest. 40 bytes - the old default - was reasonable. This allowed side chains and hashes of however much data you wanted. 80 bytes was an unnecessary compromise. Changing it to 100,000 bytes by default which is "all" the latest PR does is reckless. The excuse that "at that size, the inscriptions hack is cheaper anyway so who cares" is not valid. The solution is to implement the fully functional filter that makes life harder and more expensive for inscribers - not blow out OP RETURN limits which provides an easier, if more expensive method of doing what the inscribers are doing. Fix the filters. Stop trying to play reverse whack-a-mole appeasing spammers constantly pushing for changes to Bitcoin.
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
Filters = Node sovereignty No filters = Help miners out with their side-gig
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
You do not need a CoreApprovedMempool™ to use Bitcoin. Reject this embarrassing psyop.
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
Bitcoin is amazing. So many celebrate what it does. So few understand that what makes it great is what it *doesn't* do.
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
Apologies for lack of op return war 2 content on here. Happy to start something off here if anyone has questions.
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
It's YOUR mempool. Peter Todd doesn't get to tell you what goes in it. Miners get to tell you what goes in the blocks in your local copy of the blockchain *if* they meet a massive PoW requirement that fits within consensus rules. But "you are not allowed control over what goes into your mempool anymore" As I said yesterday, it's over if this gets merged and it looks like Core are ignoring all the push back and accelerating it. image
Bitcoin Mechanic's avatar
GrassFedBitcoin 9 months ago
He attacks Bitcoin This motivates a major change to Bitcoin In the resulting discussion on github, he approves of this change (that is motivated by his attack) If you point out this conflict of interest - no matter how politely - you will be banned. @ODELL hope you're paying attention to all this