Justin Berman

There is clear interest in the ability for an app to be able to start background sync without a user needing to open the wallet and enter a password, even...

I updated the PR with the core changes to support what we discussed above. Would like to get an ACK on the general approach/UX/dev UX I took in the PR...

Good idea from @kayabaNerve I'm adding to my TODO's: Keep a copy of the background encryption key stored in the main wallet. This would offer a material UX improvement to...

I implemented @kayabaNerve 's idea to keep a copy of the background cache encryption key stored in the main wallet. The PR's code now matches the spec detailed in the...

Yes please :) [this comment](https://github.com/monero-project/monero/pull/8619#issue-1417682567) You can also read through the code to see how it implements the described behavior and functionality, but yes you're right, it's not ready for...

> Probablistically selecting results, or yielding multiple results, will lead to unexpected/undesirable behavior. I think this is a fair argument. > 1. Banning trimmed seeds (trimmed referring to partial words,...

> (though note that, if any two dictionaries overlap in a single word, that would imply you need to specify a language to disambiguate) Good spot here. I checked and...

Worth noting: there is an additional UX thorn with requiring specifying a language. There's both an English and EnglishOld, and there are duplicate words across both (e.g. `goodbye`). Users would...

> Probably the easiest option would be to datestamp it This is a good solution for EnglishOld. > Wallets can also try to abstract it, by decoding with all languages,...

Haven't been able to repro this behavior, but a few questions to help debug: Are the daemons you're using compiled from source or release binaries? edit: also do you know...