Paste it here and I’ll test it.
Discussion
TeamBTC’s nostr profile is showing “LNURL1DP68GURN8GHJ7MRW 9E6XJURN9UH8WETVDSKKKM NOWAHZZMRWW4EXCUPOXPUR 2CF5V3JRSDR9X4SK2VRXX3INZSOTE5H”. It has spaces in it, which is no bueno. Also, without the spaces, it doesn’t decode. It looks like a bad copy/paste job.
You’re right. I butchered the copy & paste. I think it’s working now.
Thanks for the help #[3]
I think there’s one more thing you have to do in your Lightning Tip Bot … run this command
/nostr add npub1j7xg7fh2nv793075erwlm6phgxnvyjt04de8wsgflergr89yjuyqj8lafh
I never had to do that and it always worked.
If you don’t do that, then ln.tips LNURL response won’t include the NIP-57 required fields of `allowsNostr` and `nostrPubkey`. So, without adding your nostr pubkey to ln.tips bot, you can still receive sats over lightning network, but they are not NIP-57 Zaps. This means they won’t show up in your nostr client.
