Skip to content

Handle nodes with multiple channels between them better in scoring #2223

Open
@TheBlueMatt

Description

@TheBlueMatt

Currently we treat them each as distinct edges with different available liquidity, but this isn't how it works in practice - nodes will just forward over any channel they have. Maybe splicing will just fix this for us, but we might consider handling this somehow in the scorer by ignoring redundant channels and just treating it as one big channel.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions