| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| |
| | |
b4eada9 wallet: make load_keys check types when loading JSON (moneromooo-monero)
3e55725 wallet: make the JSON reading type safe (moneromooo-monero)
f8d05f3 common: new json_util.h (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
24b3e90 Convey tx verification failure reasons to the RPC client (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows appropriate action to be taken, like displaying
the reason to the user.
Do just that in simplewallet, which should help a lot in
determining why users fail to send.
Also make it so a tx which is accepted but not relayed is
seen as a success rather than a failure.
|
| | |/
|/| |
|
| | |
| |
| |
| | |
Because we can.
|
| | |
| |
| |
| |
| |
| | |
This will be slower, though more private.
New trusted_daemon parameter to the matching RPC call, false by default.
|
| | |
| |
| |
| |
| |
| | |
With the change in mixin rules for v2, the "annoying" outputs are
slightly changed. There is high correlation between dust and
unmixable, but no equivalence.
|
| | |
| |
| |
| | |
It resulted in a tx being sent with too low a fee, and thus rejected.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It takes a filename containing JSON data to generate a wallet.
The following fields are valid:
version: integer, should be 1
filename: string, path/filename for the newly created wallet
scan_from_height: 64 bit unsigned integer, optional
password: string, optional
viewkey: string, hex representation
spendkey: string, hex representation
seed: string, optional, list of words separated by spaces
Either seed or private keys should be given. If using private
keys, the spend key may be omitted (the wallet will not be
able to spend, but will see incoming transactions).
If scan_from_height is given, blocks below this height will not
be checked for transactions as an optimization.
|
| |
|
|
|
|
| |
Ain't nobody got time for link/cmake skullduggery.
This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
|
| |
|
|
| |
Useful for debugging users' logs
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
After the fork, normal transfer functions called via RPC
use the minimum mixin 2 if 0 or 1 is requested. While the
incoming transaction may be valid (eg, it has an unmixable
and at most a mixable input), it is a simple way to make
sure RPC users can't get a seemingly random accept/reject
behavior if they don't update their requested mixin.
|
| |
|
|
| |
We will need it in the wallet RPC server
|
| |
|
|
| |
and all other associated IPC
|
| |
|
|
| |
Add support for short/integrated/encrypted IDs to get_payments RPC
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If it is, it points to reuse of a tx key, which isn't meant to happen.
If it does, a key image collision means that only one of those
outputs is spendable, so the wallet selects the larger amount,
unless that output was spent already.
This causes a discrepancy betewen reported received inputs and
payment total.
Since tx keys are 256 bits, this should never happen except if
done on purpose, or if a sender uses a bad PRNG.
|
| |
|
|
|
| |
This reverts commit 58f890652e86039e98dff2d48d217c9ea9e84eca, reversing
changes made to 39d73d2a27730e6a5844c259d81a0ed9d4ee3000.
|
| |\
| |
| |
| |
| | |
7fc6fa3 wallet: forbid dust altogether in output selection where appropriate (moneromooo-monero)
5e1a739 blockchain: log number of outputs available for a new tx (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
80882ac wallet: guard against exception in process_blocks (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
If an exception occurs, the thread needs to be joined, or it
will be deleted while still live, and terminate the process.
|
| |\ \
| | |
| | |
| | | |
2cf8b32 wallet: guard against exception in process_blocks (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
If an exception occurs, the thread needs to be joined, or it
will be deleted while still live, and terminate the process.
|
| |/
|
|
|
| |
When a transaction is not found in the pool anymore, it is marked
as failed, and displayed as such in show_transfers.
|
| |
|
|
|
| |
Some of it uses hardcoded height, which will need some thinking
for next (voted upon) fork.
|
| | |
|
| |
|
|
|
|
|
|
| |
The value will be different depending on whether we've reached
the first hard fork, which allows a larger size, or not.
This fixes transactions being rejected by the daemon on mainnet
where the first hard fork is not yet active.
|
| | |
|
| |\
| |
| |
| | |
5c67c48 wallet: don't forget to close the file after storing cache (moneromooo-monero)
|
| | |
| |
| |
| |
| | |
Also add some flags to open, as epee's save_string_to_file does,
to truncate file, etc.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |/
|
|
|
| |
This can happen when the daemon exits, which would also cause
the wallet to crash via unhandled exception
|
| | |
|
| |\
| |
| |
| | |
61befc2 wallet: store cache to file without unnecessary memory buffer (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| | |
Reported by saddam
|
| |/
|
|
| |
reported by saddam
|