Add BOLT12 support to LSPS2 via custom Router implementation

lightning-liquidity/src/lsps2/event.rs

@@ -49,7 +49,23 @@ pub enum LSPS2ClientEvent {
 	/// When the invoice is paid, the LSP will open a channel with the previously agreed upon
 	/// parameters to you.
 	///
+	/// For BOLT11 JIT invoices, `intercept_scid` and `cltv_expiry_delta` can be used in a route
+	/// hint.
+	///
+	/// For BOLT12 JIT flows, use [`LSPS2Bolt12InvoiceParameters::to_context_data`] to serialize
+	/// these parameters and pass them to
+	/// [`OffersMessageFlow::create_offer_builder_with_context_data`] when creating the offer. When
+	/// an [`InvoiceRequest`] is received, the parameters will be surfaced via
+	/// [`Event::InvoiceRequestReceived`], where they can be deserialized and used to build payment
+	/// paths via [`build_lsps2_payment_paths`].
+	///
 	/// **Note: ** This event will *not* be persisted across restarts.
+	///
+	/// [`LSPS2Bolt12InvoiceParameters::to_context_data`]: crate::lsps2::router::LSPS2Bolt12InvoiceParameters::to_context_data
+	/// [`OffersMessageFlow::create_offer_builder_with_context_data`]: lightning::offers::flow::OffersMessageFlow::create_offer_builder_with_context_data
+	/// [`InvoiceRequest`]: lightning::offers::invoice_request::InvoiceRequest
+	/// [`Event::InvoiceRequestReceived`]: lightning::events::Event::InvoiceRequestReceived
+	/// [`build_lsps2_payment_paths`]: crate::lsps2::router::build_lsps2_payment_paths
 	InvoiceParametersReady {
 		/// The identifier of the issued bLIP-52 / LSPS2 `buy` request, as returned by
 		/// [`LSPS2ClientHandler::select_opening_params`].

lightning-liquidity/src/lsps2/mod.rs

@@ -13,5 +13,6 @@ pub mod client;
 pub mod event;
 pub mod msgs;
 pub(crate) mod payment_queue;
+pub mod router;
 pub mod service;
 pub mod utils;