monzero-core.git/src/wallet/api/wallet.cpp, branch v0.18.4.0

Merge pull request #8617

2025-02-13T17:43:24Z

e44e8b164 wallet: background sync with just the view key (j-berman)

build: fix build with Boost 1.85 and remove instances of viewkey logging [RELEASE]

2024-09-10T21:07:36Z

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

wallet: background sync with just the view key

2024-05-25T03:42:59Z

- 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.

Enforce Tx unlock_time is Zero by Relay Rule [RELEASE]

2024-04-29T05:08:53Z

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

wallet2: fix rescanning tx via scan_tx

2023-03-13T19:57:43Z

- 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.

Merge pull request #8615

2022-12-01T07:06:16Z

85c9fe5 wallet2: fix create view-only wallet from existing wallet (j-berman)

wallet2: fix create view-only wallet from existing wallet

2022-10-18T18:47:50Z

wallet_api: take priority into account when estimating fee

2022-10-13T01:36:51Z

Merge pull request #8585

2022-09-26T19:57:58Z

5ffa31c wallet2: fail to establish daemon cxn == 'Disconnected' cxn status (j-berman)

wallet2: fail to establish daemon cxn == "Disconnected" cxn status

2022-09-22T02:12:16Z