| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |\
| |
| |
| | |
13e28ea simplewallet: batch address creation limit to match rpc (nahuhh)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Rings for outgoing transactions are stored within the scanning code since the last hardfork,
so this code is largely unneccessary now.
Co-authored-by: j-berman <justinberman@protonmail.com>
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
e0df82e simplewallet: respect `do-not-relay` in `sweep_single` (hinto.janai)
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
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.
|
| |/
|
|
|
|
|
|
|
|
|
| |
[RELEASE]
1. Use std::is_standard_layout and std::is_trivially_copyable instead of std::is_pod for KV byte-wise serialization, which fixes compile issue for Boost UUIDs
2. Removed reimplementation of std::hash for boost::uuids::uuid
3. Removed << operator overload for crypto::secret_key
4. Removed instances in code where private view key was dumped to the log in plaintext
Release version of #9450, containing C++14 modified assertions
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Related to https://github.com/monero-project/research-lab/issues/78
Added a relay rule that enforces the `unlock_time` field is equal to 0 for non-coinbase transactions.
UIs changed:
* Removed `locked_transfer` and `locked_sweep_all` commands from `monero-wallet-cli`
APIs changed:
* Removed `unlock_time` parameters from `wallet2` transfer methods
* Wallet RPC transfer endpoints send error codes when requested unlock time is not 0
* Removed `unlock_time` parameters from `construct_tx*` cryptonote core functions
@tobtoht: undo rebase changes tx.dsts -> tx_dsts
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
[release-v0.18]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Detach & re-process txs >= lowest scan height
- ensures that if a user calls scan_tx(tx1) after scanning tx2,
the wallet correctly processes tx1 and tx2
- if a user provides a tx with a height higher than the wallet's
last scanned height, the wallet will scan starting from that tx's
height
- scan_tx requires trusted daemon iff need to re-process existing
txs: in addition to querying a daemon for txids, if a user
provides a txid of a tx with height *lower* than any *already*
scanned txs in the wallet, then the wallet will also query the
daemon for all the *higher* txs as well. This is likely
unexpected behavior to a caller, and so to protect a caller from
revealing txid's to an untrusted daemon in an unexpected way,
require the daemon be trusted.
|
| |\
| |
| |
| | |
5ffa31c wallet2: fail to establish daemon cxn == 'Disconnected' cxn status (j-berman)
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
12e7c41 Merge pull request #5 from j-berman/restore-msig-encrypted-seed (Justin Berman)
848a0c0 Fix segfault restoring encrypted multisig seed (j-berman)
401f5d9 Require user ack multisig is experimental to restore (j-berman)
fc8a5d6 multisig: fix #8537 seed restore (suggestions by @UkoeHB) (j-berman)
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
|
| |\
| |
| |
| | |
41b1a6b simplewallet: print usage when given no args (hinto.janaiyo)
|
| | | |
|
| |/
|
|
|
|
| |
unconfirmed solely uses a - b, and received now accepts b so it can
provide more detailed logs on what occurred (printing a - b, yet with a
and b).
|
| |\
| |
| |
| | |
1164874 src, epee: fix a couple compiler warnings (selsta)
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| | |
0d6ecb1 multisig: add post-kex verification round to check that all participants have completed the multisig address (koe)
|
| | |
| |
| |
| | |
have completed the multisig address
|
| |\ \
| | |
| | |
| | | |
5d388eb Bump ring size to 16 for v15 & remove set default in wallet cli (j-berman)
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
3593a98 simplewallet: fix integrated_address output string (selsta)
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | | |
da9aa1f Copyright: Update to 2022 (mj-xmr)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
3f88fdd simplewallet: add option for exporting tx keys (reemuru)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit adds an option to export transaction
keys when performing export_transfers all. By passing
option=with_keys a new column 'tx key' will be
populated with respective keys.
|
| |\ \ \
| | | |
| | | |
| | | | |
cf44349 account info text alignment (im)
|
| | |/ / |
|
| | |/
|/| |
|
| |\ \
| |/
|/|
| | |
e08abaa multisig key exchange update and refactor (koe)
|
| | | |
|
| |/ |
|
| | |
|