user934: Problem: Payments to a wallet don't show in a daedalus wallet, because it was sent to an address that exceeds the gap.
How can I increase the gap so I can see (and consume) that utxo?

user252: 
How can I increase the gap so I can see (and consume) that utxo?

Daedalus is simply a UI that (for wallet) serves the data provided by cardano-wallet component, you can either use the API to add address_pool_gap OR use cardano-wallet CLI to override the default address pool gap as below:
cardano-wallet.exe wallet create from-recovery-phrase --address-pool-gap 100 --port XXX

With the reply to your question out the way, it is a very bad idea to use this component for anything beyond a very small centralised userbase service.

The bigger the address gap is, slower will be the performance to fetch details about UTxO, as they have to scan larger amount of empty addresses.
Resource consumption of cardano-wallet with larger amount of addresses will be another trouble you will encounter even if you're alright with using large address gap.

It isnt a new/unique problem, most exchanges who tried to use cardano-wallet face similar issues. They usually end up going with a more proficient solution based on querying a layer above dbsync. One common example, initially an attempt to provide a standard by coinbase - is Rosetta API (you can find cardano-rosetta implementation here, and a typical Construction overview here ). It might be a change in your plans from where you are now, but it's an investment well worth the time - countless folks have wrongly started on cardano-wallet API due to familiarity of a wallet, and had to migrate later - the sooner the better if you're aiming for your solution to cater for larger than few hundred users.

934: <p>Problem: Payments to a wallet don't show in a daedalus wallet, because it was sent to an address that exceeds the gap.</p>
<p>How can I increase the gap so I can see (and consume) that utxo?</p>
 252: <blockquote>
<p>How can I increase the gap so I can see (and consume) that utxo?</p>
</blockquote>
<p>Daedalus is simply a UI that (for wallet) serves the data provided by <code>cardano-wallet</code> component, you can either use the <a href="https://input-output-hk.github.io/cardano-wallet/api/edge/#operation/postWallet" rel="nofollow noreferrer">API</a> to add <code>address_pool_gap</code> OR use cardano-wallet CLI to override the default address pool gap as below:</p>
<pre><code>cardano-wallet.exe wallet create from-recovery-phrase --address-pool-gap 100 --port XXX
</code></pre>
<p>With the reply to your question out the way, it is a very bad idea to use this component for anything beyond a very small centralised userbase service.</p>
<ol>
<li>The bigger the address gap is, slower will be the performance to fetch details about UTxO, as they have to scan larger amount of empty addresses.</li>
<li>Resource consumption of <code>cardano-wallet</code> with larger amount of addresses will be another trouble you will encounter even if you're alright with using large address gap.</li>
</ol>
<p>It isnt a new/unique problem, most exchanges who tried to use <code>cardano-wallet</code> face similar issues. They usually end up going with a more proficient solution based on querying a layer above <code>dbsync</code>. One common example, initially an attempt to provide a standard by coinbase - is Rosetta API (you can find cardano-rosetta implementation <a href="https://github.com/input-output-hk/cardano-rosetta" rel="nofollow noreferrer">here</a>, and a typical Construction overview <a href="https://www.rosetta-api.org/docs/construction_api_introduction.html" rel="nofollow noreferrer">here</a> ). It might be a change in your plans from where you are now, but it's an investment well worth the time - countless folks have wrongly started on cardano-wallet API due to familiarity of a wallet, and had to migrate later - the sooner the better if you're aiming for your solution to cater for larger than few hundred users.</p>
