monzero-core.git/src/cryptonote_basic/account.h, branch mainMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=main2024-05-25T03:42:59Zwallet: background sync with just the view key2024-05-25T03:42:59Zj-bermanjustinberman@protonmail.com2022-10-14T01:33:33Zurn:sha1:e44e8b164030cfbddb9ae8b39251c1ccf396e2b6
- 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.
src, epee: fix a couple compiler warnings2022-05-16T22:33:10Zselstaselsta@sent.at2022-05-16T22:33:10Zurn:sha1:1164874afc29212155de615531266c91cfdb7e4eCopyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009multisig key exchange update and refactor2022-02-22T22:37:42Zkoeukoe@protonmail.com2021-08-03T04:27:43Zurn:sha1:e08abaa43f2c534bf21c0ed59ba325538502007eRevert "Use domain-separated ChaCha20 for in-memory key encryption"2020-08-17T19:08:59Zluigi1111luigi1111w@gmail.com2020-08-17T19:08:59Zurn:sha1:765db1ae7a3337d085584ab31983fe6b7599dbcb
This reverts commit 921dd8dde5d381052d0aa2936304a3541a230c55.
Use domain-separated ChaCha20 for in-memory key encryption2020-08-09T23:11:54ZSarang Noether32460187+SarangNoether@users.noreply.github.com2020-08-09T23:11:54Zurn:sha1:921dd8dde5d381052d0aa2936304a3541a230c55Update copyright year to 20202020-05-07T02:36:54ZSomaticFanaticafdlkajdlfkj@aldkfjf.com2020-05-07T02:36:54Zurn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6
Update copyright year to 2020
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6device/trezor: trezor support added2018-11-02T20:36:39ZDusan Klinecdusan.klinec@gmail.com2018-08-23T21:50:53Zurn:sha1:29ffb6bba8867586986345b4f0c560e5ea5fce85hw_device: support for multiple devices added [for review]2018-09-14T14:02:00ZDusan Klinecdusan.klinec@gmail.com2018-08-23T22:50:31Zurn:sha1:f9b22a7b01994f444185f38fe1f645593590c943
- device name is a new wallet property
- full device name is now a bit more structured so we can address particular device vendor + device path. Example: 'Ledger', 'Trezor:udp', 'Trezor:udp:127.0.0.1:21324', 'Trezor:bridge:usb01'. The part before ':' identifies HW device implementation, the optional part after ':' is device path to look for.
- new --hw-device parameter added to the wallet, can name the hardware device
- device reconnect added