pull down to refresh
102 sats \ 5 replies \ @optimism 1h \ parent \ on: Undeprecate datacarrier PR rationale - @schmidty bitcoin
Everything landed okay-ish after the blocksize war so besides time nothing was wasted, except maybe the invention of LOT itself, which is imho an abomination. It's seen a lot of discussion and was at some point proposed for taproot activation, but we got ST in its place.
I do agree that this isn't a reason to not move forward with any decentralization though. And it's easy for anyone to use this fear against the current power that has vested in Core.
SegWit discount may still manifest itself as a much bigger problem than is understood today, and that was a result of compromise... Compromise being a dereliction of principles and "weak men creating hard times".
I'm not in the weeds enough to know the LOT history but I assume it's a similar story. These types of compromises only happen because of Core's positioning and the battlefield it's become as a result.
Without Core, no one has to compromise, it's a level field for ideas to compete on.
reply
If you're a pool, you can kill segwit discount today if you want to. You anyway need the witness data before you create your blocktemplate, so you can just calculate the inclusion fee as absolute per-byte. Fees aren't part of consensus. You can also enforce 1MB block space to include witness data. Your block template, your choice.
reply
But the centralized distribution of Core normalized it, where it wasn't before. Miners being rational market actors had the market rules changed on them by a politburo, one that leads the auto-downloaders.
Can't on the one hand worry about chaos by multiple distributions while ignoring the chaos caused by a universal one.
reply
We can do a little experiment - though it will take some time to code up - where we dump mempool, recalculate without segwit discount, and see what happens to transaction ordering. If there is more money in it for miners, especially with current fee regime, then I don't see any reason why they wouldn't want to patch.
reply
Possible, but trying to get the genie back in the bottle isn't something we want to rely on with future changes. The threshold for letting it out in the first place needs to be higher than a few salaried devs punching a clock having the keys just because they usurped a given GitHub repo.
reply