Skip to content

Consider whether to support looping payments #292

Closed as not planned
Closed as not planned
@tnull

Description

@tnull

A user encountered a case where they wanted to pay a JIT-channel invoice generated by ourselves to trigger a channel open from an LSP (Voltage Flow 2.0 in this case).

However, LDK Node rejected the payment with an NodeError: DuplicatePayment: A payment with the given hash has already been initiated error.

Generally, this is may be considered a misuse of JIT channels as they are really 'just-in-time' and not meant to order (and self-pay) liquidity upfront.
While looping payments are kind of bogus, we still should consider if we need to support them if users keep running into similar issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions