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
{{ message }}
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.
It is a HUGE pain right now to manage both Bitcoin and BitcoinCash with the Nano S + Chrome wallet. Currently, switching from BTC to BCH (or vice versa) requires:
Opening the correct app on the Nano S device
Selecting the desired block chain
Selecting Legacy vs. Segwit (for BTC) or Main vs. Split (for BCH)
This is a ton of steps for something as simple as checking a wallet balance, mostly because the "Remember my choice" option only applies to which blockchain should be selected, but it affects both BTC and BCH, which doesn't make sense.
Proposal for what should be enhanced:
Opening the BitcoinCash app on the Nano S should automatically select the BitcoinCash blockchain, as it is the only valid chain currently in existence for BCH (please correct me if I am wrong about this).
Selecting Legacy vs. Segwit and Main vs. Split should have a "Remember my choice" option, just as the selection screen for the Bitcoin blockchain does. (This could also be implemented as simply no longer prompting once the user selects Segwit or Split, as I believe once those are selected it doesn't make sense to go back to the other option. Again please correct me if I am wrong here.)
Thanks.
The text was updated successfully, but these errors were encountered:
It is a HUGE pain right now to manage both Bitcoin and BitcoinCash with the Nano S + Chrome wallet. Currently, switching from BTC to BCH (or vice versa) requires:
This is a ton of steps for something as simple as checking a wallet balance, mostly because the "Remember my choice" option only applies to which blockchain should be selected, but it affects both BTC and BCH, which doesn't make sense.
Proposal for what should be enhanced:
Thanks.
The text was updated successfully, but these errors were encountered: