In my view, the market kinda had sorted this out: For the most part, it seemed like node-runners didn't really care about the amount of their resources being used for dick pics, etc. - with the exception of a few spikes in network fees that have all but disappeared. They ran the default reference implementation without having to worry about specific settings all that much. All was well.

With Core v30 changing those default settings, it is not yet known what the consequences will be. Most node-runners - who weren't all that concerned about specific setting before - probably don't notice when they have been changed from one version to the next. If a consequence of these changes is a return to higher, possibly sustained, network fees, these changes will have had the effect of (at least temporarily) distorting that market that seemed to have already been sorted out.

Personally, I would be interested in exploring the possibility of a consensus change to hard limit all such arbitrary data back to what had previously been widely considered 'standard'. I am not so much interested in any 'emergency' fork that may start retroactively reorganizing any part of the blockchain based on someone's 🤷 subjective interpretation of the law of some indeterminate jurisdiction 🤷.

Reply to this note

Please Login to reply.

Discussion

No replies yet.