j-berman e71c8bf190 wallet: background sync with just the view key ... - 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.		2024-05-24 23:11:58 -07:00
..
__init__.py	functional_tests: move RPC API to utils, it is not test specific	2019-03-22 15:29:44 +00:00
daemon.py	functional_tests: test HTTP digest auth	2024-03-11 23:54:50 -05:00
rpc.py	functional_tests: test HTTP digest auth	2024-03-11 23:54:50 -05:00
wallet.py	wallet: background sync with just the view key	2024-05-24 23:11:58 -07:00
zmq.py	Copyright: Update to 2023	2023-01-16 13:00:18 +01:00