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

add wallet rpc call to get default fee priority

2025-02-15T20:21:27Z

Set response limits on http server connections

2025-02-14T05:21:05Z

Merge pull request #8617

2025-02-13T17:43:24Z

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

Merge pull request #9614

2024-12-23T16:04:04Z

20a1c00 wallet: report exact reason for open_wallet failure. (0xFFFC0000)

wallet: report exact reason for open_wallet failure.

2024-12-13T17:35:10Z

Daemon-specific proxy for the wallet-rpc.

2024-11-23T19:11:25Z

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.

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.

Merge pull request #9311

2024-05-21T04:42:54Z

dd47d03 Enforce Tx unlock_time is Zero by Relay Rule [RELEASE] (jeffro256)

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