2015-11-30 16:40:31 -08:00
|
|
|
<pre>
|
|
|
|
|
BIP: 122
|
|
|
|
|
Title: Transaction Version 2 Specification (wildcard inputs)
|
|
|
|
|
Author: Chris Priest <cp368202@ohiou.edu>
|
|
|
|
|
Status: Draft
|
|
|
|
|
Type: Standards Track
|
|
|
|
|
Created: 2015-11-30
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
==Abstract==
|
|
|
|
|
|
|
|
|
|
This specification defines a new type of transaction that supplements (not replaces)
|
|
|
|
|
version 1 transactions.
|
|
|
|
|
|
|
|
|
|
==Motivation==
|
|
|
|
|
|
|
|
|
|
Version 1 Bitcoin Transactions have one large inefficiency: When you want to spend
|
2015-12-01 13:14:55 -08:00
|
|
|
from multiple inputs with the exact same scriptSig, you have to list each
|
|
|
|
|
input separately, along with the same signature multiple times.
|
|
|
|
|
This bloats the transaction size and makes it expensive to spend from small value inputs.
|
2015-11-30 16:40:31 -08:00
|
|
|
|
|
|
|
|
Because small value inputs are expensive to send, they remain in the UTXO pool
|
|
|
|
|
which full nodes have to keep around. It is believed that long term increase of the UTXO
|
|
|
|
|
set can have negative scaling consequences on the network.
|
|
|
|
|
|
2015-12-01 13:14:55 -08:00
|
|
|
If maximum blocksize is made to increase *slower* than the actual number of transactins bitcoin users are sending
|
|
|
|
|
to the network, this problem is projected to get worse.
|
|
|
|
|
|
2015-11-30 16:40:31 -08:00
|
|
|
==Specification==
|
|
|
|
|
|
|
|
|
|
A version 2 transaction is formulated the exact same way as a version 1 transaction
|
|
|
|
|
with one exception: each input is treated as a "wildcard input".
|
|
|
|
|
|
2015-12-01 13:14:55 -08:00
|
|
|
A wildcard input beings the value of all inputs with the exact same scriptSig
|
2015-11-30 16:40:31 -08:00
|
|
|
in a block lower or equal to the block the wildcard input is confirmed into.
|
