monzero-core.git/src/wallet/wallet2.h, branch crash-plMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=crash-pl2018-04-12T11:47:20ZMerge pull request #35342018-04-12T11:47:20ZRiccardo Spagniric@spagni.net2018-04-12T11:47:19Zurn:sha1:5d8439e310e1804c13dd380161494cfa46997e37
eecfb57d wallet: warn if not using the default ring size (moneromooo-monero)
wallet: warn if not using the default ring size2018-03-31T14:47:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-31T13:20:48Zurn:sha1:eecfb57df9aa4a78fb7c1b3c8072b1368654b433wallet: catch exceptions dealing with ringdb and warn2018-03-21T14:29:49Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-21T14:29:49Zurn:sha1:57300491781af47bdb58d9c8f9a82252564d35c6wallet: make the segregation height settable2018-03-17T14:56:31Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-13T19:38:52Zurn:sha1:1e393f4bb779cc5e108705109bc62362b8d243d5
via user setting first, then DNS TXT record, hardcoded fallback
Add command line option allowing to restrict the default sub-address lookahead in order to avoid2018-03-16T17:00:28Zstoffustoffu@protonmail.ch2018-03-16T04:11:45Zurn:sha1:b86f1e5dad3d5a9a07f3b6184802e5938afa57db
so looooong time of set-up when creating a HW based wallet.
wallet: more user friendly print_ring2018-03-16T12:07:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-14T19:13:55Zurn:sha1:eac3a11ed330faefa01685e98cf91e9ac1e31135
It can now take a txid (to display rings for all its inputs),
and will print rings in a format that set_ring understands
wallet: add a set_ring command2018-03-16T10:32:51Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-28T18:26:06Zurn:sha1:b09e5181cc7c24fc6cf13b4a43044833bd2763fa
This is so one can set rings for spent key images in case the
attackers don't merge the ring matching patch set.
wallet: make ringdb an object with database state2018-03-16T10:32:42Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-27T08:30:59Zurn:sha1:db10dd6d8329de92e212247a2eb101c773d4c3cdwallet: add an output blackball list to avoid using those in rings2018-03-16T10:32:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-25T19:20:07Zurn:sha1:d29ea0455a34c2d08c681dacdf809e7f7317d2b3wallet: key reuse mitigation options2018-03-16T10:32:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-19T10:23:23Zurn:sha1:18eaf194897cb8216c9c035871911e6ba099a179
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.