Skip to content
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

Requirements for next version of "Account Map" #71

Open
Fonta1n3 opened this issue Sep 7, 2020 · 0 comments
Open

Requirements for next version of "Account Map" #71

Fonta1n3 opened this issue Sep 7, 2020 · 0 comments

Comments

@Fonta1n3
Copy link
Contributor

Fonta1n3 commented Sep 7, 2020

Currently the Account Map (AM) only supports one descriptor and is a "minimal backup". Our wallets can support many descriptors. There is a disconnect here. We ought to add additional params to the AM so that we specify a keypool descriptor and then an array of watching descriptors. Currently the way recovery wallets are treated in Gordian-iOS and Fully Noded is that they have one primary descriptor which is used to generate invoice addresses and a similar change descriptor for transactions. However there is also a list of watching descriptors which are included when recovering a wallet. These should also be added to the AM to ensure their wallet is recreated in its entirety. The current AM is designed with the idea to keep it as small as possible, this new approach would not care about size as we can export it as a .json file or animated QR's.

In addition I think we ought to support one "wallet export" file which is essentially just a json file with an array of each wallets AM. Likewise for the QuickConnects. if we are going to release a macOS version of GordianWallet (bc iCloud sync does not work on Catalyst) users will want to easily recreate all of their wallets and node connections in one fell swoop rather then having to do each one individually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant