when verifying a multisig address from sparrow the address verification tool on core searches the descriptor but it starts at deriv 51-100 and change 0-30 and then if you continue it goes 23-150 and only then 0-20 or something to like this. but it takes 3 search attempts to start at 0.
annoyingly key presses have been deliberately slowed down for eg if you press any number in quick succession it forces you to type slowly its quite annoying. this was not like that previously
The address search order is expected. Passport Core remembers the last successfully verified index and begins around that point, then expands the search backwards and forwards. This avoids repeatedly starting from zero for wallets that have already used many addresses. It affects only the search order, not the address validation itself.
Passport Core also checks receive address 0 separately at the beginning. If you are specifically verifying receive address 0 and it is not found until a later attempt, please let us know, as that would be different from the expected behaviour.
The keypad behaviour is also intentional. A short same-key debounce was added to prevent a single physical press from being registered twice. Very rapid repeated presses of the same number may therefore require slightly more spacing. Different numbers pressed quickly should not be affected.
It does not seem to remember the last search. I understand the logic however after successfully finding /0 by looking forwards then backwards, trying to search for /1 resulted in the same behavior. looking forward and then back. It did not remember it already found /0 so let me start in the beginning.
Thanks, that matches the intended behaviour. Passport retains the highest verified index as its starting point. Verifying /0 does not reset that value, so a subsequent search for /1 may still begin higher and work backwards. Sorry if I didn’t make that clearer in my previous post.
This affects only the search order, not the address validation itself.
Wouldnt a solution be to remember your last search then? if you last searched/5 then why not know to start at 0-50. and if you last searched /51 then it would start at 51-100??
That would be another possible approach, but it comes with a trade-off. Passport deliberately retains the highest verified index for that account and address branch, since wallet address usage normally progresses upwards. Verifying an older address therefore does not move the starting point backwards and make the next current-address search slower.