Thanks for disclosure, and appreciate your acknowledgment, that was exactly the use case.
If an HTLC is held, the UI shows “reconciliation pending” and polls both durable payment records every two seconds. The quote is consumed, and that operation remains locked (even after reopening the app) until both records agree on a terminal success or failure. It never reroutes or sends again.
The second guardrail is a user-set absolute fee cap in sats, separate from the quoted fee. It is enforced during pathfinding and execution; success requires the actual fee to match the quote and remain below the cap. Current release doesn’t offer ppm caps yet.
Thanks for disclosure, and appreciate your acknowledgment, that was exactly the use case.
If an HTLC is held, the UI shows “reconciliation pending” and polls both durable payment records every two seconds. The quote is consumed, and that operation remains locked (even after reopening the app) until both records agree on a terminal success or failure. It never reroutes or sends again.
The second guardrail is a user-set absolute fee cap in sats, separate from the quoted fee. It is enforced during pathfinding and execution; success requires the actual fee to match the quote and remain below the cap. Current release doesn’t offer ppm caps yet.