| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
| |
When additional keys was needed, the TX scan failed because the
derivation data was always recomputed with the main tx_key and not
the corresponding additional one.
Moreover this patch avoid perf decreasing when not using HW device.
|
| |\
| |
| |
| |
| | |
73951cbd wallet2: request transactions in slices when scanning for known rings (moneromooo-monero)
25fe67e4 rpc: allow getting pruned blocks from gettransactions (moneromooo-monero)
|
| | |
| |
| |
| | |
This avoid massive memory consumption for huge wallets
|
| | |
| |
| |
| |
| |
| |
| |
| | |
and get them pruned in find_and_save_rings, since it does not need
the pruned data in the first place.
Also set decode_to_json to false where missing, we don't need this
either.
|
| |\ \
| | |
| | |
| | | |
24acb66e wallet2: fix misc issues when the ringdb can't be initialized (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
0b26c4d5 wallet2: move segregation height to v7 (moneromooo-monero)
|
| | | |/
| |/|
| | |
| | | |
since people seem to really want to use things the wrong way.
|
| |\ \ \
| | | |
| | | |
| | | | |
eecfb57d wallet: warn if not using the default ring size (moneromooo-monero)
|
| | |/ / |
|
| |\ \ \
| |_|/
|/| |
| | | |
1e0958c0 wallet: fix default mixin (4 -> 6) (sneurlax)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
11c933e1 fix lambda compile error on openbsd (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
c77d2bfa Add the possibility to export private view key for fast scan. (cslashm)
100b7bc1 Change mutex lock model to avoid dead lock and ensure locks are always released. (cslashm)
641dfc99 Automatic height setup when creating/restoring hw device. (cslashm)
|
| | |/
| |
| |
| |
| |
| | |
On client startup the device asks for authorization to export the private view key.
If user agree, the client hold the private view key allowing a fast blockchain scan.
If the user does not agree, the blockchain scan is fully done via the device.
|
| |\ \
| | |
| | |
| | |
| | | |
eaa8bfe7 wallet2: set from_height of GET_OUTPUT_DISTRIBUTION correctly The previous expression (stoffu)
0a619f78 wallet2: enable the mitigation only after the fork height (stoffu)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The previous expression
req_t.from_height = X ? Y >= Z : 0;
forces the parameter to take the value of either 0 or 1.
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
0098ed33 wallet2: fix for loading settings of key reuse mitigation (stoffu)
|
| | |/ |
|
| |/ |
|
| |
|
|
| |
via user setting first, then DNS TXT record, hardcoded fallback
|
| |\
| |
| |
| | |
9732a37e wallet_rpc_server: add sweep_unmixable as alias for sweep_dust (moneromooo-monero)
|
| | | |
|
| |/
|
|
|
|
| |
lookahead in order to avoid
so looooong time of set-up when creating a HW based wallet.
|
| |\
| |
| |
| | |
57c0b1ed Fix typos in various files (Dimitris Apostolou)
|
| | | |
|
| | |
| |
| |
| |
| | |
It can now take a txid (to display rings for all its inputs),
and will print rings in a format that set_ring understands
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This will avoid careless forkers polluting the shared database
even if they make their own chain. They'll then automatically
start using another subdb, and any key-reusing fork of those
forks will reuse their subdbs.
|
| | |
| |
| |
| |
| | |
This is so one can set rings for spent key images in case the
attackers don't merge the ring matching patch set.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| | |
| |
| |
| | |
calls to wallet2
|
| |/
|
|
| |
invoke_http_json_rpc("/json_rpc",methodname,...) to reduce boilerplate
|
| |\
| |
| |
| | |
c577abab wallet: fix auto low priority so that it takes effect only when saved default is 0 (stoffu)
|
| | |
| |
| |
| | |
default is 0
|
| |\ \
| | |
| | |
| | | |
1d39b265 wallet2: fix use_fork_rules() when querying version that is defined but not enabled yet (stoffu)
|
| | |/
| |
| |
| | |
enabled yet
|
| |\ \
| | |
| | |
| | | |
9abeff59 wallet2: handle no blocks returned in refresh to mean no new blocks (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
This is not a possible return from the daemon, but I want this in
now so all wallets handle this when the daemon starts doing so.
|
| |\ \
| | |
| | |
| | | |
ec41006c node_rpc_proxy: fix target height caching (moneromooo-monero)
|