| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \
| | |
| | |
| | | |
ad4649ac Enable verifying wallet password with having to load wallet. (m2049r)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
c97d1bd3 wallet: return unlock_time in get_transfers (moneromooo-monero)
|
| | |/
| |
| |
| | |
also show it in simplewallet's show_transfer
|
| |/
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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)
|
| |
|
|
|
| |
Reviewed and squashed. Open/Create is only allowed if no walletfile
was specified at startup.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| | |
350e99ae wallet2: cache which pool txes were scanned already (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
This massively speeds up the wallet updating the pool on mainnet,
where the tx backlog is more than 500 txes.
|
| |/
|
|
|
|
|
| |
Asking for a full histogram from a remote node (since it's
untrusted) is pretty slow, and spams the remote node, so
we replace it by only adding a second input if we have rct
ones, which are for all intents and purposes always mixable.
|
| |
|
|
|
|
|
|
|
|
| |
Minimum mixin 4 and enforced ringct is moved from v5 to v6.
v5 is now used for an increased minimum block size (from 60000
to 300000) to cater for larger typical/minimum transaction size.
The fee algorithm is also changed to decrease the base per kB
fee, and add a cheap tier for those transactions which we do
not care if they get delayed (or even included in a block).
|
| |\
| |
| |
| | |
4b48565c wallet: add password command (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
Also tweak wallet2 password code to verify password without
saying it's a new wallet, because it's assuming things.
|
| |/ |
|
| |\
| |
| |
| | |
2c468dd4 allow user I/O in millinero, micronero, nanonero, piconero (moneromooo-monero)
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
ce7fcbb4 Add server auth to monerod, and client auth to wallet-cli and wallet-rpc (Lee Clagett)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
bceaf4b7 wallet2: fix transactions not considering rct inputs (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
I broke this very recently in 2bf029be172a47ace8134143e1320fdb10d3ea44
and didn't notice in time
|
| |/ |
|
| |\
| |
| |
| | |
f97526e6 simplewallet: option to always ask password for any crytical operations (kenshi84)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
c02e1cb9 Updates to epee HTTP client code - http_simple_client now uses std::chrono for timeouts - http_simple_client accepts timeouts per connect / invoke call - shortened names of epee http invoke functions - invoke command functions only take relative path, connection is not automatically performed (Lee Clagett)
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
- http_simple_client now uses std::chrono for timeouts
- http_simple_client accepts timeouts per connect / invoke call
- shortened names of epee http invoke functions
- invoke command functions only take relative path, connection
is not automatically performed
|
| |/ |
|
| |
|
|
|
| |
Mostly getinfo and get_hard_fork_info, which are called
pretty often. This speeds up transfers as a bonus.
|
| |
|
|
|
|
|
|
| |
This avoids indirectly leaking the real output to the daemon,
and is faster.
This will still happen for more complex cases, especially
when cancelling a tx and "re-rolling" it.
|
| |\
| |
| |
| | |
16b8b66a specify restore height by YYYY-MM-DD format (kenshi84)
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the epee and data_loggers logging systems with
a single one, and also adds filename:line and explicit severity
levels. Categories may be defined, and logging severity set
by category (or set of categories). epee style 0-4 log level
maps to a sensible severity configuration. Log files now also
rotate when reaching 100 MB.
To select which logs to output, use the MONERO_LOGS environment
variable, with a comma separated list of categories (globs are
supported), with their requested severity level after a colon.
If a log matches more than one such setting, the last one in
the configuration string applies. A few examples:
This one is (mostly) silent, only outputting fatal errors:
MONERO_LOGS=*:FATAL
This one is very verbose:
MONERO_LOGS=*:TRACE
This one is totally silent (logwise):
MONERO_LOGS=""
This one outputs all errors and warnings, except for the
"verify" category, which prints just fatal errors (the verify
category is used for logs about incoming transactions and
blocks, and it is expected that some/many will fail to verify,
hence we don't want the spam):
MONERO_LOGS=*:WARNING,verify:FATAL
Log levels are, in decreasing order of priority:
FATAL, ERROR, WARNING, INFO, DEBUG, TRACE
Subcategories may be added using prefixes and globs. This
example will output net.p2p logs at the TRACE level, but all
other net* logs only at INFO:
MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE
Logs which are intended for the user (which Monero was using
a lot through epee, but really isn't a nice way to go things)
should use the "global" category. There are a few helper macros
for using this category, eg: MGINFO("this shows up by default")
or MGINFO_RED("this is red"), to try to keep a similar look
and feel for now.
Existing epee log macros still exist, and map to the new log
levels, but since they're used as a "user facing" UI element
as much as a logging system, they often don't map well to log
severities (ie, a log level 0 log may be an error, or may be
something we want the user to see, such as an important info).
In those cases, I tried to use the new macros. In other cases,
I left the existing macros in. When modifying logs, it is
probably best to switch to the new macros with explicit levels.
The --log-level options and set_log commands now also accept
category settings, in addition to the epee style log levels.
|
| |\
| |
| |
| | |
d276a165 wallet2: use at least two rct inputs if possible (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
If we'd make a rct tx with just one input, we try to add
a second one to match the 2/2 ideal. This means more txes
use that template (and are thus using a larger anonymity
set), and it coalesces outputs "for free". We use the
smallest amount outputs in priority for this, so we can
"clean" the wallet at the same time.
|
| |/ |
|
| |\
| |
| |
| | |
a081b39c Move key image export/import functions to wallet2 (Jaquee)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
db56a03f Wallet2 + API: Callbacks for unconfirmed transfers (Jaquee)
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
0d3918e1 Wallet api: Update trustedDaemon when daemon is changed (Jaquee)
dbb838f4 GUI cold signing (Jaquee)
afb85a02 Wallet API: functions for supporting/creating view only wallets (Jaquee)
|
| | | |
| | |
| | |
| | | |
fix conflict
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
79b4e1f9 Cold signing: make sure short payment id isnt encrypted twice (Jaquee)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
5eed5b05 Wallet API: functions for supporting/creating view only wallets (Jaquee)
|
