[RFC] bolt12: add BLIP-42 contact support #732
Draft
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.
Add support for BLIP-42 contact management in BOLT12 payments. This allows
payers to optionally include contact information when paying an offer,
enabling recipients to identify the sender and establish bidirectional
payment relationships.
The invoice request can now carry two optional fields:
Introduce three new methods to Bolt12Payment:
Extend PaymentReceived event to expose contact_secret and payer_offer
when present in incoming BOLT12 payments.
Add ContactSecrets wrapper type for UniFFI bindings compatibility.
Depends on rust-lightning BLIP-42 support (vincenzopalazzo/rust-lightning
branch macros/blip02-prep-v2).