Ok, so you support Core. Tell me: domyou update to V30? And argument why uncap op_ return doesn't consern you?
Login to reply
Replies (2)
I haven’t updated, I am typically several releases behind mainly out of a conservative nature and laziness. Uncapped op return doesn’t concern me because in my mind the limits on transactions are economic and the over all block size of 4mb. I see no difference in a single large op return and 100s of small ones except that 100s of small ones cause more waste as it requires more block space for headers etc and that extra space can’t be pruned the way op return data can be. People throwing large transactions into op return and paying full freight is much better than using witness data to take those data loads.
Block space is clearly not highly demanded as evidenced by the long term trend of empty mempools. If bitcoin was seeing massive economic adoption we would have consistently full blocks and there really wouldn’t be room for spam.
My major issue with this whole thing is the narrative that bip-110 is required out of an emergency and that csam is a critical threat to Bitcoin. These are not arguments, they are threats and I will it be threatened into action.
As with many things in life, inaction can fuck things up badly in the future.
What is the incentive of bip-110 / knots, and what is the incentive of core? Who's decisions are potentially distorted by economic incentives other than the long term survival of the network? That's what bothers me.