As we get close to the mid-January activation of Halo 2 and subsequently using Unified Addresses with the Orchard Pool. It would be a good idea for a community discussion around user experience decisions made by wallets developers.
Today, @NighthawkWallet defaults to Sapling Shielded Address for sending and receiving ZEC.
And supports T-address for receiving Transparent ZEC with the only option to Shield all funds.
For the upcoming upgrade, here is a pathway for Nighthawk to work with Unified Addresses:
- Replace Sapling Shielded Address with Orchard Shielded Address(UA) on the “Receive” screen.
- Allow Send/Receive ZEC and view transactions history from Orchard Shielded Address(UA) only.
- Limit funds in Sapling Shielded Address to be manually sent to Orchard Shielded Address(UA) only.
- Support Receiving funds on T-address and enable Manual/Auto shielding of transparent ZEC received on both UA & T-address.
- Exchanges can send transparent ZEC to UA.
- All Exchanges/Service Providers may not immediately upgrade to support UAs, so we need to continue supporting T-address for wallet users.
- Migrating ZEC from Sapling Shielded Pool to Orchard Shielded Pool will publicly expose user funds on the block chain. We might want to warn users about this.
The updated workflows will need to be worked out in the designs for Nighthawk which are in-progress for the current Milestone 3. We will be conducting user feedback and reviews with a small cohort of crypto wallet users soon.
Please provide any comments/suggestions/inputs on anything we might have missed.