it was a good idea. however the implementation you could say is too naive.
Discussion
they could have just added a new P2PKH schnorr signature transaction type. it was on the table back then, i remember ranting about it one time after reading up on the options that were being discussed.
instead we have witness discount and a bloated scripting signature algorithm that leaks the spending keys immediately instead of only at the moment of spend. and why, is my question, does taproot not have a limit on push data size?
i remember also the hype around pushing people to roll out taproot and once it hit like 10% of nodes using it the ordinals arrived.
next time additions to the consensus protocol are being discussed i'm gonna sniff it very closely
discussed by whom?
"they could have just added a new P2PKH schnorr signature transaction type"
something like that could be coming with bip-360.
"does taproot not have a limit on push data size"
ofc it has. 520 bytes per op, same as elsewhere.