diff options
| author | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2018-02-19 10:23:23 +0000 |
|---|---|---|
| committer | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2018-03-16 10:32:34 +0000 |
| commit | 18eaf194897cb8216c9c035871911e6ba099a179 (patch) | |
| tree | 5f239450512374bb1f4c4325da3128f611bf4abf /snap | |
| parent | wallet: add shared ring database (diff) | |
| download | monero-18eaf194897cb8216c9c035871911e6ba099a179.tar.xz | |
wallet: key reuse mitigation options
If a pre-fork output is spent on both Monero and attack chain,
any post-fork output can be deduced to be a fake output, thereby
decreasing the effective ring size.
The segregate-per-fork-outputs option, on by default, allows
selecting only pre-fork outputs in this case, so that the same
ring can be used when spending it on the other side, which does
not decrease the effective ring size.
This is intended to be SET when intending to spend Monero on the
attack fork, and to be UNSET if not intending to spend Monero
on the attack fork (since it leaks the fact that the output being
spent is pre-fork).
If the user is not certain yet whether they will spend pre-fork
outputs on a key reusing fork, the key-reuse-mitigation2 option
should be SET instead.
If you use this option and intend to spend Monero on both forks,
then spend real Monero first.
Diffstat (limited to 'snap')
0 files changed, 0 insertions, 0 deletions