bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

fixed bolding

Browse Source
This commit is contained in:
Chris Priest 2015-12-07 15:55:42 -08:00
parent bdd7c9ff76
commit e994fa264a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bip-coalesc-wildcard.mediawiki
View File

@ -62,17 +62,17 @@ in a block lower or equal to the block the wildcard input is confirmed into.
The bitcoin code needs to be modified in three places in order to handle Coalescing Transactions. The bitcoin code needs to be modified in three places in order to handle Coalescing Transactions.
1. **Full Node Coalescing validation** - When a full node receives a coalescing transaction, it has to 1. <b>Full Node Coalescing validation</b> - When a full node receives a coalescing transaction, it has to
aggregate the value of all the UTXOs in the blockchain older than the input aggregate the value of all the UTXOs in the blockchain older than the input
with the same scriptPubKey. If this value is greater than or equal to the with the same scriptPubKey. If this value is greater than or equal to the
amount of all outputs, then that coalescing transaction is valid and can be propagated. amount of all outputs, then that coalescing transaction is valid and can be propagated.
2. **Full Node Non-Coalescing validation** - When a non-coalescing transaction comes in, the code needs to be modified 2. <b>Full Node Non-Coalescing validation</b> - When a non-coalescing transaction comes in, the code needs to be modified
to check if each input has not been spent by a coalescing transaction. If there exist any to check if each input has not been spent by a coalescing transaction. If there exist any
coalescing transaction in the blockchain with the same scriptPubKey found in a block *after* that input, coalescing transaction in the blockchain with the same scriptPubKey found in a block *after* that input,
then the UTXO has been spent and the transaction is invalid. then the UTXO has been spent and the transaction is invalid.
3. **Wallet** - The user facing wallet portion of the reference client should notify 3. <b>Wallet</b> - The user facing wallet portion of the reference client should notify
the user when their wallet contains many UTXOs that qualify it to benefit from the user when their wallet contains many UTXOs that qualify it to benefit from
a coalescing transaction. Wallets should not simply replace non-coalescing transactions a coalescing transaction. Wallets should not simply replace non-coalescing transactions
with coalescing transactions in all instances. with coalescing transactions in all instances.