21:12:38 <sandbeach123> Hi, would there be a problem for a wallet to scan say last month, and looking for say major index 10 and minor index 100000? Does a wallet look for all possible indexex or only up to a range by default?
21:17:01 <jeffro256> Only up to a certain range. This is called the "subaddress lookahead"
21:18:33 <jeffro256> It automatically expands when it detects received XMR to high-index address. But if there's a big enough gap (by default 50 in major, 200 in minor), then it won't scan for that and will miss received XMR to that address
21:23:43 <sandbeach123> Thanks. I am planning to launch a xmr pos at play store, now I want to get the ux part right. Should I ask the user to set a limit for the minor index, so the address will get reused (back to minor 0) when reaching 100? Or just to tell the user to make sure he generate all subaddresses in is admin wallet to make sure his wallet is scanning all
21:23:43 <sandbeach123> possible txs?
21:35:19 <sandbeach123> Btw it will be open source and only scan the node the user wants
21:38:56 <jeffro256> If it's fine to re-use old addresses if a payment didn't go through, you could re-use old unused address indices if you would otherwise exceed the default lookahead 
21:41:25 <jeffro256> Alternatively, you could use integrated addresses if you don't need each receive to be indistinguishable from the next 
21:53:31 <sandbeach123> I will look into integrated addresses
21:53:35 <sandbeach123> Thanks