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
We've implemented the LNURL fallback scheme with URLs as outlined in LUD-01 but it seems like a number of wallets still haven't implemented this and there's no signal for which ones do.
Should we incorporate this sort of data into the compatibility table somehow as a signal to ones who don't support it yet that they should?
From my testing with the wallets I have access to I came up with the following:
I had a look at it for Zap Android and in this case it failed due to the parameter being uppercase.
"LIGHTNING=LNURL1..." instead of "lightning=LNURL1..."
Thank you for opening filing issues for each project.
vindard
changed the title
Misleading "supported" table for LUD-01 in README
Misleading "supported" table for LUD-01 f in README (fallback support)
Apr 19, 2023
vindard
changed the title
Misleading "supported" table for LUD-01 f in README (fallback support)
Misleading "supported" table for LUD-01 in README (fallback support)
Apr 19, 2023
Description
We've implemented the LNURL fallback scheme with URLs as outlined in LUD-01 but it seems like a number of wallets still haven't implemented this and there's no signal for which ones do.
Should we incorporate this sort of data into the compatibility table somehow as a signal to ones who don't support it yet that they should?
From my testing with the wallets I have access to I came up with the following:
The text was updated successfully, but these errors were encountered: