Closed slanesuke closed 2 weeks ago
For fedimint just having max_total_routing_fee_msat as an absolute value would be the most user friendly.
For fedimint just having max_total_routing_fee_msat as an absolute value would be the most user friendly.
Thanks, good to know!
Ah, seems this needs a rebase to make CI pass (which we just fixed, excuse the inconvenience!)
Ah, seems this needs a rebase to make CI pass (which we just fixed, excuse the inconvenience!)
done!
rebased!
You'll also need to account for the new send
argument in all the test cases (CLN, bindings tests, etc)l
@tnull I could use some advice on how to go about overriding routing params in the bolt12 methods. In bolt11/spontaneous send methods I could access the route parameters so it was a bit easier. But when paying offers I can't find where/how to override the existing routing params. Any thoughts?
rebased
@tnull I could use some advice on how to go about overriding routing params in the bolt12 methods. In bolt11/spontaneous send methods I could access the route parameters so it was a bit easier. But when paying offers I can't find where/how to override the existing routing params. Any thoughts?
I think unfortunately LDK currently doesn't provide a way to override all of the fields, now opened the issue here: https://github.com/lightningdevkit/rust-lightning/issues/3262
Let's keep this PR BOLT11/Spontaneous only and I'll open a tracking issue to make sure we won't forget to add SendingParameters
to Bolt12Payment::send
once the API becomes available.
I think CI fails as you haven't updated the Kotlin tests in bindings/kotlin/ldk-node-jvm/lib/src/test/kotlin/org/lightningdevkit/ldknode/LibraryTest.kt
yet.
Could you also try to clean up the commit history a bit? Seems there are a few overlapping / back-and-forth commits going on.
@tnull I could use some advice on how to go about overriding routing params in the bolt12 methods. In bolt11/spontaneous send methods I could access the route parameters so it was a bit easier. But when paying offers I can't find where/how to override the existing routing params. Any thoughts?
I think unfortunately LDK currently doesn't provide a way to override all of the fields, now opened the issue here: lightningdevkit/rust-lightning#3262
Let's keep this PR BOLT11/Spontaneous only and I'll open a tracking issue to make sure we won't forget to add
SendingParameters
toBolt12Payment::send
once the API becomes available.
Okay, sounds good.
Based on #166 and #328
This PR introduces a
PaymentParameters
struct to allow users to override fields likemax_total_cltv_expiry_delta
,max_total_routing_fee_msat
, andexpiry_time
. I'd appreciate suggestions on other useful fields to include as well.I've added the optional
PaymentParameters
param to the send methods for both BOLT11 and Spontaneous payments. But, I need advice on whether we should be including it in the send methods for BOLT12 payments when paying for an offer. Specifically, I'm uncertain if values likemax_total_cltv_expiry_delta
orexpiry_time
can be overridden in this context.