diff options
| author | Daniel Cousens <github@dcousens.com> | 2015-08-21 08:52:18 +1000 |
|---|---|---|
| committer | Daniel Cousens <github@dcousens.com> | 2015-08-21 09:10:00 +1000 |
| commit | c351ae0b9f518709fdd540573c30206696078f0b (patch) | |
| tree | 9f2b992524119f1e0b808f2d5b56555d41d9f950 | |
| parent | 342058602eb7737ceeb098d07eb9237d5e5fc65a (diff) | |
| download | bips-c351ae0b9f518709fdd540573c30206696078f0b.tar.xz | |
remove mention of information typically found in wallets
| -rw-r--r-- | bip-0069.mediawiki | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/bip-0069.mediawiki b/bip-0069.mediawiki index 43d25ee..5a20389 100644 --- a/bip-0069.mediawiki +++ b/bip-0069.mediawiki @@ -96,8 +96,6 @@ Previous transaction hashes (in their little-endian, byte-array form) are to be In the event of two matching transaction hashes, the respective previous output indices will be compared by their integer value, in ascending order. If the previous output indices match, the inputs are considered equal. -Because the hash of previous transactions and output indices must be included in a signed transaction, wallet clients capable of signing transactions will necessarily have access to this data. - Transaction malleability will not negatively impact the correctness of this process. Even if a wallet client follows this process using unconfirmed UTXOs as inputs and an attacker changes modifies the blockchain’s record of the hash of the previous transaction, the wallet client will include the invalidated previous transaction hash in its input data, and will still correctly sort with respect to that invalidated hash. |