mirror of
https://github.com/bitcoin/bips.git
synced 2025-01-18 05:12:47 +01:00
added more stuff
This commit is contained in:
parent
bd5e1ead70
commit
a5093f1c4a
@ -15,18 +15,21 @@ version 1 transactions.
|
||||
==Motivation==
|
||||
|
||||
Version 1 Bitcoin Transactions have one large inefficiency: When you want to spend
|
||||
from multiple inputs with the exact same scriptPubKey, you have to list the same
|
||||
signature multiple times. This bloats the transaction size and makes it expensive to spend
|
||||
from small value inputs.
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
==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".
|
||||
|
||||
A wildcard input beings the value of all inputs with the exact same scriptPubKey
|
||||
A wildcard input beings the value of all inputs with the exact same scriptSig
|
||||
in a block lower or equal to the block the wildcard input is confirmed into.
|
||||
|
Loading…
Reference in New Issue
Block a user