Skip to content

[feature]: 0conf anchor restriction is needlessly limiting #7113

Open
@TheBlueMatt

Description

@TheBlueMatt

The current 0conf anchor requirement, as I understand it, only applies to lnd as the funder, not lnd as the fundee. 0conf is generally primarily useful in an LSP-client model where the LSP funds a 0conf channel that the client accepts. In many cases lnd is used as an LSP on a server, however its relatively rare, afaiu, for lnd to be used as an LSP client (ignoring the general "buying inbound liquidity" stuff, which isn't always/usually 0conf). Thus, the 0conf anchor restriction applying on funding (but not fundee) is somewhat backwards - the primary use of 0conf in lnd (AFAIU) is where lnd is the funder, opening a channel to, eg, LDK or greenlight clients (though I believe that's always CLN as the LSP), not the other way around. Thus, the anchor restriction as it stands makes the 0conf feature in lnd not very useful for its primary potential use-case, as far as I can see.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImprovements to existing features / behaviourzero conf

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions