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
Currently, we should remove from device mainnet wallet to recreate a testnet account
It's too complicated
Describe the solution you'd like
Allow the user to switch between networks (mainnet or testnet).
If the user doesn't have a keychain and keychainAccess corresponding to the current network in the other network, they are prompted to create them.
Before creation, the user is offered the option to either duplicate one or more existing services in the target keychain or to create a new service.
The selection of existing services has only one constraint: there must be at least one wallet-type service (and therefore no aeHosting).
Once aeWallet detects the presence of the keychain on both networks, the user can switch between the two networks via the general menu of aeWallet.
Once the keychains are available on both networks, they operate independently with their own lifecycle.
The user can create or remove any account as they currently do. (In case of removal, simply recreating the service with the same name will restore the transaction chain due to the derivation path management of the service name.)
A "enable testnet" option, set to "no" by default, is available in the customization menu to allow users to activate this feature.
Clearly notify the user whether they are in mainnet or testnet.
Replace the Buy UCO button with access to the Faucet when the user is in testnet.
NB: This issue doesn't aim to implement multi-keychain management in the wallet for now.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently, we should remove from device mainnet wallet to recreate a testnet account
It's too complicated
Describe the solution you'd like
Allow the user to switch between networks (mainnet or testnet).
If the user doesn't have a keychain and keychainAccess corresponding to the current network in the other network, they are prompted to create them.
Before creation, the user is offered the option to either duplicate one or more existing services in the target keychain or to create a new service.
The selection of existing services has only one constraint: there must be at least one wallet-type service (and therefore no aeHosting).
Once aeWallet detects the presence of the keychain on both networks, the user can switch between the two networks via the general menu of aeWallet.
Once the keychains are available on both networks, they operate independently with their own lifecycle.
The user can create or remove any account as they currently do. (In case of removal, simply recreating the service with the same name will restore the transaction chain due to the derivation path management of the service name.)
A "enable testnet" option, set to "no" by default, is available in the customization menu to allow users to activate this feature.
Clearly notify the user whether they are in mainnet or testnet.
Replace the Buy UCO button with access to the Faucet when the user is in testnet.
NB: This issue doesn't aim to implement multi-keychain management in the wallet for now.
The text was updated successfully, but these errors were encountered: