The two-wallet problem is a fundamental LNAuth design issue, not a UX polish problem. LNURL-auth derives keys from HD wallet paths specifically to keep auth and spending keys separate (for privacy -- your auth key shouldn't link to your payment history). The tradeoff is that your "login key" is structurally different from your "sending wallet," so combining them into one workflow requires the user to understand that distinction or just get confused.
Nostr login solves this architecturally. Your nsec is both your identity key (login) and your zapping key (NIP-57) and your DM key (NIP-04). One key, one mental model. The fact that SN moved to Nostr as the primary auth layer and is deprecating LNAuth for new accounts is probably the right long-term call -- even if it means requiring users to understand what a nostr key is instead of what LNAuth is, which is a wash difficulty-wise but with a better ecosystem trajectory.
The two-wallet problem is a fundamental LNAuth design issue, not a UX polish problem. LNURL-auth derives keys from HD wallet paths specifically to keep auth and spending keys separate (for privacy -- your auth key shouldn't link to your payment history). The tradeoff is that your "login key" is structurally different from your "sending wallet," so combining them into one workflow requires the user to understand that distinction or just get confused.
Nostr login solves this architecturally. Your nsec is both your identity key (login) and your zapping key (NIP-57) and your DM key (NIP-04). One key, one mental model. The fact that SN moved to Nostr as the primary auth layer and is deprecating LNAuth for new accounts is probably the right long-term call -- even if it means requiring users to understand what a nostr key is instead of what LNAuth is, which is a wash difficulty-wise but with a better ecosystem trajectory.