Skip to content

Add random CLTV offsets (or max CLTV offsets) during route calculation #158

Closed

Description

@TheBlueMatt

As suggested by BOLT 7 in "Recommendations for Routing" to avoid making it obvious which hops a route is taking.

Activity

  1. TheBlueMatt commented on Jan 8, 2020

    @TheBlueMatt
    CollaboratorAuthor

    Note we should do the same for the value sent.

  2. TheBlueMatt commented on May 13, 2022

    @TheBlueMatt
    CollaboratorAuthor

    Done in #1286.

  3. tnull commented on May 16, 2022

    @tnull
    Contributor

    Note we should do the same for the value sent.

    Do we still want some form of fee randomization/overpayment? On the one hand, adding the exact fees might give something away to an adversary that is able to guess the actual payment amount to be delivered correctly. On the other, it is questionable how often this would be the case and whether these few instances would actually justify the losing some amount in overpaid fees and making the routing logic more complex.

  4. TheBlueMatt commented on May 16, 2022

    @TheBlueMatt
    CollaboratorAuthor

    Oh good point, yea, maybe lets open an issue to track it, but I think I agree with you there may not be a ton of value in it. One question is if we should randomize in the sub-sat range - we should maybe investigate how much invoices in the wild have 0 msats or any other "round numbers" where we should randomize a bit to add noise.

  5. TheBlueMatt commented on May 16, 2022

    @TheBlueMatt
    CollaboratorAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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