The OP of this mailing list post reads very much like #AIslop, but I commend the few people who've answered to give clear and reasoned answers. I link here to the final answer, which, yet again, explains the reasoning behind the recent core v30 changes. My guess is that many of the proponents of knots have not actually followed the discussions from the last few years that led to this decision. So, maybe, this provides some insights...
pull down to refresh
27 sats \ 0 replies \ @standardcrypto 7h
Russell O'Connor.
" If we cap the OP_RETURN outputs to 80 bytes and 1 per transaction, the folks using these protocols will simply have no choice but to instead place their data for publication into bare multisig outputs. This outcome would be objectively worse for everyone involved. The protocol users will have to pay someone higher fees. Everyone's UTXO sets will be bloated with these unspendable transactions, and, unlike with OP_RETURN, there will be no way to decide which bare multisigs are being used as a poor man's bulletin board, and which ones are legitimate"
everyone's UTXO sets will be bloated ??
untrue. Untrue!
#ReleaseTheFiles Luke!
🫵🏼🎄✖️⭕
@justin_shocknet
@ek
@Car
@theariard
Whatever is causing the delay, it is time to let bygones be bygones. Before the long game turns into the "never happening" game.
Luke's superor abilities as bitcoin developer and 5d chess player in the mempool policy chessboard buy him a lot of leeway. We get it luke. You have been with bitcoin from the start and you aren't going anywhere.
But it's time to #ReleaseTheFiles.
reply