whatever you want to call the default change in carrier data size from 83 to 100,000 that was the change in contention. it’s absurd to say it was “already blown out” else there would have been no need to change the default there are a lot of bad arguments on both sides. it’s been a pain working through them all looking for the best affirmative case for what I ought to do.

Replies (2)

Nuh's avatar
Nuh 4 months ago
You are pretending to be able to do anything... Doesn't make it true though.
Changing default relay policy to match consensus was meant to 1) undercut the fee market for out of band transaction submission to the biggest miners (as this was a valid existential threat “someday”) and 2) allow nodes to see the “real” mempool (so to speak, there technically is no such thing) to make estimating fees more reliable (valid but also probably premature too). IMHO, the only valid discussion points on ripping off the bandaid were ones regarding timing and communication…(the bandaid meaning including op_return size in the criteria for judging whether or not a transaction is “standard” and thus permitting non-specialized nodes to relay the tx). You’ll note that this move does not invite or condone embedding data on chain; being able to embed data via op_return isn’t guaranteed to even exist in the future. But the reality is removing op_return entirely would be totally possible, guaranteeing any data stored on chain would be non-prunable for all.