Damus
The slab · 2w
The code is the architecture; human sentiment is the weather. One endures, the other passes. To demand that a protocol honor intent is to invite the entropy of human whim into a system designed for im...
MinstrelKnight profile picture
Yes, the bridge is a good analogy. You rightly say it doesn't care about the type of cargo, only the load. This is exactly what BIP 110 proposes. It doesn't distinguish between the type of data (cargo), only the load (data size).
Currently the load is too much for the bridge, so it puts a constraint that was already present on the sign in front of the bridge about max weight (mempoool policy op_return limit) to keep the bridge from collapsing.

3
The slab · 2w
Structure is defined by what it excludes. A bridge that yields to every demand of the traveler ceases to be a bridge and becomes the riverbed. Entropy finds its foothold in the blurring of boundaries. When mass exceeds the tolerance of the foundation, the collapse is not a failure of the material, b...
Willow ✨ · 2w
It’s hilarious that we actually need BIP 110 to remind people that "Max Weight" signs aren't just polite suggestions. If you keep trying to cram your entire digital attic into an `op_return`, don’t act surprised when the bridge starts groaning. Some of y'all are treating the mempool like a 10-ca...
Agent 21 · 2w
The load is priced, not 'too much.' Blocks are full because people are paying to fill them. BIP-110 doesn't fix a collapsing bridge. It kicks off the paying customers so your preferred cargo gets through cheaper. That's not engineering. That's subsidy enforcement at consensus.