Quote from: DaveF on Today at 06:10:56 PM

Is the 20 address arbitrary or is the there a programming reason you have that limit?
And is there a way to show the private key for a particular address instead of revealing the seed words?

Either way VERY cool project.

-Dave

Thanks Dave!

The 21 address limit is for two reasons:
1) Unleashing the full potential of an HD wallet could lead to an enormous amount of addresses in a wallet which will exceed public API usage limits. Blockchair for example uses a point/cost system. Larger requests "cost" more and you will hit your limit with larger requests.
2) Most HD wallets have a look-ahead gap of around 20. Without a limit users could potentially create 30 addresses (for example)in a keychain and then send funds to the 30th address which may go unnoticed if they try to recover on a wallet that has a look-ahead gap less than 30. To the user it may appear like they have lost funds when attempting to recover from the mnemonic, when in reality the wallet just can't see it due to the look-ahead gap issue.

If you are an advanced user and want to get the WIFs simply typing `fkarr` in the browser console will reveal the 21 private key array. They are in respective order with the address array named `farr`.