From d982c11f87bfd5fa97b8456c9f98d9c7909a9c00 Mon Sep 17 00:00:00 2001 From: Chris Priest Date: Fri, 4 Dec 2015 14:37:51 -0800 Subject: [PATCH] fixed formatting --- bip-tx-ver2.mediawiki | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/bip-tx-ver2.mediawiki b/bip-tx-ver2.mediawiki index 101842d3..b0339547 100644 --- a/bip-tx-ver2.mediawiki +++ b/bip-tx-ver2.mediawiki @@ -63,16 +63,16 @@ 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 Version 2 Transactions. 1. **Full Node Coalescing validation** - 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 - 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. +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 +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 - 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, - then the UTXO has been spent and the transaction is invalid. +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, +then the UTXO has been spent and the transaction is invalid. 3. **Wallet** - 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 - a coalescing transaction. Wallets should not simply replace non-coalescing transactions - with coalescing transactions in all instances. +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 +with coalescing transactions in all instances.