| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
including expected transaction backlog at different priorities
|
| | |
|
| |\
| |
| |
| | |
74597bd1 wallet2: improve refresh height determination (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| | |
As reported by jaquee, the calculation could underflow for very
low heights.
Additionally, we now use the target height too.
|
| |\ \
| | |
| | |
| | | |
9707998a wallet2: clear some missing containers in clear() (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
b7d6ec83 simplewallet: add (out of sync) or (no daemon) markers in the prompt (moneromooo-monero)
fa23a500 wallet2: add a is_synced function (moneromooo-monero)
f1307bbd node_rpc_proxy: add a proxy for target height (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
ad4649ac Enable verifying wallet password with having to load wallet. (m2049r)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
67ce4910 wallet2: store testnet bool in keys file (Jaquee)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
c97d1bd3 wallet: return unlock_time in get_transfers (moneromooo-monero)
|
| | |/
| |
| |
| | |
also show it in simplewallet's show_transfer
|
| | | |
|
| |\ \
| | |
| | |
| | | |
0c57df97 wallet2: fix temporarily missing incoming tx when being mined (moneromooo-monero)
|
| | |/
| |
| |
| |
| |
| |
| | |
When scanning the txpool without having first updated the
blockchain, the tx would be seen as neither in the txpool
nor the chain, and removed, so it'd only reappear once the
chain is refreshed, and the tx seen in a block.
|
| |/ |
|
| |
|
|
|
| |
Use current time to estimate current height only if the daemon
cannot be queried.
|
| |
|
|
|
|
|
| |
If the refresh height is in the future, the current code will
loop till the actual height reaches this. Fix it by bailing out
if we receive only three hashes, which is what we set in the
call parameters.
|
| |
|
|
|
|
|
| |
The previous patch was based on a wrong premise (that the
daemon height was 0 because the daemon calling code wasn't
yet initialized). In fact, current height approximation
was not setup for testnet. Fix this.
|
| | |
|
| |\
| |
| |
| | |
6bcd3b2d fix get_upper_transaction rename (schnerchi)
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
89b2f306 tests: fix invalid key image test (moneromooo-monero)
a374a522 wallet2: check key image validity domain in import_key_images (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
e2529347 Correct spelling of 'get_upper_transaction_size_limit' (Nano Akron)
3029d0ef Remove the 1.25x multiplier in max transaction size in just the wallet (Nano Akron)
|
| | | | |
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
6cb1ad1f wallet fix: ensure iterator to be valid (stoffu)
|
| | |/ |
|
| |/
|
|
| |
The bump to minimum mixin 4 was moved from v5 to v6
|
| |
|
|
|
|
|
| |
It sweeps all outputs below the given threshold
This is available via the existing sweep_all RPC, by setting
amount_threshold the desired amount (in atomic units)
|
| |\
| |
| |
| |
| | |
a6d5bb75 wallet2: refer to triangular distribution for recent zone in comment (moneromooo-monero)
ac1aba90 wallet2: bias fake outs more towards recent outputs (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
It was wrongly refering to equiprobable distribution, which I think
I'd originally done, but forgot to update the comment after changing
to triangular
Reported by smooth on IRC
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Two recent papers quantified the real usage bias for the
real output in a ring being the true one, and shows that
the current biasing is much too weak.
While we wait for a better solution, we increase the ratio
of recent-to-total fake outputs, as well as decrease the
time window for recent outputs, so that half the fake outs
are selected within the last 1.8 day. Value plucked from
figure 10, page 11 of An Empirical Analysis of Linkability
in the Monero Blockchain, 2017, Miller et al.
This is also arbitrary, of course, but serves as a stopgap
till a better selection algorithm is chosen.
|
| |\ \
| | |
| | |
| | | |
7f4beaa4 wallet2: fix removal of wrong txes from unconfirmed_payments (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
unconfirmed_payments changed from having the txid as key to
the payment id, and this was not changed to match.
|
| |\ \
| | |
| | |
| | | |
a7d78dda wallet2: fix --generate-from-json in RPC mode (moneromooo-monero)
|
| | |/
| |
| |
| | |
The daemon address was initialized too late
|
| |\ \
| | |
| | |
| | | |
89d70756 wallet2: fix spurious output splitting when not merging destinations (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
10e137be wallet2: mention escaping/quoting --password in help string (moneromooo-monero)
|
| | |/ / |
|
| | |/
|/|
| |
| |
| | |
Reviewed and squashed. Open/Create is only allowed if no walletfile
was specified at startup.
|
| |/
|
|
|
|
| |
If using a large input and many destinations, the code would
generate as many outputs as it could using that input, even if
it would bring the resulting tx above the max tx size.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
With the change from the original transfer method to the new
algorithm, payments to the same destination were merged. It
seemed like a good idea, optimizing space. However, it is a
useful tool for people who want to split large outputs into
several smaller ones (ie, service providers making frequent
payments, and who do not like a large chunk of their balance
being locked for 10 blocks after each payment).
Default to off, which is a change from the previous behavior.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a single input is enough to satisfy a transfer, the code would
previously try to add a second input, to match the "canonical" makeup
of a transaction with two inputs and two outputs. This would cause
wallets to slowly merge outputs till all the monero ends up in a
single output, which causes trouble when making two transactions
one after the other, since change is locked for 10 blocks, and an
increasing portion of the remaining balance would end up locked on
each transaction.
There are two new settings (min-output-count and min-output-value)
which can control when to stop adding such unneeded second outputs.
The idea is that small "dust" outputs will still get added, but
larger ones will not.
Enable with, eg:
set min-output-count 10
set min-output-value 30
to avoid using an unneeded second output of 30 monero or more, if
there would be less than 10 such outputs left.
This does not invalidate any other reason why such outputs would
be used (ie, when they're really needed to satisfy a transfer, or
when randomly picked in the normal course of selection). This may
be improved in the future.
|
| |
|
|
| |
Includes a new RPC to get tx pool hashes fast.
|
| |\
| |
| |
| | |
350e99ae wallet2: cache which pool txes were scanned already (moneromooo-monero)
|
