pull down to refresh

I saw some buzz about this on X and even skimmed the repo, but have not had the time to go in deep.
The author's Github account was created a day prior to its posting on the mailinglist. The BIP was assigned BIP-Number 444 by Dashjr shortly after publication. The BIP has since been marked as "too heated" and consequently locked by Core developers, limiting the discussion to contributors.
The softfork proposal aims to invalidate scriptPubKeys exceeding 34 bytes and OP_Return to 83 bytes, invalidate certain OP_PUSHDATA with payloads larger than 256 bytes, invalidate certain undefined witness (or Tapleaf) versions and witness stacks with a Taproot annex, invalidate taproot control blocks larger than 257 bytes, invalidate tapscripts including OP_SUCCESS opcodes anywhere, and invalidate tapscripts executing the OP_IF or OP_NOTIF instruction.
442 sats \ 0 replies \ @BeeRye 4h
this is an utterly bat shit proposal, regardless of perceived merit or moral high ground.
reply
Genuinely can't understand why anyone is even entertaining Luke and his proposals. I suppose the fudsters, news outlets, influencers and anti-Bitcoin crowd need to play off something? I don't know.
Soft fork? No thanks. I'll hard pass on this.
reply
sigh Why does everything just spiral out these days? What concrete problem does this actually solve?
reply