You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
On iOS, if there are multiple wallets that support the lightning: scheme or LUD-17 then there is no mechanism for apps or games to offer a choice to the user on which wallet to open. The wallet that would open is undefined.
Idea
Wallets could publish their scheme for opening their wallet e.g. zebedee: and then apps/games can detect if the wallet exists.
If the user of the app/game wishes to open ZEBEDEE with the lnurl, the developer would be open the wallet with the following format:
zebedee:lnurlw:<insert lnurl here>
[side note, this format already works in ZEBEDEE wallet, not sure if this is by design]
The wallet could then process the lnurlw scheme as if it had been opened via lnurlw:<insert lnurl here>
This would be optional for wallets if they want to support it of course.
The text was updated successfully, but these errors were encountered:
FWIW while implementing blixtwallet: deeplinking for Blixt Wallet, I made sure that the schema nestling suggested here works, as it was the most intuitive solution.
Problem
On iOS, if there are multiple wallets that support the lightning: scheme or LUD-17 then there is no mechanism for apps or games to offer a choice to the user on which wallet to open. The wallet that would open is undefined.
Idea
Wallets could publish their scheme for opening their wallet e.g.
zebedee:
and then apps/games can detect if the wallet exists.If the user of the app/game wishes to open ZEBEDEE with the lnurl, the developer would be open the wallet with the following format:
zebedee:lnurlw:<insert lnurl here>
[side note, this format already works in ZEBEDEE wallet, not sure if this is by design]
The wallet could then process the lnurlw scheme as if it had been opened via
lnurlw:<insert lnurl here>
This would be optional for wallets if they want to support it of course.
The text was updated successfully, but these errors were encountered: