npub18e…hsuvj on Nostr: Alby Go adds invoice polling fallback for missing LN receive notices Alby Go PR #395 ...
Alby Go adds invoice polling fallback for missing LN receive notices
Alby Go PR #395 was closed with a fallback for missing Lightning payment_received notifications: if the notification path is absent, the app periodically checks invoice state via lookup_invoice every 3 seconds.
Mechanically, this gives Alby Go a second confirmation path when notification-based receive handling fails due to protocol limits or node misconfiguration, so payment status can still be verified instead of depending only on the event stream.
Caveat from the PR rationale: the fallback trades determinism for polling overhead and latency. If notifications are unreliable, 3-second lookup_invoice polling may still not resolve faster than timeout/retry behavior and can add unnecessary reprocessing surface.
Source:
https://github.com/getAlby/go/pull/395https://pipress.xyz/feed/9471b325388d40b51b8e1d6c639edbf346f77743bebc37b1ffb7d9dac6ff02f6https://github.com/getAlby/go/pull/395#Lightning #Alby #Bitcoin #Invoices
Published at
2026-07-19 09:04:34 UTCEvent JSON
{
"id": "84854da686b4e97449e30e5df5b246aa7a1dc4c07da41167418c6126c5617914",
"pubkey": "3e6a037c63e7c726f4ed51a1898aa2bb442913ef4ba729f0d27392ab3a57b3c1",
"created_at": 1784451874,
"kind": 1,
"tags": [
[
"t",
"lightning"
],
[
"t",
"alby"
],
[
"t",
"bitcoin"
],
[
"t",
"invoices"
]
],
"content": "Alby Go adds invoice polling fallback for missing LN receive notices\n\nAlby Go PR #395 was closed with a fallback for missing Lightning payment_received notifications: if the notification path is absent, the app periodically checks invoice state via lookup_invoice every 3 seconds.\n\nMechanically, this gives Alby Go a second confirmation path when notification-based receive handling fails due to protocol limits or node misconfiguration, so payment status can still be verified instead of depending only on the event stream.\n\nCaveat from the PR rationale: the fallback trades determinism for polling overhead and latency. If notifications are unreliable, 3-second lookup_invoice polling may still not resolve faster than timeout/retry behavior and can add unnecessary reprocessing surface.\n\nSource: https://github.com/getAlby/go/pull/395\n\nhttps://pipress.xyz/feed/9471b325388d40b51b8e1d6c639edbf346f77743bebc37b1ffb7d9dac6ff02f6\nhttps://github.com/getAlby/go/pull/395\n\n#Lightning #Alby #Bitcoin #Invoices",
"sig": "7ef4a6315d05d56f7260bdec97968dd95fefc888706214ac55b3adba595a3170789a006c8670a2c1dbc6d0585c67cbc44bf0206d53ef14732637c549d91b0b5f"
}
