Always is…

Gm

Now that I am accepting zaps to my own lightning node, need to build this son of a gun back up and make it more reachable. I'm glad I use some LSP's as well because I've been having some payment issues this morning and they certainly helped move things along. For those considering running their own node, I highly recommend it. However, it's essential to be mindful of the trade-offs involved. Additionally, having alternative payment methods in place is crucial to navigate any potential issues smoothly.

Wrote a script to seek out old/problematic versions of a kind 3 contact list and so far have found about 25 relays that are storing versions of a contact list with an empty relay section and even more that are storing a very old version of my contact list. This could very likely be the cause of the weird relay behavior I recently experienced on Damus. Need to keep plugging away and figure out what is going on here and see if I can track this down to a particular client.

My relays keep disappearing from Damus, all of them. Sometimes this is fixed by signing out then back in, the 4 bootstrap relays will appear, then a few hours later back to 0 relays? This happening to anyone else? I'm using several other clients and they don't seem to be experiencing the same behavior.

Long overdue, but I made a simple, easy to setup NIP-57 server to serve LN invoices and accept Zaps to your Lightning node running on Tor. This is just one of many non-custodial solutions available for receiving zaps on nostr, that comes with some trade-offs listed in the documentation. This is more geared towards tinkerers who already run a node at home and are comfortable/interested running a separate server, this can be run on a $5 a month VPS. I encourage anyone who is interested to try it out and provide feedback. Happy zapping! ⚡️⚡️⚡️⚡️

GitHub

GitHub - UTXOnly/zap_server: An LNURL server to fetch invoices from a tor hosted Bitcoin lightning node, specifically made for NOSTR zaps

An LNURL server to fetch invoices from a tor hosted Bitcoin lightning node, specifically made for NOSTR zaps - UTXOnly/zap_server

Are you able to generate a Zap invoice for this note? I have made a LUD-16 identifier and a LNURL server to accept zaps on my own node. This is working without issue on Snort but the zap button is grayed out on other clients. I can see in my server logs that the other clients are reaching the LNURL server, server returns a 200 response along with the proper callback URL but can't seem to even request an invoice from the LNURL server or attempt to generate one in the nostr client for that matter. Do other clients handle zaps/requesting invoices differently? About to go digging through some repos as I haven't found anything useful in console logs, but wanted to see if I am missing a well known limitation or something?