Testing zaps for this note… we made six attempts to⚡zap this note, at gothicmonk@nos.social, over a period of about 1 hour. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at satoshi@btcpay.theunschooled.net, over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

We did some zap tests on this note… we made six attempts to⚡zap this note, at dave@dtrt.org, over a period of about 1 hour. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at just-on@speed.app, over a period of 41 minutes. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "mr_greengold", over a period of about 1 hour. In each case, we found that your lightning address server did not respond correctly. (The failure point was when we did a GET request to your specified callback URL: https://getalby.com/lnurlp/mr_greengold/callback ). Your server did not produce an invoice, thus the zap failed. The error we got was "Invalid amount. Make sure the amount is within the range.". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

Testing zaps for this note… we made six attempts to⚡zap this note, at tickerbell@xport.top, over a period of about 1 hour. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

Testing zap receipts for this note… we made six attempts to⚡zap this note, at anon@anon.dev, over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... also FYI... your server at anon.dev is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 2536ms (2.5 seconds). We consider this slow... generally, zap invoices should be created in under one second. You might want to look into using a cloud-based Lightning node to get more reliable zaps.

We did some zap tests on this note… we made six attempts to⚡zap this note, at avaledwindsail@iris.to, over a period of about 1 hour. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

Testing for this note… we made six attempts to⚡zap this note, at robinson@nostrich.house, over a period of 21 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4618ms (4.6 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.

Testing zaps on this note… we made six attempts to⚡zap this note, at valderdama@minibits.cash, over a period of about 1 hour. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4574ms (4.6 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "longextraordinaire", over a period of 31 minutes. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

Testing for this note… we made six attempts to⚡zap this note, at dyer@nostrich.house, over a period of about 1 hour. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4432ms (4.4 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at mags@pay.bbw.sv, over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

We did some zap tests on this note… we made six attempts to⚡zap this note, at professor_anna@speed.app, over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

We tested zaps on this note… we made six attempts to⚡zap this note, at _@bitcointreasuries.net, over a period of 34 minutes. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

Testing zap receipts for this note… we made six attempts to⚡zap this note, using your lightning address starting with "gonegone", over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

Testing zaps for this note… we made six attempts to⚡zap this note, at farmerboy@mutiny.plus, over a period of about 1 hour. In each case, we found that your lightning address server did not respond correctly. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at soc@hivetalk.org, over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (The zap spec requires that the zap receipts be sent to the relays specified in the zap.) This means a Nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

Testing zaps on this note… we made six attempts to⚡zap this note, at lyons@nostrich.house, over a period of about 1 hour. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4752ms (4.8 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.

Zap test on this note… we made six attempts to⚡zap this note, at sachin@minibits.cash, over a period of about 1 hour. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4490ms (4.5 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "thevoidstaresback", over a period of about 2 hours. In each case, we found that your lightning address server did not respond correctly. (The failure point was when we did a GET request to your specified callback URL: https://getalby.com/lnurlp/thevoidstaresback/callback ). Your server did not produce an invoice, thus the zap failed. The error we got was "Recipient wallet error. Please contact the recipient.". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at nostr@cguida.io, over a period of 24 minutes. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not** produce any zap receipts. This means that nobody else could see see that you got zapped... no number appears next to the ⚡icon after zapping.... You might want to look into using a cloud-based Lightning node to get more reliable zaps.

We're using this separate Nostr profile to perform zap testing! Please use our main profile nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq for all communication!