[ad_1]
One attainable optimization to compress bitcoin transaction dimension is avoiding repetition of redundant knowledge between inputs.
As a consensus change, a brand new transaction sort might enable signing an inventory of txid:vout pairs if all of them share the identical output script.
To choose an excessive instance, there are 1.6 million outputs with script 1HckjUpRGcrrRAtFaaCAUaGjsPx9oYmLaZ. Spending considered one of these P2PKH outputs prices 40+72 vBytes (prevOut + scriptSig) per enter. By aggregating the scriptSig throughout inputs, the transaction might omit 72 per enter and solely embody it as soon as per transaction. When consolidating all these outputs, an optimization like this might save community knowledge on the order of 115 MvBytes. (At a price price of 10sat/b, this is able to 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?
[ad_2]
Supply hyperlink
