Where should wallets explain the differences between on-chain Bitcoin and Lightning?

The primary issue arises from the common misconception among beginners who do not differentiate between on-chain Bitcoin and Lightning Network transactions, often referring to both simply as "BTC." This confusion necessitates strategic decisions regarding the amount and timing of information presented to the user, tailored to enhance understanding without overwhelming them.

When it comes to receiving payments, the dilemma revolves around whether users should be prompted to choose between on-chain and Lightning before they see payment details or if the wallet should automatically guide them based on the transaction type. This decision influences how straightforward the payment process appears to the user, balancing simplicity with adequate education on the differences between these transaction types. For sending payments, after a user inputs an address or invoice, the wallet usually identifies the type of payment automatically. However, it remains crucial to decide whether the confirmation screen should explicitly label the transaction as on-chain or Lightning and provide details about the expected fees, transaction speed, and potential failure scenarios to set realistic expectations.

Furthermore, the aspect of backup and recovery introduces additional complexities. The general statement that a "seed phrase backs up your wallet" is somewhat oversimplified as what gets restored can vary significantly depending on how the wallet's Lightning features are implemented. A clear explanation is vital prior to any loss of device to ensure users are adequately informed about what their backup will actually recover without delving too deeply into technical jargon.

Lastly, the handling of payment failures poses yet another challenge. The decision to either shield the user from the differences between on-chain and Lightning payments until an issue arises, or to educate them beforehand, affects their overall experience and expectation management. This balance between transparency and simplicity is pivotal in shaping user confidence and satisfaction.

Understanding these nuances is crucial for developers and support teams in crafting user interfaces that effectively communicate these distinctions. It is essential to gather insights on effective interface patterns, terminology, and outcomes from user testing to determine the most opportune moments—be it during onboarding, at the point of transaction confirmation, or during the backup process—to introduce such critical information. This approach not only enhances user experience but also ensures a higher level of user education and engagement with the product.