diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-26 17:03:37 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-26 17:10:29 +0200 |
| commit | c948dc8f4285e27d8c0f3553d9d427b2a7b01b77 (patch) | |
| tree | 63217cda399decdd418c61daace45a3b9091f117 /src/qt | |
| parent | ec7dbaa37c233599e9fc68f8284ee85c1261652b (diff) | |
| parent | 2fb9c1e6681370478e24a19172ed6d78d95d50d3 (diff) | |
| download | bitcoin-c948dc8f4285e27d8c0f3553d9d427b2a7b01b77.tar.xz | |
Merge #12699: [wallet] Shuffle transaction inputs before signing
2fb9c1e shuffle selected coins before transaction finalization (Gregory Sanders)
Pull request description:
Currently inputs are ordered based on COutPoint ordering, which while doesn't leak additional internal wallet state, likely further fingerprints the wallet as a Core wallet to observers.
Note: This slightly changed behavior of `fundrawtransaction` in that the newly-appended inputs will now be shuffled rather than in outpoint-order. This does not break API compatibility.
Simple shuffling of the coins being returned will hopefully allow the wallet to blend in a bit more, in lieu of additional data to find what other wallets are doing, or another standard, ala @gmaxwell's suggested of ordering via scriptPubKey.
Tree-SHA512: 70689a6eccf9fa7fc6e3d884f2eba4b482446a1e6128beff7a98f446d0c60f7966c5a6c55e9b0b3d73a9b539ce54889a26c7efe78ab7f34af386d5e4f3fa6df2
Diffstat (limited to 'src/qt')
0 files changed, 0 insertions, 0 deletions