Ah I see, thanks for looking into it. If I understand right that’s something I can’t change?
I even know what the problem is. https://ghst.to/.well-known/lnurlp/royal-tan-bandicoot you can check callback, and see that they use irl parameters for the user, where it would have been better to use path. Since I assume many LN implementations just blindly add ?amount=12344&…. Instead of parsing the url and adding the additional parameter, you end up with broken request for invoice. So unless they make it a path or all implementations do it right, it will not work as it should 🐶🐾🫡
Callback for you is: https://ghst.to/api/pay?user=royal-tan-bandicoot
The client must add amount parameter and they do it wrong
Discussion
Unless you proxy your address like I am, not possible 🐶🐾🫂
Not too sure what it means to proxy the address or if I could do so 😜
If you really want, I can setup one for you to try. I have fishcake@ln.do as my address, and it proxies to my nodes ugly lnbits address. And I have WoS as a backup, so if proxy cannot fetch from primary, it falls back to WoS . Simple 🐶🐾🫡
Ah ist that similar to ip2tor and https service with duck dns? Got my btc pay Shop on that set up but the home network got issues so that’s most of the time not available. Maybe the Amboss ghost addresses have the same network problems?
Unlikely, I can’t even fetch the invoice 🐶🐾🫡
Wired, I’ve double checked the royal-tan-bandicoot@ghst.to and successfully sent 50 sats last night 🧐
From Phoenix wallet…
Please read what I wrote about why it might fail for me on Damus using Zeus 🐶🐾🫡
I’ll do my best trying to understand 🙏
🐶🐾🫂💜🙌🏻
Just received my alby invite Code while we where writing 😂 plan alby should work now maybe
No need to set one up for me, thank you. Should be abele to work it out somehow; sometime 😆