pull down to refresh

Has anyone moved lightning wallets from say Breez to Phoenix, Phoenix to their own node, or a LND node to a CLN node and successfully moved their lnurl-auth accounts with them? Using lnurl-auth is interesting, but I’m curious what I’d be locking myself into by using it.
No, you will not be able to move a ln-auth from one implementation to another. Each one is using a different key and are not compatible.
So keep sane your LN-auth accounts. If you want to handle yourself a multiple LN-auth accounts system, use your own LNbits instance, create several accounts and manage from there as you want, and not depending on any mobile app or node.
I would not use the same LN-auth wallet also for day to day LN txs.
reply
But presumably restoring with the same implementation should be fine? I.e a lost phone, and restoring a fresh Phoenix install with the 12 word Phoenix backup, or a fresh Breez install with the backup data file?
So aside from running your own lnbits instance, when using lnurl-auth, the length of your lnurl-auth account(s) is limited to the longevity of any lightning app you choose to use remaining operational?
reply
But presumably restoring with the same implementation should be fine?
Yes.
reply
Thanks!
reply
603 sats \ 1 reply \ @ek 16 May 2023
the length of your lnurl-auth account(s) is limited to the longevity of any lightning app you choose to use remaining operational?
Yes.
However, this can be solved by services giving users the ability to migrate their account to a different LN wallet. Should be as easy as being logged in and just going to your settings to link another LN wallet. Then you can login to the same account using both wallets. Deleting the old linked wallet would then finalize the migration.
However, SN is guilty of not having this, too. But there is already a ticket.
Thanks for posting, this brought the importance of this ticket back into light!
reply
Ah, yes, that would be a great feature to have. Subscribed to notifications for that issue. Thanks.
reply