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.

Reply to this note

Please Login to reply.

Discussion

You can just use the email-style address.

Would be easier

You’ll get something that looks like:

0x3e91adaee25215f4@ln.tips

I pasted it properly this time. It seems to be working. Thanks #[3]

Yep! Worked for me. ⚡️💯🤙

Thanks #[3]

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.

Added #[3] Thank you for the sats😀

Awesome, can confirm your ln.tips lnurl is all set up to support nip-57 zaps now. Good work ser!

Thank you for the tech support😀🤙🏻

Pura vida mae!

Anytime!