| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
| |
It is similar in use to --restore-from-view-key, but also expects
a spend private key.
Requested by luigi1112, and useful to restore MyMonero wallets.
|
| |
|
|
|
| |
Some of it uses hardcoded height, which will need some thinking
for next (voted upon) fork.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
instead of a command line setting. It makes sense that is is
a long lived setting.
|
| |
|
|
|
|
|
|
| |
^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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
With backward compatibility
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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
|
| |
|
|
|
| |
It allows enabling the rescan_spent command only for trusted
daemon
|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
| |
The new save_watch_only saves a copy of the keys file without the
spend key. It can then be given away to be used as a normal keys
file, but with no spend ability.
|
| |
|
|
|
|
| |
Sends all the dust to your own wallet. May fail (if the fee required
is more than the dust total). May end up paying most of the dust in fees.
Unlocked dust total is now also displayed in "balance".
|
| | |
|
| | |
|
| |
|
|
|
| |
Add simple_wallet::set_variable method to provide top-level "set"
command and support "set seed language" command.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Source: cryptonotefoundation
|
| | |
|
| |
|
|
| |
not yet password protected
|
| | |
|
| |
|
|
|
|
|
|
| |
wallet RPC now uses wallet2::create_transactions and wallet2::commit_tx instead
of wallet2::transfer. This made it possible to add the RPC call /transfer_split, which
will split transactions automatically if they are too large. The old call to
/transfer will return an error stating to use /transfer_split if multiple
transactions are needed to fulfill the request.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
--generate-new-wallet and --wallet-file are now properly mutually-exclusive.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
