Rizful.com (zap tester)

Rizful.com -- 🏠 Your home base for⚡zaps.

Get a Lightning Node for highly reliable zaps ... rizful.com

Created by the team behind The Megalith Node, one of the biggest nodes on the Lightning Network.

Public Key

npub1x5tpj06sw9d57ykhh0cr699d63vc805pjvcvrcged7530a3l492sdy55am

NIP-05 Address

zap-tester@rizful.com

NIP-57 Address

zap-tester@rizful.com

Profile Code

nprofile1qqsr29se8ag8zk60zttmhupazjkagkvrh6qexvxpuyvkl2gh7cl6j4gpr4mhxue69uhkymmnw3ezucnfw33k76tww3ux76m09e3k7mf0qywhwumn8ghj7cnpwdjkgur0w3shgmewdehhxarjxyhxxmmd9uccu3cp

Publishing to

bostr.bitcointxoko.com

basedpotato.nostr1.com

Author Public Key

npub1x5tpj06sw9d57ykhh0cr699d63vc805pjvcvrcged7530a3l492sdy55am

Show more details

Last Notes

2025-04-23 16:19:30

- reply

Thanks, will check it out. FWIW, my understanding is that the "route finding" algos of the major Lightning implementations don't yet take "speed" (i.e. payment latency) into consideration.

2025-04-18 21:21:23

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at themptyuniverse@zeusnuts.com, over a period of about 4 hours. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5943ms (5.9 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.

2025-04-16 23:00:40

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at hugmoon@vipsats.app, over a period of about 5 hours. 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.

2025-04-16 18:04:27

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at zen@credenso.cafe, over a period of 44 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.

2025-04-16 17:51:53

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at david@bitcoin-is-digital.gold, over a period of about 4 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/cookieradiant380229/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.

2025-04-15 23:42:09

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at naranja@lawallet.ar, over a period of 25 minutes. Six of the zaps were successfully paid... Please check for 6 satoshis received. However, we did find that only five of the payments produced zap receipts in time for our server to recognize them. This is a problem because the user who zapped you would NOT see an active ⚡icon after zapping. They might think the zap failed, and therefore might not zap you again.... Also.... your average zap time was 5192ms (5.2 seconds). We consider this zap time slow... if possible, zaps should be confirmed in under two seconds. (If time is too slow, other Nostr users might think your zaps are broken, might not zap you again.) You might want to look into using a cloud-based Lightning node to get more reliable zaps.

2025-04-15 23:40:30

- reply

Testing for this note… we made six attempts to⚡zap this note, using your lightning address starting with "zaawaadi", 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 6905ms (6.9 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.

2025-04-15 22:06:50

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at petar@21million.fun, 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.

2025-04-15 22:05:53

- reply

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.

2025-04-15 22:05:19

- reply

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.

2025-04-15 22:04:50

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at coffeeman@lawallet.ar, 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 5528ms (5.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.

2025-04-15 22:04:21

- reply

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.

2025-04-15 22:03:43

- reply

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.

2025-04-15 22:03:19

- reply

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at x@lnaddress.com, over a period of 39 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.

2025-04-15 22:03:03

- reply

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.

2025-04-15 22:02:18

- reply

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.

2025-04-15 22:01:48

- reply

Testing for this note… we made six attempts to⚡zap this note, at inpc@wallet.yakihonne.com, 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 8716ms (8.7 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.

2025-04-15 22:00:53

- reply

Zap test on this note… we made six attempts to⚡zap this note, at guarrilla@lawallet.ar, 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 4985ms (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.

2025-04-15 22:00:19

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at chadwick@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 4668ms (4.7 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.

2025-04-15 21:59:59

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at dgy7@lawallet.ar, over a period of about 1 hour. Six of the zaps were successfully paid... Please check for 6 satoshis received. However, we did find that only five of the payments produced zap receipts in time for our server to recognize them. This is a problem because the user who zapped you would NOT see an active ⚡icon after zapping. They might think the zap failed, and therefore might not zap you again.... Also.... your average zap time was 5649ms (5.6 seconds). We consider this zap time slow... if possible, zaps should be confirmed in under two seconds. (If time is too slow, other Nostr users might think your zaps are broken, might not zap you again.) You might want to look into using a cloud-based Lightning node to get more reliable zaps.

2025-04-15 21:59:25

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at seymour@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.

2025-04-15 21:58:39

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at savethebees@lnmarkets.com, 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.

2025-04-15 21:58:10

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at greg.tonoski@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.

2025-04-15 21:57:44

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at qlmar@seewaan.com, 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.

2025-04-15 18:28:36

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at cryptoborshch@speed.app, over a period of 5 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.

2025-04-15 05:04:22

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at dobkun@zaps.lol, over a period of 4 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.

2025-04-15 05:03:34

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at agilereason397@minibits.cash, over a period of 6 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4485ms (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.

2025-04-15 05:02:19

- reply

Testing for this note… we made six attempts to⚡zap this note, at kuzushi@minibits.cash, over a period of 5 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4474ms (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.

2025-04-15 05:01:24

- reply

Zap test on this note… we made six attempts to⚡zap this note, at nostudal@minibits.cash, over a period of 7 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4360ms (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.

2025-04-15 05:00:59

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, at anonymous@nostrplebs.com, over a period of 5 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.

2025-04-15 05:00:09

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at cloudy@nos.social, over a period of 5 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.

2025-04-14 22:13:29

- reply

Yes our testing indicates that most or all SpeedWallet users do not generate zap receipts.

2025-04-14 04:03:07

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "murawaki", 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/murawaki/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.

2025-04-14 04:02:06

- reply

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.

2025-04-14 01:45:16

- reply

Testing for this note… we made six attempts to⚡zap this note, at kittay@wallet.yakihonne.com, 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 8404ms (8.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.

2025-04-14 00:22:24

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at ancientwarrior.147111@nostr.com, over a period of about 2 hours. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4288ms (4.3 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.

2025-04-14 00:20:36

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "grover", over a period of 29 minutes. 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/grover/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.

2025-04-13 20:51:41

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at zap@semisol.dev, over a period of about 4 hours. Six of the zaps were successfully paid... Please check for 6 satoshis received. However, we did find that only three of the payments produced zap receipts in time for our server to recognize them. This is a problem because the user who zapped you would NOT see an active ⚡icon after zapping. They might think the zap failed, and therefore might not zap you again.... Also.... your average zap time was 37483ms (37.5 seconds). We consider this zap time slow... if possible, zaps should be confirmed in under two seconds. (If time is too slow, other Nostr users might think your zaps are broken, might not zap you again.) You might want to look into using a cloud-based Lightning node to get more reliable zaps.

2025-04-13 20:51:30

- reply

Zap test on this note… we made six attempts to⚡zap this note, at b2db27@wallet.yakihonne.com, over a period of about 4 hours. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 8274ms (8.3 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.

2025-04-13 20:51:26

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at desiboard@thevikas.com, over a period of about 4 hours. 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. 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.

2025-04-13 16:49:32

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at mrbtc1@lifpay.me, 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://lifpay.me/api/ln/lnurl/payreq/mrbtc1_244814 ). Your server did not produce an invoice, thus the zap failed. The error we got was "Receive or send bitcoin is currently unavailable, please refer to announcement. ". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-13 16:49:29

- reply

Testing for this note… we made six attempts to⚡zap this note, at thekalimerashow@wallet.yakihonne.com, over a period of about 2 hours. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 8228ms (8.2 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.

2025-04-13 16:47:29

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at twofaktor@btcpay.minibolt.info, over a period of about 2 hours. Five of the zaps were successfully paid... Please check for 5 satoshis received. However, we did find that only two of the payments produced zap receipts. This is a problem because the user who zapped you would NOT see an active ⚡icon after zapping. They might think the zap failed, and therefore might not zap you again.... also FYI... your server at btcpay.minibolt.info is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 12623ms (12.6 seconds). We consider this slow... generally, zap invoices should be created in under one second. Also.... your average zap time was 25799ms (25.8 seconds). We consider this zap time slow... if possible, zaps should be confirmed in under two seconds. (If time is too slow, other Nostr users might think your zaps are broken, might not zap you again.) You might want to look into using a cloud-based Lightning node to get more reliable zaps.

2025-04-13 16:47:23

- reply

Zap test on this note… we made six attempts to⚡zap this note, at tincho70@lawallet.ar, over a period of about 2 hours. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 6280ms (6.3 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.

2025-04-13 05:18:40

- reply

Zap test on this note… we made six attempts to⚡zap this note, at begum@nostrich.house, over a period of 38 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 8865ms (8.9 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.

2025-04-13 05:16:00

- reply

Testing for this note… we made six attempts to⚡zap this note, at rice@nostrich.house, over a period of 38 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5818ms (5.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.

2025-04-13 04:16:50

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "daryncavalier", over a period of about 3 hours. Zero of the zaps were successfully paid... Your server did produce invoices, however, we were unable to successfully pay the invoices. It may be that your node or wallet service was offline at the time we attempted the zaps. The actual error we got was 'route not found'... which is an unfortunately vague error that Lightning payments sometimes produce. This means our payment node could not find a path to your node. (It could also be that your node was online at the time of payment, but did not have sufficient inbound capacity to receive payments.) You might want to look into using an always-on, cloud-based Lightning node to get more reliable zaps.

2025-04-13 04:14:27

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at xinomo@blixtwallet.com, over a period of about 3 hours. 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.... also FYI... your server at blixtwallet.com is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 2677ms (2.7 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.

2025-04-13 04:14:21

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at qq1649095@iris.to, over a period of about 3 hours. 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.

2025-04-12 16:50:06

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at clayslingingsensei@primal.com, over a period of 37 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.

2025-04-12 16:47:47

- reply

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at zwegen@sats.mobi, 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** 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.

2025-04-12 14:42:48

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, using your lightning address starting with "andrewflows", over a period of 9 minutes. 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/andrewflows/callback ). Your server did not produce an invoice, thus the zap failed. The error we got was "Could not create lightning invoice. The recipient potentially lacks receiving capacity?". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-12 05:25:51

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, at npub13ytn4m4x3mg0v3ey6ylkw69u033n9zlrdg7f2s04zvtmrqa52z9sedtyky@nost.vip, over a period of 11 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.

2025-04-12 04:44:31

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "captjack", over a period of 19 minutes. 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/captjack/callback ). Your server did not produce an invoice, thus the zap failed. The error we got was "Could not create lightning invoice. The recipient potentially lacks receiving capacity?". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-12 02:02:51

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at blockdyor@cosanostr.com, over a period of 18 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.

2025-04-11 04:24:01

- reply

Testing for this note… we made six attempts to⚡zap this note, at logen@lightning.btcforplebs.com, over a period of 20 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 6615ms (6.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.

2025-04-11 03:45:52

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "takeitez", over a period of 14 minutes. 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/takeitez/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.

2025-04-11 03:45:48

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, using your lightning address starting with "scalebar", over a period of 15 minutes. 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/scalebar/callback ). Your server did not produce an invoice, thus the zap failed. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-11 03:44:26

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "lectio", over a period of 13 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.... also FYI... your server at using your lightning address starting with "lectio" is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 2183ms (2.2 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.

2025-04-11 03:44:20

- reply

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at donate@btcpay.start9.com, over a period of 26 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.

2025-04-11 03:42:51

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "nodenation", over a period of 8 minutes. 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/nodenation/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.

2025-04-11 03:42:48

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at _@4rs.nl, over a period of 11 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.

2025-04-11 03:42:43

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at zap@danielwonder.com, over a period of 10 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4149ms (4.1 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.

2025-04-11 02:46:13

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, at saleh@ditoo.pub, 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.

2025-04-09 04:03:01

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at lhasasensei@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 5946ms (5.9 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.

2025-04-09 04:02:32

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, at craig@zap.bitcoin-cats.ca, 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://zap.bitcoin-cats.ca/BTC/UILNURL/pay/lnaddress/Craig ). Your server did not produce an invoice, thus the zap failed. The error we got was "Lightning node could not generate invoice with description hash: The HTTP status code of the response was not expected (500).". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-08 23:53:21

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "paulochinho", 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/paulochinho/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.

2025-04-08 20:55:30

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, at nobsbitcoin@geyser.fund, over a period of 21 minutes. 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://api.geyser.fund/.well-known/lnurlp/nobsbitcoin ). Your server did not produce an invoice, thus the zap failed. The error we got was "Could not generate a lightning invoice for this project". You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-08 18:45:25

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at yael@vlt.ge, over a period of 9 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4175ms (4.2 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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-07 20:05:11

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "ches", over a period of 28 minutes. 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/ches/callback ). Your server did not produce an invoice, thus the zap failed. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-07 19:54:22

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "nomishka", 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** 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.

2025-04-07 19:53:25

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "serendipityautumn764925", 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/serendipityautumn764925/callback ). Your server did not produce an invoice, thus the zap failed. You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-07 18:49:17

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, using your lightning address starting with "rcc", over a period of 15 minutes. 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/rcc/callback.) Your server did not produce an invoice, thus the zap failed. The error we got was "Could not create lightning invoice. The recipient potentially lacks receiving capacity?" You might want to look into using a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-07 18:45:02

- reply

Testing for this note… we made six attempts to⚡zap this note, at garrett@minibits.cash, over a period of 12 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5590ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-07 18:30:36

- reply

Zap test on this note… we made three attempts to⚡zap this note, at majje@minibits.cash, over a period of 10 minutes. All three attempts were successful. Please check on your end to be sure you received. Average zap time was 5580ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-06 19:56:33

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, using your lightning address starting with "notoshi", over a period of 20 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 7453ms (7.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-06 18:40:06

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at sime@21m.lol, over a period of 28 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-06 18:30:55

- reply

We tested zaps on this note… we made six attempts to⚡zap this note, at btcmagician@stacker.news, over a period of 33 minutes. 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://stacker.news/api/lnurlp/BTCMagician/pay.) Your server did not produce an invoice, thus the zap failed. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-06 14:26:29

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at poetix@speed.app, over a period of about 10 hours. 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-06 14:03:15

- reply

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at hello@ln.peachbitcoin.com, over a period of 11 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-06 14:03:08

- reply

Testing for this note… we made six attempts to⚡zap this note, at jdo@wallet.yakihonne.com, over a period of 14 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 6917ms (6.9 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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-06 14:01:34

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "blockchainyogi", over a period of 14 minutes. 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/blockchainyogi/callback.) Your server did not produce an invoice, thus the zap failed. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:38:56

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at headstash@lnbc.cz, over a period of 15 minutes. In each case, we found that your lightning address server did not respond correctly. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:38:54

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at jimbocoin@btcpay175473.lndyn.com, over a period of 23 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-05 23:38:51

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, using your lightning address starting with "blossomdivine827615", over a period of 16 minutes. 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/blossomdivine827615/callback.) Your server did not produce an invoice, thus the zap failed. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:38:46

- reply

Zap test on this note… we made six attempts to⚡zap this note, using your lightning address starting with "the4str0n4ut", over a period of 25 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 4937ms (4.9 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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:37:42

- reply

We tested zaps and zap receipts on this note… we made six attempts to⚡zap this note, at brent19@speed.app, over a period of 19 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-05 23:37:37

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at justinanon@speed.app, over a period of 29 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-05 23:36:23

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at asyncmind@asyncmind.xyz, over a period of 27 minutes. Five of the zaps were successfully paid... Please check for 5 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.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-04-05 23:36:10

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at pedromvpg@btcpay989117.lndyn.com, over a period of 19 minutes. 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://btcpay989117.lndyn.com/BTC/UILNURL/pay/lnaddress/pedromvpg.) Your server did not produce an invoice, thus the zap failed. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:36:04

- reply

Testing for this note… we made six attempts to⚡zap this note, at dawn@minibits.cash, over a period of 16 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5415ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:34:59

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at bkeeper@minibits.cash, over a period of 30 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5381ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:34:57

- reply

Testing for this note… we made six attempts to⚡zap this note, at hazey@minibits.cash, over a period of 20 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5600ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:34:52

- reply

Testing for this note… we made six attempts to⚡zap this note, at twofish@minibits.cash, over a period of 22 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 7466ms (7.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:34:49

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at _@ordisrespector.com, over a period of 25 minutes. In each case, we found that your lightning address server did not respond correctly. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:34:45

- reply

Testing for this note… we made six attempts to⚡zap this note, at silvertepee776@minibits.cash, over a period of 31 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5201ms (5.2 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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:34:42

- reply

We did some zap tests on this note… we made six attempts to⚡zap this note, at garrett@renderbitcoin.com, over a period of 24 minutes. In each case, we found that your lightning address server did not respond correctly. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:33:20

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, using your lightning address starting with "graciouspassion61883", over a period of 20 minutes. 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/graciouspassion61883/callback.) Your server did not produce an invoice, thus the zap failed. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.

2025-04-05 23:33:11

- reply

Testing for this note… we made six attempts to⚡zap this note, at ronin@minibits.cash, over a period of 32 minutes. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5530ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce your latency.

2025-04-05 23:33:06

- reply

Testing zaps for this note… we made six attempts to⚡zap this note, at c.lacdael@poetry.me.uk, over a period of 31 minutes. In each case, we found that your lightning address server did not respond correctly. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.