Closed HDauven closed 3 weeks ago
Here there is the design for moonlight. @ZER0 @HDauven could You give us feedbacks on figma file if any?
Moonlight UX/UI follows the same interactions of a Phoenix transaction, we can already see the history in the table below and the balance (moonlight spendable) as well.
As discussed with @autholykos, @ZER0 will handle the design and accept it
@laremas please find a meeting time for the stakeholders to discuss this UX.
Here is the updated Figma file after our meeting yesterday between @HDauven @kieranhall @ZER0.
Design file has been reviewed with @autholykos as well. Considering this addressed.
Summary
With the introduction of Moonlight, our account-based transaction model, users will now have an additional method for creating transactions. This new transaction approach is similar to public chains that do not have privacy, which is in stark contrast to our Phoenix UTXO transactions.
Our web wallet should support both transaction types.
Phoenix can be thought about as cash money, where each note a user has represents a unique banknote held by the user. Transferring that note happens between two users, without exposing who they are.
Moonlight functions like a digital bank account. Transferring funds from one to the other is similar to cash withdrawals from an ATM, or physical bank deposits.
Possible solution design or implementation
Design a UI/UX where it is possible to create both Phoenix and Moonlight transactions. The user should be able to view balances and transaction histories for both models. The interface should ensure a clear distinction between the two transaction types and allow for the transfer of funds from one model to the other.