Hey nostr:npub1c6fgvvw7mpa404m23zzm32y57enfu3sqgn3ayzsxp3ahpynljqwsc5v4pd is this yours?

https://lnbeats.com/album/a3fbb5e6-a7d3-542d-995f-ec948e3c7538

if so the lightning address part in your feed needs fixed. If your using Alby your feed needs to look like the bottom pic with the node, custom key, custom value etc..

nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9

Seems to be working... The value block area of sovereign feeds is a bit different now. Is Keysend going away? It recognized that it was a lightning address... Maybe Mr B can explain.

Reply to this note

Please Login to reply.

Discussion

Well... I tested a few apps and couldn't get it to work... but something came through from an anonymous user. App unknown... still running with scissors...

Most of the PC2.0 apps don't support lnaddress yet. If you have a wallet that supports keysend, which Alby does, you should choose keysend (or node) so you can get all of the metadata that keysend allows us to attach.

You can use lnaddress, but a lot of the apps will fail with their payments until they get around to supporting lnaddress.

I've changed SF back to default to using keysend, since you're not the first one to be confused by the changes.

I also have a question about the value block page in SF. I'm moderately confused about the different sections. Add new split vs add new fee. Sorry if this has already been explained a thousand times.