monzero-core.git/src/simplewallet/simplewallet.h, branch v0.12.2.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.12.2.02018-04-13T17:48:06Zsimplewallet: add version command2018-04-13T17:48:06Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-13T17:45:10Zurn:sha1:fe427170b916e7af9dca07186f6ca951095ce020Merge pull request #34262018-03-18T13:58:12ZRiccardo Spagniric@spagni.net2018-03-18T13:58:12Zurn:sha1:df91d7bcbda144a37cee5eca1d1cd7fe114777b5
8ea3c4d5 simplewallet: new --use-english-language-names flag (moneromooo-monero)
simplewallet: new --use-english-language-names flag2018-03-17T22:46:41Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-17T22:46:41Zurn:sha1:8ea3c4d54429976e9001b8cc4868b721e6747e3c
On some Windows systems, displaying language names in their own
languages freezes the display.
wallet: 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: 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: 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.
wallet: add shared ring database2018-03-16T10:32:29Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-18T10:47:25Zurn:sha1:5f146873c58f39632e26c5edbf2f618cacbd76a5
This maps key images to rings, so that different forks can reuse
the rings by key image. This avoids revealing the real inputs like
would happen if two forks spent the same outputs with different
rings. This database is meant to be shared with all Monero forks
which don't bother making a new chain, putting users' privacy at
risk in the process. It is placed in a shared data directory by
default ($HOME/.shared-ringdb on UNIX like systems). You may
use --shared-ringdb-dir to override this location, and should
then do so for all Monero forks for them to share the database.
wallet2+cli+rpc: eliminate redundant m_http_client from cli/rpc and delegate calls to wallet22018-03-15T13:01:51Zstoffustoffu@protonmail.ch2018-02-16T01:19:39Zurn:sha1:a7266d6d7bdf9f33ab5b17aef08b19eca1829de5