I did it for our relay, and also added an improvement to our LNURL server that makes seeing received zaps even more bulletproof, even if other people's relays don't fix it:
quotingI just deployed a few things that I was working on over the last week, and some of them should make the zapping experience with the Kosmos relay and Lightning accounts/addresses a bit faster and more consistent:
nevent1q…jpp7
1. When we zap someone to a non-Kosmos Lightning address, their server is now able to post the receipt back to our members-only relay.
2. When someone who's not using our relay zaps us, our accounts server publishes the receipt to the non-member's requested relays, but it will also publish it to our own relay in addition to theirs.
This means that we now reliably (and quickly) see all incoming and outgoing zaps in all of our clients, especially when other people's relay lists don't overlap with ours.
I think everyone running members-only or paid relays should implement a similar policy for allowing zap receipts to be published for their own users' outgoing zaps. Here's the relevant code in our own policy:
https://gitea.kosmos.org/kosmos/akkounts/pulls/197/files#diff-cc5c58329fae4e65a47568a691835d6d14ab236a
If someone spots a mistake, or this is generally a bad idea for some reason, please let me know! 🙏
#nostr