[UX] Wallet recovery depth steps confusing

[f321x]

When recovering the wallet from the mnemonic backup the user first has to click to detect ecash from derivation 0 - 50, then he has to click again for 50 - 100, etc...
One problem here is that if ecash is found in 0 - 50 the user could think that everything has been found and continue without scanning 50 - 100 and missing some ecash.
Also it's confusing for users to do "the same thing" multiple times.
Couldn't the wallet just scan until it doesn't detect unspent ecash anymore all in one step?

[minibits-cash]

It could, but there is some performance problem related to used cryptographic operations that are very slow specifically in react native - you can see each round taking quite a time.

Agree not optimal, but for now this is safer option.

[f321x]

If you mean the time it takes to load in the restoring process, i feel like it is not a big problem to wait some time as long as the UI shows that its doing something (Restoring balance...). Restoring onchain bitcoin wallets like Bluewallet also take >30 sec if it tries to scan different derivation paths.
Not sure about the other stuff going on in the background of Minibits, so just my unqualified observation.

[ThePhoDit]

Came here to ask how the restoring process works exactly. What are keystores? Do I have to scan them all to ensure all txs are found?