| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| | |
7b1e9ca multisig: add flag to skip refresh after multisig import (woodser)
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
e44e8b164 wallet: background sync with just the view key (j-berman)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- When background syncing, the wallet wipes the spend key
from memory and processes all new transactions. The wallet saves
all receives, spends, and "plausible" spends of receives the
wallet does not know key images for.
- When background sync disabled, the wallet processes all
background synced txs and then clears the background sync cache.
- Adding "plausible" spends to the background sync cache ensures
that the wallet does not need to query the daemon to see if any
received outputs were spent while background sync was enabled.
This would harm privacy especially for users of 3rd party daemons.
- To enable the feature in the CLI wallet, the user can set
background-sync to reuse-wallet-password or
custom-background-password and the wallet automatically syncs in
the background when the wallet locks, then processes all
background synced txs when the wallet is unlocked.
- The custom-background-password option enables the user to
open a distinct background wallet that only has a view key saved
and can be opened/closed/synced separately from the main wallet.
When the main wallet opens, it processes the background wallet's
cache.
- To enable the feature in the RPC wallet, there is a new
`/setup_background_sync` endpoint.
- HW, multsig and view-only wallets cannot background sync.
|
| |/
|
|
|
|
|
| |
1. Daemon-specific proxy is exclusive with global proxy (--proxy).
2. If you set global proxy (--proxy) you cannot set daemon-specific proxy.
3. If you don't set global proxy, you can set proxy (or not set) proxy for
each daemon connection with the proxy field in jsonrpc to the wallet-rpc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To transfer ~5 XMR to an address such that your balance drops by exactly 5 XMR, provide a `subtractfeefrom` flag to the `transfer` command. For example:
transfer 76bDHojqFYiFCCYYtzTveJ8oFtmpNp3X1TgV2oKP7rHmZyFK1RvyE4r8vsJzf7SyNohMnbKT9wbcD3XUTgsZLX8LU5JBCfm 5 subtractfeefrom=all
If my walet balance was exactly 30 XMR before this transaction, it will be exactly 25 XMR afterwards and the destination address will receive slightly
less than 5 XMR. You can manually select which destinations fund the transaction fee and which ones do not by providing the destination index.
For example:
transfer 75sr8AAr... 3 74M7W4eg... 4 7AbWqDZ6... 5 subtractfeefrom=0,2
This will drop your balance by exactly 12 XMR including fees and will spread the fee cost proportionally (3:5 ratio) over destinations with addresses
`75sr8AAr...` and `7AbWqDZ6...`, respectively.
Disclaimer: This feature was paid for by @LocalMonero.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
|
| |
|
|
|
|
|
|
|
| |
There are vulnerabilities in multisig protocol if the parties do not
trust each other, and while there is a patch for it, it has not been
throroughly reviewed yet, so it is felt safer to disable multisig by
default for now.
If all parties in a multisig setup trust each other, then it is safe
to enable multisig.
|
| |\
| |
| |
| | |
d1f1947 wallet_rpc_server: support regex for get_accounts tag (reemuru)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This commit adds a 'regexp' boolean field to the get_accounts
request. The flag is set to false by default and maintains backwards
compatibility. When set to true the user can search tags by regular
expression filters. An additional error message was added for failed
regular expression searches. Bump minor version to 25.
|
| |/ |
|
| |\
| |
| |
| | |
fb5b2b3 support authentication in monero-wallet-rpc set_daemon (woodser)
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
This ensures each list of recipients is only the recipients
for one transaction. It also adds a new field "summary"
that describes the txset as a whole.
Fixes #7344
|
| | |
|
| | |
|
| |\
| |
| |
| | |
064eeb2 wallet_rpc_server: set seed language in generate_from_keys (moneromooo-monero)
|
| | |
| |
| |
| | |
Also sanity check language name
|
| |\ \
| | |
| | |
| | | |
d46d90c return output key for incoming transfers (benevanoff)
|
| | |/ |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reduces the attack surface for data that can come from
malicious sources (exported output and key images, multisig
transactions...) since the monero serialization is already
exposed to the outside, and the boost lib we were using had
a few known crashers.
For interoperability, a new load-deprecated-formats wallet
setting is added (off by default). This allows loading boost
format data if there is no alternative. It will likely go
at some point, along with the ability to load those.
Notably, the peer lists file still uses the boost serialization
code, as the data it stores is define in epee, while the new
serialization code is in monero, and migrating it was fairly
hairy. Since this file is local and not obtained from anyone
else, the marginal risk is minimal, but it could be migrated
later if needed.
Some tests and tools also do, this will stay as is for now.
|
| |
|
|
| |
Update copyright year to 2020
|
| | |
|
| |\
| |
| |
| | |
ae84ec90 wallet-cli/rpc: allow sweep_all to use outputs in all subaddresses within an account (stoffu)
|
| | |
| |
| |
| | |
account
|
| |\ \
| | |
| | |
| | | |
096a9db Wallet: Distingush amounts for a single subaddress (tmoravec)
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
Adding a new `amounts` field ot the output of `get_transfers` RPC
method. This field specifies individual payments made to a single
subaddress in a single transaction, e.g., made by this command:
transfer <addr1> <amount1> <addr1> <amount2>
|
| |\ \
| | |
| | |
| | | |
b328de6b wallet_rpc_server: add tx weight in transfer commands responses (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
d64e5aa7 wallet: allow message sign/verify for subaddresses (moneromooo-monero)
|
| | |/ |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
0e0351c4 wallet_rpc_server: add count parameter to create_address (Matt Smith)
|
| | |/ |
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
3407743 wallet_rpc_server: add locked field to get_transfers/get_{bulk_,}_payments (moneromooo-monero)
|
| | |
| |
| |
| | |
Much easier to work with than the raw unlock_time field
|