Skip to content

bug: move to spark activity loses direction and fee #1819

Open

Description

@ovitrif

Refs: #1774

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.

Activity

  1. added this to the 3.2.0 milestone on Nov 9, 2026
  2. changed the title [-]fix: move to spark activity loses direction and fee[/-] [+]bug: move to spark activity loses direction and fee[/+] on Nov 9, 2026
  3. ovitrif commented on Nov 9, 2026

    @ovitrif
    CollaboratorAuthor

    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.

  4. self-assigned this
    on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions