| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| | |
1834127c rpc: make get_output_distribution a non-restricted RPC (moneromooo-monero)
|
| | |
| |
| |
| | |
so that those nodes can still be used for sending transactions
|
| |\ \
| | |
| | |
| | |
| | | |
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.
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
5f664793 p2p: correct port number for seed nodes (stoffu)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
0098ed33 wallet2: fix for loading settings of key reuse mitigation (stoffu)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
57300491 wallet: catch exceptions dealing with ringdb and warn (moneromooo-monero)
|
| | |/ |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
8ea3c4d5 simplewallet: new --use-english-language-names flag (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
On some Windows systems, displaying language names in their own
languages freezes the display.
|
| |\ \
| | |
| | |
| | | |
1e393f4b wallet: make the segregation height settable (moneromooo-monero)
|
| | |/
| |
| |
| | |
via user setting first, then DNS TXT record, hardcoded fallback
|
| |/ |
|
| |\
| |
| |
| | |
9732a37e wallet_rpc_server: add sweep_unmixable as alias for sweep_dust (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
20a00266 blockchain: forbid bulletproof types before v8 (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | | |
They were already forbidden implicitely, but let's make that
explicit for robustness
|
| | |/
|/|
| |
| |
| |
| | |
lookahead in order to avoid
so looooong time of set-up when creating a HW based wallet.
|
| |\ \
| | |
| | |
| | | |
6f54c910 simplewallet: fix restore height prompt that got disabled by #3175 (stoffu)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
524cbdc1 blockchain: fix log message about per-kB fee (stoffu)
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | | |
833f9fcf show '<Not set>' for empty wallet description (cryptochangements34)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
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.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It scans for known spent outputs and stores their public keys
in a database which can then be read by the wallet, which can
then avoid using those as fake outs in new transactions.
Usage: monero-blockchain-blackball db1 db2...
This uses the shared database in ~/.shared-ringdb
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | |_|/
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | | |
c5024c5b simplewallet: add a warning when getting a daemon error in transfer (moneromooo-monero)
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
A malicious daemon (or MITM) could attempt to add spurious errors
so the wallet tries again, sending another set of fake outs.
|