pull down to refresh
The coinos NWC string includes the lightning address (e.g. xxxxx&lud16=nout@coinos.io), so why do users have to set it up separately? Can't you just parse that and use it?
Is lud16 not what I think it is and the fact that it matches my receive lightning address is just coincidence?
damn, unfortunately the 700 sats for my zap couldn't be forwarded to your wallet because no route was found
There's a big chance that I actually don't have it configured correctly somewhere :)
You did receive 70 sats here though
So I guess the route is very illiquid
I guess I need to zap more to balance the channels :)
haha yes
Oh, to be honest, I just haven't noticed that Coinos includes it and completely forgot that NWC strings can include it!
We can definitely do something with that, great idea, thank you!
Yeah, my original question was meant to complain about the UX when I have to set up send and then receive to lightning address separately even though it could all be done as a single step.
Btw, you definitely earned that description in my eyes now:
Chief user experience complainer
Missing that NWC strings can include a lud16 parameter was definitely incompetence on my end haha
embarrassment-driven development
I am quite embarrassed that I haven't thought of this, but you are totally right, if it includes lud16, we can totally use that to setup receive haha
lol I had to deeply suck air in when I read this
I wish we could use the same connection for both but no.
Maybe I will have some suggestions for the spec, because the UX around permissions is by far the biggest pain point when it comes to NWC.