Scan also for unused addresses about xpub-scan

[glethuillier]

By default, the gap limit is 20 addresses. It can be extended by changing the value of this variable (e.g., const DEFAULT_GAP_LIMIT = 1000).

Therefore, if you experience a gap limit error, it will be detected in the range that you provide through this variable, and the used addresses will be displayed like this:

SegWit          m/1/0          {active address 1, pre gap}   0               +0.30998771     ←	-0.30998771     →
SegWit          m/1/1          {active address 2, pre gap}   0               +0.29764036     ←	-0.29764036     →
SegWit          m/1/1001       {active address 3, post gap}  0               +0.09834688     ←	-0.09834688     →
SegWit          m/1/1002       {active address 4, post gap}  0.01178649      +0.01178649     ←	-0              →
SegWit          m/1/1003       {active address 5, post gap}  0.02907135      +0.02907135     ←	-0              →
...

In other words, the unused addresses belonging to the gap are never displayed, but the used addresses outside the gap are. The gap is rendered implicitly: it can be inferred from the derivation paths (in this example: m/1/1 ⇨ m/1/1001).

Do you think that this is helpful, or would you still prefer to have a way to display the unused addresses belonging to the gap?