Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1/3]: Preparatory work for Forwarding Blinded Routes #8159

Merged
merged 14 commits into from
Mar 28, 2024

Commits on Mar 27, 2024

  1. Configuration menu
    Copy the full SHA
    42069ef View commit details
    Browse the repository at this point in the history
  2. lnwire: create common encoder/decoder for raw feature vectors

    We'll need to pack feature vectors for route blinding, so we pull
    the encoding/decoding out into separate functions (currently
    contained in ChannelType). Though it's more lines of code, we keep
    most of the ChannelType assertions so that we strictly enforce
    use of the alias.
    carlaKC committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    3cc50ce View commit details
    Browse the repository at this point in the history
  3. record: add TLV encoding/decoding for blinded route data blobs

    This commit adds encoding and decoding for blinded route data blobs.
    TLV fields such as path_id (which are only used for the final hop)
    are omitted to minimize the change size.
    carlaKC committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    c48841a View commit details
    Browse the repository at this point in the history
  4. multi: add validation of blinded route encrypted data

    Co-authored-by: Calvin Zachman <calvin.zachman@protonmail.com>
    carlaKC and calvinrzachman committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    d8979d3 View commit details
    Browse the repository at this point in the history
  5. lnwire: add blinding point to update_add_htlc TLVs

    Add blinding points to update_add_htlc. This TLV will be set for
    nodes that are relaying payments in blinded routes that are _not_
    the introduction node.
    carlaKC committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    e4f90ec View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    7596e76 View commit details
    Browse the repository at this point in the history
  7. multi: add blinding point to payment descriptor and persist

    This commit adds an optional blinding point to payment descriptors and
    persists them in our HTLC's extra data. A get/set pattern is used to
    populate the ExtraData on our disk representation of the HTLC so that
    callers do not need to worry about the underlying storage detail.
    carlaKC committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    f090a64 View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    7bf1daa View commit details
    Browse the repository at this point in the history
  9. htlcswitch: add incoming amount and to decode hop iterator request

    When we have payments inside of a blinded route, we need to know
    the incoming amount to be able to back-calculate the amount that
    we need to forward using the forwarding parameters provided in the
    blinded route encrypted data. This commit adds the payment amount
    to our DecodeHopIteratorRequest so that it can be threaded down to
    payment forwarding information creation in later commits.
    carlaKC committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    7265e4c View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    4a93f4d View commit details
    Browse the repository at this point in the history
  11. Configuration menu
    Copy the full SHA
    0aeb7c4 View commit details
    Browse the repository at this point in the history
  12. lnrpc: rename proportional fee rate on lnrpc

    This field is incorrectly suffixed as "msat", when it is actually
    interpreted as the proportional fee rate. This is the value that we
    should be using because the sender will calculate proportional fees
    accordingly. This is a breaking change to the RPC, but on an
    experimental and unreleased API.
    carlaKC committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    4214330 View commit details
    Browse the repository at this point in the history
  13. Configuration menu
    Copy the full SHA
    d67f652 View commit details
    Browse the repository at this point in the history
  14. Configuration menu
    Copy the full SHA
    2130022 View commit details
    Browse the repository at this point in the history