This is, again, a limitation of the code rather than a protocol problem
I see we agree. On this small point, at any rate.
I wonder who may have an incentive to code up an alternative implementation? Maybe somebody who already has millions of dollars tied up in capital equipment - someone whose continued profitability requires making any optimization allowed by the protocol...
Bitcoin is moving to Schnorr sigs. We need them not only to stop O(n^2) attacks, but also to enable tree signatures and fungibility, etc.
Why would anyone waste time trying to fix the obsolete Lamport scheme?
Perhaps the Unlimite_ crowd will decide to dig in their heels against Schnorr?
Oh wait, by blocking segwit they already have!
