There are several ways to do that:

option 1
1 seed with customisable derivation paths or a passphrase. It sounds good because you only have to remember 1 seed, but from my experience in Eclair Mobile, the issue is that some users will forget to backup the derivation path (or the passphrase) and will lose their funds.

option 2
Have some logic within Phoenix that somehow segregates funds based on user configuration. It sounds good from an UX perspective, as the user would not have to backup anything more than they already do. Also, they would be able to reuse their channel (and the liquidity they bought) across those sub-wallets. However it would be technically challenging, since Phoenix would have to persist the configuration that segregates those funds across reinstall. Besides, this segregation would only be done in the UI, not at the channel level, which causes issue with #607 (the actual funds available would be visible from the channels list screen).

option 3
Use different seeds within the same instance of Phoenix. The UI gives you a button in the Settings to create/restore/switch to another seed. Only one wallet would be active at a given time.

Option 3) seems the correct solution to me. It should be relatively easy to implement without too many side-effects, and should work for #607. Although it would force the user to backup several seeds.

@nvk Is option 3) what you had in mind ?

Multi Wallet Support #606

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions