user4186: We noticed this situation with sending ADA to a wallet using addresses generated from cardano-address (according to the specifications on https://github.com/input-output-hk/cardano-addresses) which are separated by more than several hundred.
Situation
When we send a payment (from Nami or CCVault or wallet-server for example) to an address that is generated by the 2000th key (for example, it just needs to be something more than a few hundred above 0), we see that the transaction posts to the blockchain but is not recognized by any wallet (Nami or CCVault).
However, when you send payment to an that is recognized (something within about 200 addresses from 0th address or 200 addresses from the previously wallet-recognized transaction), you can sequentially increase the addresses by about 200 until you reach within 200 of the initial high-numbered address and then the transaction to the high-numbered address will suddenly appear (even if it is days later).
Question
Can we be certain that the high-n incremented addresses will post to a wallet for verification?
Here is an example of two days worth of transactions.
Day 1 Jan 16
2000th addr tx 2000th address /0/2000 DATUM MSG 2000 - JAN 16, 18:16 PST
200th addr tx 200th address /0/200 DATUM MSG 200 - JAN 16, 18:21 PST

200 SHOWN IN WALLET 18:22 PST
2000 NOT SHOWN IN WALLET 18:22 PST

400th addr tx 400th addr /0/400 DATUM MSG 400th - JAN 16, 18:32 PST

400 SHOWN IN WALLET 18:32 PST
2000 NOT SHOWN IN WALLET 18:32 PST

600th addr tx 600th addr /0/600 DATUM MSG 600th - JAN 16, 18:33 PST

600 SHOWN IN WALLET 18:33 PST
2000 NOT SHOWN IN WALLET 18:33 PST

800th addr tx 800th addr /0/800 DATUM MSG 800th - JAN 16, 19:20 PST

800 SHOWN IN WALLET 19:20 PST
2000 NOT SHOWN IN WALLET 19:20 PST

Day 2 Jan 17
1000th addr tx 1000th addr /0/1000 DATUM MSG 1000th - JAN 17, 09:49 PST

1000 SHOWN IN WALLET 09:49 PST
2000 NOT SHOWN IN WALLET 09:49 PST

1200th addr tx 1200th addr /0/1200 DATUM MSG 1200th - JAN 17, 09:53 PST

1200 SHOWN IN WALLET 09:53 PST
2000 NOT SHOWN IN WALLET 09:53 PST

1400th addr tx 1400th addr /0/1400 DATUM MSG 1400th - JAN 17, 09:57 PST

1400 SHOWN IN WALLET 09:57 PST
2000 NOT SHOWN IN WALLET 09:57 PST

1600th addr tx 1600th addr /0/1600 DATUM MSG 1600th - JAN 17, 09:59 PST

1600 SHOWN IN WALLET 09:59 PST
2000 NOT SHOWN IN WALLET 09:59 PST

1800th addr tx 1800th addr /0/1800 DATUM MSG 1800th - JAN 17, 10:02 PST

1800 SHOWN IN WALLET 10:02 PST
2000 NOT SHOWN IN WALLET 10:02 PST

2000 SHOWN IN WALLET JAN 17, 10:17 PST

user4302: Cardano addresses use the BIP-32 standard for key derivation. This allows a very large (2^31-1) number of addresses to be created per account index, per master seed.
Being that most computers running wallet software do not have enterprise level specs, it is not feasible (nor necessary) for them to query the chain for such a large number of addresses. For this reason, wallet software(s)' "address discovery" is throttled by an address-gap parameter that limits how many address indexes are derived and queried, as described in BIP-44. In short,

If N is the gap-parameter

And X is the highest index with UTXO's currently recognized by the wallet

Then the wallet software will check all indexes from 0 to X+N


Most wallet software has this limit set to 20 by default, but my guess is yours was set to 200, since your examples are all separated by 200 indexes. In case funds live at a very high index number that you don't want to query all the way up to, you can always manually derive the spending key for that single address using cardano-addresses.

4186: <p>We noticed this situation with sending ADA to a wallet using addresses generated from cardano-address (according to the specifications on <a href="https://github.com/input-output-hk/cardano-addresses" rel="nofollow noreferrer">https://github.com/input-output-hk/cardano-addresses</a>) which are separated by more than several hundred.</p>
<p><em><strong>Situation</strong></em></p>
<p>When we send a payment (from Nami or CCVault or wallet-server for example) to an address that is generated by the 2000th key (for example, it just needs to be something more than a few hundred above 0), we see that the transaction posts to the blockchain but is not recognized by any wallet (Nami or CCVault).</p>
<p>However, when you send payment to an that is recognized (something within about 200 addresses from 0th address or 200 addresses from the previously wallet-recognized transaction), you can sequentially increase the addresses by about 200 until you reach within 200 of the initial high-numbered address and then the transaction to the high-numbered address will suddenly appear (even if it is days later).</p>
<p><em><strong>Question</strong></em></p>
<p>Can we be certain that the high-n incremented addresses will post to a wallet for verification?</p>
<p>Here is an example of two days worth of transactions.</p>
<h2>Day 1 Jan 16</h2>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=6d1537692e98bd3b7b6c90f5f54907687ff955c4e19d838a796c1393eb657491" rel="nofollow noreferrer">2000th addr tx</a> 2000th address /0/2000 DATUM MSG 2000 - JAN 16, 18:16 PST</p>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=6d1537692e98bd3b7b6c90f5f54907687ff955c4e19d838a796c1393eb657491" rel="nofollow noreferrer">200th addr tx</a> 200th address /0/200 DATUM MSG 200 - JAN 16, 18:21 PST</p>
<ul>
<li>200 SHOWN IN WALLET 18:22 PST</li>
<li>2000 NOT SHOWN IN WALLET 18:22 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=30586713d8f8abde3fcc4bc36cfc5c9db9aec7b140a6aa57c477cab8eb88aad2" rel="nofollow noreferrer">400th addr tx</a> 400th addr /0/400 DATUM MSG 400th - JAN 16, 18:32 PST</p>
<ul>
<li>400 SHOWN IN WALLET 18:32 PST</li>
<li>2000 NOT SHOWN IN WALLET 18:32 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=cf99d0eebe4284f0a39f569992cae0426e135960be1bc2ed68842a3b29881422" rel="nofollow noreferrer">600th addr tx</a> 600th addr /0/600 DATUM MSG 600th - JAN 16, 18:33 PST</p>
<ul>
<li>600 SHOWN IN WALLET 18:33 PST</li>
<li>2000 NOT SHOWN IN WALLET 18:33 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=895cb0123130d73ef58821547d496936dc207679fb2d01c749e9c5f1f7f46e0b" rel="nofollow noreferrer">800th addr tx</a> 800th addr /0/800 DATUM MSG 800th - JAN 16, 19:20 PST</p>
<ul>
<li>800 SHOWN IN WALLET 19:20 PST</li>
<li>2000 NOT SHOWN IN WALLET 19:20 PST</li>
</ul>
<h2>Day 2 Jan 17</h2>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=d10e86ba7ac218b248fafd21d49c1e6b0a0d6b380279c0b87d4fd04a588cf1c9" rel="nofollow noreferrer">1000th addr tx</a> 1000th addr /0/1000 DATUM MSG 1000th - JAN 17, 09:49 PST</p>
<ul>
<li>1000 SHOWN IN WALLET 09:49 PST</li>
<li>2000 NOT SHOWN IN WALLET 09:49 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=ed09ca1c00f961d2e21121963a43e829c0c8065fc312c53b558f97e680572a0a" rel="nofollow noreferrer">1200th addr tx</a> 1200th addr /0/1200 DATUM MSG 1200th - JAN 17, 09:53 PST</p>
<ul>
<li>1200 SHOWN IN WALLET 09:53 PST</li>
<li>2000 NOT SHOWN IN WALLET 09:53 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=34089914a9c159f7527529e9ef78e87bb8883713416f6299f0cc2f1ad8c5e514" rel="nofollow noreferrer">1400th addr tx</a> 1400th addr /0/1400 DATUM MSG 1400th - JAN 17, 09:57 PST</p>
<ul>
<li>1400 SHOWN IN WALLET 09:57 PST</li>
<li>2000 NOT SHOWN IN WALLET 09:57 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=5eb6527f5bb17ca6ef73c5e78f96468bbb971adedb69386f410005eb37eff8bc" rel="nofollow noreferrer">1600th addr tx</a> 1600th addr /0/1600 DATUM MSG 1600th - JAN 17, 09:59 PST</p>
<ul>
<li>1600 SHOWN IN WALLET 09:59 PST</li>
<li>2000 NOT SHOWN IN WALLET 09:59 PST</li>
</ul>
<p><a href="https://explorer.cardano-testnet.iohkdev.io/en/transaction?id=71cf10a8eb81ebbbe309165bc76564ee72db1d83d1dea5e7e56b7d05c08643d0" rel="nofollow noreferrer">1800th addr tx</a> 1800th addr /0/1800 DATUM MSG 1800th - JAN 17, 10:02 PST</p>
<ul>
<li>1800 SHOWN IN WALLET 10:02 PST</li>
<li>2000 NOT SHOWN IN WALLET 10:02 PST</li>
</ul>
<p><strong>2000 SHOWN IN WALLET JAN 17, 10:17 PST</strong></p>
 4302: <p><a href="https://github.com/input-output-hk/cardano-addresses" rel="nofollow noreferrer">Cardano addresses</a> use the <a href="https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki" rel="nofollow noreferrer">BIP-32</a> standard for key derivation. This allows a very large (2^31-1) number of addresses to be created per account index, per master seed.</p>
<p>Being that most computers running wallet software do not have enterprise level specs, it is not feasible (nor necessary) for them to query the chain for such a large number of addresses. For this reason, wallet software(s)' &quot;address discovery&quot; is throttled by an address-gap parameter that limits how many address indexes are derived and queried, <a href="https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#Account_discovery" rel="nofollow noreferrer">as described in BIP-44</a>. In short,</p>
<ul>
<li><p>If N is the gap-parameter</p>
</li>
<li><p>And X is the highest index <em>with</em> UTXO's currently recognized by the wallet</p>
</li>
<li><p><strong>Then the wallet software will check all indexes from 0 to X+N</strong></p>
</li>
</ul>
<p>Most wallet software has this limit set to 20 by default, but my guess is yours was set to 200, since your examples are all separated by 200 indexes. In case funds live at a very high index number that you don't want to query all the way up to, you can always manually derive the spending key for that single address using cardano-addresses.</p>
