New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decrease gap limit to 21 #12921
Comments
Reply by @lontivero on a PR I made in the past: #10473 (comment) If consensus changed I can reopen it |
21 might be too low when promoting privacy preserving habits like never giving the same address to two entities. Some wallet like Green wallet will display a new address everytime one go back and forth the receive page, some will constantly show the last one until coins are received, two extremes. wasabi and electrum seems to be in the middle with manual creation of new addresses, Wasabi is forcing the use of labels which leads people to create fake label name and clicking on any at random one to just get past that step. A gap limit of 50 should cover the vast majority of edge cases. |
Would like to work on this |
Small gap limits cause problems in some use cases, for example, when you use wallet in Wasabi, combined with same wallet as watch only (xpub) in BTCPay Server or SatSale. Which seems normal practice for merchants to me, you might not want to expose hot wallet to a server online. I have this problem with https://donate.kristapsk.lv and Blue Wallet currently. |
Still no consensus, closing. Better keep as it is. |
We increased the gap limit because of some synchronization problems in the past, these are fixed now, and a larger value leads to longer loading time.
We should decrease the gal limit to 21.
The text was updated successfully, but these errors were encountered: