09:23:35 jberman: any progress on background sync? 16:40:38 ETA 1-2 weeks. I'm prioritizing fixing 8566 atm. I figure bug fixing takes priority over new features. Hoping to be done with that today or tomorrow 16:41:16 While working on 8566 I also started thinking about a different feature that gingeropolous has brought up in the past: allowing a user to "skip" scanning to current height 16:41:58 So if you haven't used your wallet in a while and know you haven't sent/received any txs you can just skip scanning. Seems like it would be simple to implement reusing what I'm doing to fix 8566, and imo would be more impactful than background sync 16:52:32 I suspect people will use that option all the time, and eventually miss a received txn and complain 17:00:49 I was thinking something like: in advanced mode, there's a checkbox in the "Interface" tab that lets you enable the feature. If the feature is enabled, while the wallet is syncing it would display a "skip" button above "Wallet blocks remaining". When you enable the feature, a modal warns you of the consequences before you confirm. Then when you hit the "skip" button, a modal warns you of the consequences every time but you can click a 17:00:49 checkbox that says "don't show this again" 17:00:58 in the GUI 19:14:04 i agree with hyc, seems like a feature that can easily cause headaches 19:15:58 background sync is much simpler and effective 19:16:37 feather wallet is working on this alongside with an option to let you import individual transactions by TX ID 19:17:17 so if you know specifically what transactions you received, you can skip and add them manually, with the added bonus of maybe helping people with missing transaction issues more generally 19:17:55 by feather wallet I mean tobtoht of course :D 19:18:55 what's background sync though 19:22:40 Lyza: allowing wallet to sync in the background while keeping only the viewkey hot 19:23:14 spendkey decrypts when user enters password, and grabs all the synced blocks 19:23:40 major UX improvement for mobile wallets 19:25:13 ok I see. yeah monerujo already does this but I guess it must keep the spend key open 19:25:53 monerujo just keeps the app open in background 19:26:09 jberman's feature will be more secure 19:28:48 yeah it sounds like it -- but you'd need to keep the app open anyway right? I was thinking on desktop this + a system tray icon would be nice. don't think it replaces the skip sync feature though, it seems kinda nice especially if you can also import individual TX IDs 19:30:05 yes but it can be locked in the background, and just have an android service running 19:30:41 def an improvement 19:36:00 I'm trying to restore a wallet from monero-wallet-cli, and it's ignoring the restore height command when passed as `restore height ` and in the json file `"restore_height":""`. Does anyone else have this problem? 19:36:59 I run -monero-wallet-cli, and then it prompts for a restore height. Luckily it properly accepts `"setup-background-mining":"0"` 19:37:39 s/`/`--/, s//-/ 19:47:11 Whats the full command? 19:47:11 `monero-wallet-cli --daemon-address --restore-from-seed --restore-date ` 19:47:11 I can try to reproduce 19:49:12 sgp[m]: the command is `--restore-height` and not `restore height` 19:52:25 at least I'm not aware of such a command 19:54:17 I have no issue with 19:54:17 `./monero-wallet-cli --daemon-address 192.168.0.12:18089 --restore-from-seed --restore-height 2000000` 19:54:17 It starts at 0 and speedruns 10k blocks at a time until 2000000, then starts scanning 19:56:46 I'll keep looking, but for some reason I can't get it to work with --restore-height. Thanks for checking 20:00:46 what exactly doesn't work? 20:00:47 in the json file i use "scan_from_height": 20:02:01 yep, with json file it seems to be `scan_from_height` https://monero.stackexchange.com/a/11045