Gm. Your minimum zap is ⚡️43. That’s going to reduce your zapability potential.
Discussion
The minimum zap for Strike users is $0.01 USD. So right now it’s 43 sats, maybe not tomorrow though.
I see. Trying to see if I can switch to LN.TIPS🙏🏻
It’s easy. You can even type /nostr add [your npub] now and it should give you the address to use.
Tried it. Didn’t work for me.
What happened when you typed /help or /advanced — it should give you a lighting address and LNURL to put in your profile.
I copied and pasted the anonymous LNURL that was provided to me after the /advanced
Paste it here and I’ll test it.
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.
Your LNURL on your nostr profile has spaces in it right now `LNURL1DP68GURN8GHJ7MRW 9E6XJURN9UH8WETVDSKKKM NOWAHZZMRWW4EXCUPOXPUR 2CF5V3JRSDR9X4SK2VRXX3 INZSOTE5H`. It shouldn’t have any spaces. Also even without spaces it doesn’t decode…
Yeah, the formatting got messed up. Try deleting it and adding it again. Make sure you copy exactly what it gives you.
Not a 43 fan, Daniel, but I couldn’t figure out how to change it in Strike.😀
