Re: Finally Bitcoin Devolpers planning to kill Ordinals and Inscription
When everyone knows what the limits are, people are free to transact. And yes, some people will inevitably find methods of exploiting or abusing those limits. But if those limits keep getting tighter, to try and catch out the ones exploiting it, you'll also catch innocent parties who are suddenly outside of a limit they were previously within.
In that case, limiting Taproot script size
remember the "promise" of taproot
'it wil look like a normal tx that only uses one signature length' pfft. promise broke from day one.
You forget about part where only certain TX can be aggregated/merged.
c. remove the blocksize miscount of 4mb (1mb base+3mb witness) cludge. so that any and all transactions get full utility of the full 4mb space
that was a huge thing to allow into bitcoin. you would think that such a huge thing would have been discussed alot and written up about why it was being done. with analysis about the potential repercussions of it. but nothing like that seemed to happen. so here we are. not knowing if they intended for it to be this way or not. but it is this way. kind of crazy.
a feature like that should have been heavily discussed and debated prior to being implemented though and I'm sure someone would have brought up the issue that a single transaction could then consume an entire bitcoin block. and who would think that was a good thing?
But with hard-fork frowned by majority of Bitcoin community, the choice at that time is either that or keep using bytes (which means no block size increase).