Is your feature request related to a problem? Please describe.
Yes. The problem is that there are multiple ways to tell Lunie you have an address. This presents many opportunities for conflict.
Describe the solution you'd like
If a user signs in with an address and proceeds to make a transaction, the action modal should inform the user that the address they have logged in with is not _in_ the extension and will therefore not work.
We shouldn't let the user send a tx to the extension if the addresses don't match, which we can tell in advance.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
this is a simple but important ux improvement.
Design idea:
can you also make sure that if a user signs in with the extension that "extension" is the default option pre-selected for them? might already work...
Most helpful comment
can you also make sure that if a user signs in with the extension that "extension" is the default option pre-selected for them? might already work...