Quote from: ranochigo on December 11, 2017, 01:49:23 PM

Electrum has the same master public key that is used in the service you've stated. With that, Electrum will constantly query for transactions in addresses within the gap limit.

For example, your gap limit is 25 addresses. After the initial address generated by default by Electrum, Electrum will continue to look for transactions in the next 25 address. If the next address has a transaction associated with it, Electrum will query another 25 addresses after it, and so on.

Thanks!

Is there a way to tell Electrum to query beyond the gap limit? Or, better yet, is there a way to tell Electrum to look for an address that was derived in an external application (like that CoinSimple example I gave) that might be beyond the configured gap limit?

Here's my actual problem: I have a developer that is using a source code library that can take a MPK and derive a child address from it. He wrote a test program that did this (using the MPK from my electrum wallet), and I sent a small amount of coin to it. However, this address never appears in the Electrum wallet. But it must be a valid child address because it was generated from the same master public key (MPK) and the transaction was successfully broadcast and included in a block.

Thanks in advance for any of your input.