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

nprofile1qqsr29se8ag8zk60zttmhupazjkagkvrh6qexvxpuyvkl2gh7cl6j4gpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgawaehxw309a3x7um5wghxy6t5vdhkjmn50phkkmewvdhk6tc57rkdv

Publishing to

relay.nostr.band

bostr.bitcointxoko.com

basedpotato.nostr1.com

Author Public Key

npub1x5tpj06sw9d57ykhh0cr699d63vc805pjvcvrcged7530a3l492sdy55am

Show more details

Last Notes

2025-03-31 15:43:05

- reply

Testing zaps for this note… we made seven attempts to⚡zap this note, at peacock@nostrich.house, over a period of 14 minutes. Two 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.) We recommend that you use a always-on, cloud-based Lightning node to get more reliable zaps.

2025-03-31 15:41:12

- reply

We tested zaps on this note… we made seven attempts to⚡zap this note, using your lightning address starting with "sikto", over a period of 12 minutes. One 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 be that your node WAS online, but did not have sufficient inbound capacity to receive payments. We recommend that you use a always-on, cloud-based Lightning node to get more reliable zaps.

2025-03-29 22:31:37

- reply

We did some zap tests on this note… we made five attempts to⚡zap this note, at zap@ikuradon.id, over a period of 4 minutes. 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 be that your node WAS online, but did not have sufficient inbound capacity to receive payments. We recommend that you use a always-on, cloud-based Lightning node to get more reliable zaps.

2025-03-29 22:01:14

- reply

hey, we tried to ⚡zap this note at at transition_news_press@nostrid.info, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it... we recommend a cloud-based Lightning node for highest reliability.

2025-03-29 22:01:08

- reply

hey, we tried to ⚡zap this note at at floppy@joinstr.xyz, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it... we recommend a cloud-based Lightning node for highest reliability.

2025-03-29 21:59:39

- reply

hey, we tried to ⚡zap this note at at petr@zapforlife.com, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it... we recommend a cloud-based Lightning node for highest reliability.

2025-03-29 21:45:02

- reply

Zap test on this note… we made seven attempts to⚡zap this note, at insertzaphere@minibits.cash, over a period of about 13 hours. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 5510ms (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 inbound zap latency.

2025-03-29 21:44:37

- reply

We did some zap tests on this note… we made seven attempts to⚡zap this note, at ch0meji@w.bitcoinhold.net, over a period of about 13 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://w.bitcoinhold.net/BTC/UILNURL/pay/lnaddress/ch0meji.) 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-03-29 21:43:37

- reply

Zap test on this note… we made seven attempts to⚡zap this note, at lutxo@minibits.cash, over a period of about 13 hours. All seven attempts were successful. You should check on your end to be sure you received these. 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 inbound zap latency.

2025-03-29 21:43:33

- reply

Zap test on this note… we made seven attempts to⚡zap this note, at serenitys_forge@getalby.com, over a period of about 13 hours. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 4508ms (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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.

2025-03-29 21:22:15

- reply

We did some zap tests on this note… we made three attempts to⚡zap this note, at btcessex@fountain.fm, 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://api.fountain.fm/v1/lnurlp/btcessex/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-03-29 21:20:49

- reply

Zap test on this note… we made seven attempts to⚡zap this note, at mananguri@onlynostr.club, over a period of 34 minutes. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 6026ms (6.0 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 inbound zap latency.

2025-03-29 21:19:36

- reply

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

2025-03-29 21:16:08

- reply

Testing for this note… we made seven attempts to⚡zap this note, at cosmicchronicle@wallet.yakihonne.com, over a period of 40 minutes. All seven attempts were successful. Average zap time was 7052ms (7.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.

2025-03-29 21:13:33

- reply

We did some zap tests on this note… we made seven attempts to⚡zap this note, at lonewolf@zeuspay.com, over a period of 41 minutes. 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. We recommend that you use a always-on, cloud-based Lightning node to get more reliable zaps.

2025-03-29 07:50:52

- reply

We tested zaps on this note… we made seven attempts to⚡zap this note, at isabelsydow@getalby.com, over a period of 3 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/isabelsydow/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-03-29 07:40:38

- reply

hey, we tried to ⚡zap this note at at potaspotja@sotalive.net, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it...

2025-03-29 07:29:19

- reply

Testing zaps on this note… we made seven attempts to⚡zap this note, at karo-l@ln.bitdevs.tw, over a period of 10 minutes. All seven attempts were successful. Average zap time was 3811ms (3.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.

2025-03-28 22:45:16

- reply

hey, we tried to ⚡zap this note at at uchijo@www.uchijo.com, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it...

2025-03-28 00:34:38

- reply

hey, we tried to ⚡zap this note at at nonce@nostrdice.com, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it...

2025-03-28 00:33:27

- reply

Testing zaps on this note… we made six attempts to⚡zap this note, at hzrd1499@minibits.cash, over a period of 10 minutes. All six attempts were successful. Average zap time was 5663ms (5.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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to maximize inbound zap speed.

2025-03-28 00:33:21

- reply

We tested zaps and zap receipts on this note… we made seven attempts to⚡zap this note, at bhg@btcpay.bitcoinhatguy.com, over a period of 22 minutes. Seven of the zaps were successfully paid... Please check for 7 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-03-27 23:35:21

- reply

Testing for this note… we made seven attempts to⚡zap this note, at doshitters@getalby.com, over a period of 2 minutes. All seven attempts were successful. Average zap time was 4025ms (4.0 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 maximize inbound zap speed.

2025-03-27 23:31:00

- reply

Zap test on this note… we made seven attempts to⚡zap this note, at hermeticvm@minibits.cash, over a period of 5 minutes. All seven attempts were successful. Average zap time was 5433ms (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 maximize inbound zap speed.

2025-03-27 09:30:44

- reply

Testing for this note… we made seven attempts to⚡zap this note, at duhlaurien@getalby.com, over a period of 5 minutes. All seven attempts were successful. Average zap time was 7030ms (7.0 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 maximize zap speed.

2025-03-26 09:04:49

- reply

Testing for this note… we made seven attempts to⚡zap this note, at diffract@getalby.com, over a period of 1 minute. All seven attempts were successful. Average zap time was 3521ms (3.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 maximize zap speed.

2025-03-26 09:02:02

- reply

Testing for this note… we made seven attempts to⚡zap this note, at evelin@getalby.com, over a period of 1 minute. All seven attempts were successful. Average zap time was 4407ms (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.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to maximize zap speed.

2025-03-26 08:34:09

- reply

Zap test on this note… we made seven attempts to⚡zap this note, at plantimals@getalby.com, over a period of 16 minutes. All seven attempts were successful. Average zap time was 4165ms (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 maximize zap speed.

2025-03-26 00:00:11

- reply

We tested zaps and zap receipts on this note… we made seven attempts to⚡zap this note, at lawlessopera62@minibits.cash, over a period of 6 minutes. Seven of the zaps were successfully paid... Please check for 7 satoshis received. However, we did find that only three 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.... your average zap time was 4566ms (4.6 seconds). We consider this zap time slow... generally, zaps should take under two seconds. (If time is too slow, other Nostr users might think your zaps are broken, might not zap you again.) We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-03-25 23:59:11

- reply

Testing zaps for this note… we made seven attempts to⚡zap this note, at pancakelighthearted414305@getalby.com, 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/pancakelighthearted414305/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-03-24 04:18:39

- reply

Testing zap receipts for this note… we made five attempts to⚡zap this note, at melvincarvalho@btip.nl, over a period of 3 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.... also FYI... your server at btip.nl is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 3033ms (3.0 seconds). We consider this slow... generally, zap invoices should be created in under one second. We recommend that you use a cloud-based Lightning node to get more reliable zaps.

2025-03-24 03:57:06

- reply

Testing for this note… we made five attempts to⚡zap this note, at rovinguser653@minibits.cash, over a period of 3 minutes. All five attempts were successful. Average zap time was 4255ms (4.3 seconds). We consider this zap time slow... generally, zaps should take 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 maximize zap speed.

2025-03-23 22:01:09

- reply

Missing this part of the spec. https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-e-zap-receipt-event

2025-03-23 21:59:17

- reply

Just tested again. Still looks like your zap implementation is not producing zap receipts. That’s why there is no number next to the zap symbol after u get zapped.

2025-03-23 21:30:56

- reply

hey, we tried to ⚡zap this note at at ynniv@ynniv.com, but it seems this lightning address isn't working... just wanted to give you a heads up in case you would like to fix it...

2025-03-23 21:18:36

- reply

Testing zap receipts for this note… we made five attempts to⚡zap this note, at lnd@node.davidebtc.me, over a period of 9 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 set up a proper lightning node to get more reliable zaps.

2025-03-23 17:58:11

- reply

Testing zap receipts for this note… we made six attempts to⚡zap this note, at c1f9e9@wallet.yakihonne.com, over a period of 35 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. This is a problem because the user who zapped you would NOT see an actived ⚡icon after zapping. They might think the zap failed, and therefore might not zap you again. Zap timing: Average zap time was 9388ms (9.4 seconds). We consider this zap time slow... generally, zaps should take under two seconds. (If time is too slow, other Nostr users might think your zaps are broken, might not zap you again.) We recommend that you set up a proper lightning node to get more reliable zaps.

2025-03-23 17:12:53

- reply

We did some zap tests on this note… we made seven attempts to⚡zap this note, at rand@zap.sovbit.host, over a period of 10 minutes. Seven of the zaps were successfully paid... Please check for 7 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.... This is not ideal behavior. You might want to think about switching to an always-on lightning node, to receive zaps.

2025-03-23 01:45:00

- reply

We tested zaps and zap receipts on this note… we made seven attempts to⚡zap this note, at ryand@getalby.com, over a period of about 8 hours. Six of the zaps were successfully paid, meaning you should have received a total of six satoshis over this time. However, we did find that only one of the payments produced zap receipts. Why does this matter? Basically, when your side fails to send a zap receipt, the zapping user would not see an actived ⚡icon after zapping. This means they might think the zap failed, and therefore might not zap you again. This is not ideal behavior. You might want to think about switching to an always-on lightning node, to receive zaps.

2025-03-21 22:15:20

- reply

hey, we tried to ⚡zap this note at etherfi@iris.to but it seems this lightning address isn't working... lmk if we can help u set it up

2025-03-20 18:37:15

- reply

test comment