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
{{ message }}
Repository navigation
bug: move to spark activity loses direction and fee #1819
A move to Spark pays a Spark invoice from the channels, so the LDK send and the Spark receive share one payment hash. Both write the same activity row (the LDK and Spark payment handlers that write activity by payment hash), so the move can end up as a single received payment: the direction flips to incoming and the LDK routing fee is lost. For example, moving 10,000 sats with a 5 sat routing fee can leave a received 10,000 sat entry with no fee.
Decide how a move appears in Activity (one transfer row with the fee, or two linked rows), then store both legs under distinct linked identities or reconcile them so the direction and the actual routing fee survive.
Reported on the iOS twin in this review; the Android flow has the same shared hash.
Interim rule landed: a move keeps one Activity row, the channel send (outgoing, moved amount, routing fee), and the Spark receive with the same hash is not recorded (3341321). This issue stays open for the designed Move to Spark row.
Activity
[-]fix: move to spark activity loses direction and fee[/-][+]bug: move to spark activity loses direction and fee[/+]ovitrif commentedon Nov 9, 2026
Interim rule landed: a move keeps one Activity row, the channel send (outgoing, moved amount, routing fee), and the Spark receive with the same hash is not recorded (3341321). This issue stays open for the designed Move to Spark row.