-
@ Bitcoin Mechanic
2025-05-12 18:32:51
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.