Skip to content

Preserve full pay --wait events - #333

Closed
tankyleo wants to merge 1 commit into
mainfrom
2026-11-pay-wait-events
Closed

tankyleo wants to merge 1 commit into
mainfrom
2026-11-pay-wait-events

Conversation

@tankyleo

Copy link
Copy Markdown
Contributor
    Preserve full pay --wait events

    Users need BOLT12 invoices to generate payer proofs later and failure
    reasons to diagnose unsuccessful payments. Neither can currently be
    recovered from payment history, making the completion event the
    opportunity to retain this information.

    Co-Authored-By: Codex

Users need BOLT12 invoices to generate payer proofs later and failure
reasons to diagnose unsuccessful payments. Neither can currently be
recovered from payment history, making the completion event the
opportunity to retain this information.

Co-Authored-By: Codex
@ldk-reviews-bot

ldk-reviews-bot commented Nov 11, 2026 •

Copy link
Copy Markdown

👋 Thanks for assigning @benthecarman as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

&payment,
);
eprintln!("{}", sanitize_for_terminal(format!("Payment {payment_id} failed")));
print_response(&payment);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude is complaining on how this will output:

PaymentFailed.reason is an Option<i32> and has no serialize_with, so this prints "reason": 1 rather than "PAYMENT_FAILURE_REASON_RECIPIENT_REJECTED". Every other enum the CLI prints goes through stringify_enum_serializer!. Could you add an Option version of that macro and a field attribute for events.PaymentFailed.reason in ldk-server-grpc/build.rs? A bare integer doesn't help much when diagnosing a failure.

@tankyleo tankyleo closed this Nov 11, 2026
@tankyleo

Copy link
Copy Markdown
Contributor Author

Somehow I was able to push a branch on this repository. As expected could not push to it later, so continued here #334

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants