diff options
| author | fanquake <fanquake@gmail.com> | 2022-03-25 20:54:52 +0000 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2022-03-25 21:03:32 +0000 |
| commit | 6d5771ba07780ac67d5e30108ae6b860f3878e7d (patch) | |
| tree | 48f68655c9d6882e70e676eb3673e92e78b65c3a /src/wallet/fees.cpp | |
| parent | f66c827c2d7dcce2021a7913caf5f14dca37e35a (diff) | |
| parent | 9053f64fcbd26d87c26ae6b982d17756a6ea0896 (diff) | |
Merge bitcoin/bitcoin#24494: wallet: generate random change target for each tx for better privacy
9053f64fcbd26d87c26ae6b982d17756a6ea0896 [doc] release notes for random change target (glozow)
46f2fed6c5e0fa623bfeabf61ba4811d5cf8f47c [wallet] remove MIN_CHANGE (glozow)
a44236addd01cff4e4d751e0f379d399fbfc8eae [wallet] randomly generate change targets (glozow)
1e52e6bd0a8888efb4ed247d74ec7ca9dfc2e002 refactor coin selection for parameterizable change target (glozow)
Pull request description:
Closes #24458 - the wallet always chooses 1 million sats as its change target, making it easier to fingerprint transactions created by the Core wallet. Instead of using a fixed value, choose one randomly each time (within a range). Using 50ksat (around $20) as the lower bound and `min(1 million sat, 2 * average payment value)` as the upper bound.
RFC: If the payment is <25ksat, this doesn't work, so we're using the range (payment amount, 50ksat) instead.
ACKs for top commit:
achow101:
ACK 9053f64fcbd26d87c26ae6b982d17756a6ea0896
Xekyo:
reACK 9053f64fcbd26d87c26ae6b982d17756a6ea0896
Tree-SHA512: 45ce5d064697065549473347648e29935733f3deffc71a6ab995449431f60302d1f9911a0994dfdb960b48c48b5d8859f168b396ff2a62db67d535a7db041d35
Diffstat (limited to 'src/wallet/fees.cpp')
0 files changed, 0 insertions, 0 deletions