You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xpay: add xpay_attempt_start and xpay_attempt_end notifications.
Requested-by: Michael at Boltz
Signed-off-by: Rusty Russell <[email protected]>
Changelog-Added: Plugins: `xpay` now publishes `xpay_attempt_start` and `xpay_attempt_end` notifications on every payment send attempt.
Emitted by `xpay` when part of a payment ends. `payment_hash`, `groupid` and `partid`
618
+
will match a previous `xpay_attempt_start`.
619
+
620
+
`status` will be "success" or "failure". `duration` will be an integer (with 9 decimal places)
621
+
in seconds, between the time `xpay` tells lightningd to send the onion, to when `xpay` processes
622
+
the response.
623
+
624
+
If `status` is "failure", there will always be an `error_message`: the other fields below
625
+
will be missing in the unusual case where the error onion is corrupted.
626
+
627
+
`failed_node_id`: If it's a non-local error, the source of the error.
628
+
`failed_short_channel_id`: if it's not the final node, the channel it's complaining about.
629
+
`failed_direction`: if it's not the final node, the channel direction.
630
+
`error_code`: the error code returned (present unless onion was corrupted).
631
+
`error_message`: always present: if `failed_node_id` is present it's just the name of the `error_code`, but otherwise it can be a more informative error from our own node.
0 commit comments