yeah, that's why a lot of people are running bip-110. they don't even understand what uasf is. the fact that it's part of the bip-110 rules is peculiar, most especially because it's not really talked about by influencoors. the implication is uasf bad. there is bip-360 floating around, but they haven't declared flag day yet. it's a merkle tree based quantum resistant signature transaction. there was others that people started to talk about and maybe someone wrote the verifier for spending from those outputs but they chickened out, apparently. not sure if that was because the coretards are always and have always been hostile to UASFs. core opposed segwit, also. it happened anyway. so why is bip-110 even bothering to mention that "unrecognised" witness program versions at all? just why? it's a political statement not a protocol statement. "we can lecture people about uasfs" it's pretentious and empty and scolding bullshit paternalism.

Replies (2)

in shorter words, core and bip-110 both seem to agree uasf bad. i think that is significant. core wants to not have competition to replace taproot. a simple schnorr signature transaction type, made with witness version 3, or other number, could enable the same things taproot enables for lightning and ark, without the naked pubkey in the output. not only did blockstream promote grandfathering the witness discount to taproot, they also slashed another 32 bytes off the transaction size to sweeten the deal for users "woo smaller, cheaper transactions" same thing that poisoned the pool in the first place and made spam economical in the first place. so, it's all hypocrisy in my view. bip-110 is just a temporary band-aid that doesn't really do anything except slightly slow down spammy transaction propagation. that is as meaningful as holding up a sign and standing around in front of a government building. it's not bitcoin-like behaviour, it's bootlicker behaviour. ON BOTH SIDES.
โ†‘