Rizful.com (zap tester) on Nostr: Testing zaps for this note… we made seven attempts to⚡zap this note, at ...
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.
Published at
2025-03-31 15:43:05Event JSON
{
"id": "7ca6e61de1fd6a2f05702357fa0ac047127a3bc9183ebd81711dee2b27507458",
"pubkey": "3516193f50715b4f12d7bbf03d14add45983be819330c1e1196fa917f63fa955",
"created_at": 1743435785,
"kind": 1,
"tags": [
[
"e",
"6f54a646e35cce296e2e2bc98fc97195966f2a4ab94fe978e1131826a00b6433",
"wss://nostr.mom",
"root",
"262c8090db5247a9fb253c8b180799a688b2a857e0bb17d6bf372ba51324d49b"
],
[
"e",
"6c262491623f826bc9919bf378d4fa0bee8aca805c8bd3dd67762c1a0673b02d",
"wss://nostr.mom",
"reply",
"0e432913100161e8c4c06d554f26f7606a2e71988f2f6575ed165ddc31711594"
],
[
"p",
"262c8090db5247a9fb253c8b180799a688b2a857e0bb17d6bf372ba51324d49b"
],
[
"p",
"0e432913100161e8c4c06d554f26f7606a2e71988f2f6575ed165ddc31711594"
]
],
"content": "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.",
"sig": "d7a178ffc6c65b5eafbf26722dc2524a8a71903dab79b81bddc18f20ec877d50fda9a75afea075eec477505e7eebd47a2b4cfd5a7d8332bca3d7e29d0095d448"
}