One potential optimization to compress bitcoin transaction measurement is avoiding repetition of redundant information between inputs.
As a consensus change, a brand new transaction sort may permit signing a listing of txid:vout pairs if all of them share the identical output script.
To select an excessive instance, there are 1.6 million outputs with script 1HckjUpRGcrrRAtFaaCAUaGjsPx9oYmLaZ. Spending one in all these P2PKH outputs prices 40+72 vBytes (prevOut + scriptSig) per enter. By aggregating the scriptSig throughout inputs, the transaction may omit 72 per enter and solely embrace it as soon as per transaction. When consolidating all these outputs, an optimization like this might save community information on the order of 115 MvBytes. (At a payment price of 10sat/b, this might translate into 11.5 BTC, which is about 80% of the combination worth of these outputs)
What are the trade-offs and hidden issues of this kind of optimization?
