> > > Limiting the maximum size of the scriptPubKey of a transaction to 67 > bytes. > > This leave no room to deal with broken hashing algorithms and very little > future upgradability for hooks. > Can I ask for an example of such hooks for which room for "future upgradability" may be needed, please? I am not familiar with the subject and would like to learn more about it in order to evaluate the argument.
I disagree with the premise that larger maximum size of scriptPubKey is necessary for dealing with "broken hashing algorithms". Besides, I would suggest YAGNI principle. -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAMHHROzPZwh2boUW_cgMZZUVm5hK%2BSi0OHWLMQRL8a720EsMOw%40mail.gmail.com.
