Skip to content

Conversation

@dni
Copy link
Member

@dni dni commented Oct 15, 2025

closes #79

  • added as optional in advanced settings
  • api endpoint returning the success response
    screenshot-1760523700
    screenshot-1760523965

screenshot-1760523538

dni added 2 commits October 15, 2025 12:11
- added as optional in advanced settings
- api endpoint returning the success response

if link.verify:
verify_url = request.url_for(
"lnurlp.api_lnurl_verify", payment_hash=payment.payment_hash
Copy link
Collaborator

Choose a reason for hiding this comment

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

The LUD does not specify that the check value must be the payment hash.
Can't this in fact be a vulnerability? Anyone that sees the QR code can check the payment status (and obtain the pre-image).

Suggestion:

  • use verify_secret random value
  • introduce extra column (not to have such a large number of migrations)

Copy link
Collaborator

Choose a reason for hiding this comment

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

nack

Copy link
Member Author

Choose a reason for hiding this comment

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

the payment_hash is actually inside the bolt11 invoice

Copy link
Collaborator

@talvasconcelos talvasconcelos left a comment

Choose a reason for hiding this comment

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

tested

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.

feature request: add LUD-21 support

4 participants