Wouldn't always generating new addresses risk hitting the gap limit?

[ConorOkus]

Repost from Discord by amoyer

Follow-up question by Roy0Anonymous

"Is there provision to change default gap limit in BDK?"

[ConorOkus]

@thunderbiscuit:

"Yes it eventually would. One thing you can do is keep the gap limit very high if you want (say 500; would be unlikely that you give out that many addresses in a row and none ever get used). I often use the AddressIndex.LastUnused myself (if you do a sync between your address generation for example, that would be a clean way to ensure you don't reuse).

Related to this is that for wallets that display a bit more "bitcoin internals" to their users, showing the index of the address is also a good idea (requires the user knows a bit more about what is going on, but if a feature I absolutely love myself)."

[ConorOkus]

@thunderbiscuit:

"Yep you can change it using the stop_gap field on your blockchain client configuration."