| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Blockchain hashes and key images are flushed, and blocks are
pulled anew from the daemon.
The console command is shortened to match bc_height.
This should make it a lot easier on users who are currently
told to remove this particular cache file but keep the keys
one, etc, etc.
|
| | |
|
| |
|
|
|
| |
Displaying in-program commands with --help doesn't match daemon
behaviour (or make sense)
|
| |
|
|
| |
Typos, grammar, consistency. I don't claim to have gotten everything.
|
| |
|
|
|
| |
instead of a command line setting. It makes sense that is is
a long lived setting.
|
| |\
| |
| |
| | |
36a298c simplewallet: add tr markers in a few missing user visible strings (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
^C while in manual refresh will cancel the refresh, since that's
often an annoying thing to have to wait for. Also, a manual refresh
command will interrupt any running background refresh and take
over, rather than wait for the background refresh to be done, and
look to be hanging.
|
| |\ \
| | |
| | |
| | | |
66849ac simplewallet: swap colors in show_transfers (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
Green is now used for incoming transfers, and magenta for outgoing
transfers. This is consistent to the scheme used by other logging.
|
| |/
|
|
|
|
| |
The daemon will be polled every 90 seconds for new blocks.
It is enabled by default, and can be turned on/off with
set auto-refresh 1 and set auto-refresh 0 in the wallet.
|
| |
|
|
|
| |
Take the opportunity to add a no-coinbase case too, for even faster
sync when an address is known to never have mined to.
|
| |\
| |
| |
| |
| |
| |
| |
| | |
db1fb66 wallet: storing outgoing tx info now defaults to enabled (moneromooo-monero)
9156ba3 wallet: rename store-tx-keys to store-tx-info (moneromooo-monero)
b3d4d41 wallet: improve show_transfers (moneromooo-monero)
725ae4e wallet: use incoming blocks to keep track of payments too (moneromooo-monero)
00790a8 simplewallet: lessen display flicker confusion (moneromooo-monero)
|
| | |
| |
| |
| | |
With backward compatibility
|
| | |
| |
| |
| | |
More information is now saved and displayed
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Height seemed to be flying all over the place on a rescan here.
Logging to a file shows the heights are actually correct, and
this is some kind of screen refresh artifact. Flush after \r
and update less often to reduce this effect a lot.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
There are various locale related bugs in various versions of boost,
where exceptions are thrown in boost::filesystem APIs when the
current locale is not to boost's liking. It's not clear what "not
to boost's liking" means in detail, though "en" and "en_US.UTF-8"
are not to its liking.
Fix it by running a test function that's known to throw in such
a case, and resetting LANG and LC_ALL to C if an exception is
thrown. In simplewallet, the locale is queried before that so the
correct translations will still be used.
|
| |
|
|
|
| |
It's a user friendly display of incoming and outgoing transfers,
listed by height, within an optional height range.
|
| |
|
|
| |
The default default mixin is 4. It can now be changed per wallet.
|
| | |
|
| |
|
|
|
| |
It allows one to check the amount of monero sent to a particular
address in a particular transaction, given that transaction's tx key
|
| |
|
|
| |
because it leaks your standard address
|
| |\
| |
| |
| | |
df8a110 simplewallet: add a --trusted-daemon flag (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
It allows enabling the rescan_spent command only for trusted
daemon
|
| |/
|
|
| |
As recommended in MRL-0004
|
| |\
| |
| |
| | |
5dc53c2 wallet: use mutex protected random generation api (moneromooo-monero)
|
| | | |
|
| |/
|
|
| |
To enable storing tx keys in the (now encrypted) wallet cache.
|
| |
|
|
|
| |
They are also stored in the cache file, to be retrieved using
a new get_tx_key command.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Default to "simplewallet.log" in current directory when file path isn't
obtained from epee.
In this situation previously, it defaulted to the file name of ".log"
("" + ".log") in the current directory.
(Thanks to @sammy007 for reporting bug.)
An earlier version yet used "" + "/" + ".log" = "/.log", which resulted
in silently not logging in most cases, due to lack of permission.
Test:
PATH=$PATH:</path/to/simplewallet/folder> && simplewallet --wallet-file /dev/null
This results in epee not finding the executable's file path, so
simplewallet will now use a default log filename.
|
| |
|
|
|
|
|
| |
This obsoletes the need for a lengthy blockchain rescan when
a transaction doesn't end up in the chain after being accepted
by the daemon, or any other reason why the wallet's idea of
spent and unspent outputs gets out of sync from the blockchain's.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pros:
- smaller on the blockchain
- shorter integrated addresses
Cons:
- less sparseness
- less ability to embed actual information
The boolean argument to encrypt payment ids is now gone from the
RPC calls, since the decision is made based on the length of the
payment id passed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A payment ID may be encrypted using the tx secret key and the
receiver's public view key. The receiver can decrypt it with
the tx public key and the receiver's secret view key.
Using integrated addresses now cause the payment IDs to be
encrypted. Payment IDs used manually are not encrypted by default,
but can be encrypted using the new 'encrypt_payment_id' field
in the transfer and transfer_split RPC calls. It is not possible
to use an encrypted payment ID by specifying a manual simplewallet
transfer/transfer_new command, though this is just a limitation
due to input parsing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It should avoid a lot of the issues sending more than half the
wallet's contents due to change.
Actual output selection is still random. Changing this would
improve the matching of transaction amounts to output sizes,
but may have non obvious effects on blockchain analysis.
Mapped to the new transfer_new command in simplewallet, and
transfer uses the existing algorithm.
To use in RPC, add "new_algorithm: true" in the transfer_split
JSON command. It is not used in the transfer command.
|
| | |
|
| |
|
|
|
|
| |
boost doesn't support %zu for size_t, and the previous change
to %u could technically lose bits (though it would require splitting
a transfer into 4 billion transactions, which seems unlikely).
|
| |
|
|
|
| |
This can be useful if you want to be given a veto over the tx fee,
or if you want to see what a tx fee would be without actually sending.
|
| | |
|
| |
|
|
|
|
|
| |
The system is mostly the Qt system, but we don't use Qt to avoid
the dependencies.
See README.i18n for details.
|
| |
|
|
|
|
| |
The needed information is supplied via a triple:
--generate-from-view-key address:viewkey:filename
|
| |
|
|
| |
They do not make sense
|
| |\
| |
| |
| | |
fb20071 simplewallet: allow a different password for the watch-only wallet (moneromooo-monero)
|
| | | |
|
| | | |
|