You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be "problems" with the xpubs contained in the /display response. The extended public keys represent the change "sub-account", e.g. m / purpose' / coin_type' / account' / change instead of m / purpose' / coin_type' / account'. This seems to be done intentionally, so do not see this as a bug report. (But I wonder, how useful they are in practice - keys derived from this are never used by JM, right?)
However, having the xpub/zpub for each mixdepth as distinct property in a response from the api would be awesome. 🙌
Jam wants to avoid to do the calculation on the front end and feed a library with the users seed just to get the extended public key.
Related #1267 ("Enable importing joinmarket wallet as watch-only to mobile wallets").
Any insights on this would be great. What are the downsides of this? Do benefits outweigh them?
The text was updated successfully, but these errors were encountered:
There seems to be "problems" with the xpubs contained in the
/display
response. The extended public keys represent the change "sub-account", e.g.m / purpose' / coin_type' / account' / change
instead ofm / purpose' / coin_type' / account'
. This seems to be done intentionally, so do not see this as a bug report. (But I wonder, how useful they are in practice - keys derived from this are never used by JM, right?)However, having the xpub/zpub for each mixdepth as distinct property in a response from the api would be awesome. 🙌
Jam wants to avoid to do the calculation on the front end and feed a library with the users seed just to get the extended public key.
Related #1267 ("Enable importing joinmarket wallet as watch-only to mobile wallets").
Any insights on this would be great. What are the downsides of this? Do benefits outweigh them?
The text was updated successfully, but these errors were encountered: