Repository navigation
Only { res: ok } is a payment receipt - #24
Merged
Merged
Conversation
Re-subscribe dumps the cached bolt11; treating that as paid made --receipt print ok with no payment. Only { res: ok } closes the wait. 1.7.2.
Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Aug 21, 2026
A payload with any res field is still not payment. The offer spec is { res: ok }; anything else stays listening.
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
onReceiptwith{ bolt11 }. That is not paid.{ res: "ok" }(spec receipt) closes the wait. Replayed invoices and any other payload stay listening.Not on npm yet. 1.7.1 is unsafe for
onReceipt.Test plan
npm test— 46 pass, including replayed invoice after resubscribe, then real{ res: ok }{ res: GFY }does not fireonReceiptor close the sub