TrasherDK

Building `release-v0.1_0.17` against Monero `tags/v0.17.2.0` was successful :)

@j-berman when you say `monero/v17.2.3` do you mean `release-v0.17` or `tag v0.17.2.3` ?

In CLI `restore_height` unless it's a restored wallet.

I'm curious to why you choose to return `bad view key` and not just a `401` response?

Well, okay.. That kinda makes sense :smiley: The timing attack part. Wouldn't that require the attacker to be on the same server to make sense? At any time, I'm running...

So, assuming your environment has not been compromised, timing attacks are off the table. Now, correct me if I got something wrong. Sub-addresses are derived from your primary. Why would...

Look-ahead on 10K sub-addresses could become expensive on a server hosting wallets for multiple users, and is probably not a good idea for a program with `light` in the name...

Syncing 10K blocks on a i7-5500/16GB gobbles up 80% CPU for 3-4 mins. one primary and no account/sub-addresses used, both client and server running off SSD. Not exactly light load....

The 10K blocks synced was done by `monero-wallet-gui` on Windows, against a "local" `monerod` running on Slackware 14.2. Connecting to `monerod` and syncing a wallet, seems to have very limited...

I don't think the memory requirement are scary at all. If you need to host 10K primary accounts with sub-addresses, you probably can afford dedicated hardware to run it on....