Skip to content

Ability to set inbound and outbound fees #4225

Closed

Description

@Swissnode

As a major channel balancer and node operator, it has become clear to me and the community of channel balancers I work with that we really need the ability to incentivize traffic in certain directions.

As such, we would highly recommend having inbound and outbound fees to allow such incentivization.

Activity

  1. Roasbeef commented on Apr 27, 2020

    @Roasbeef
    Member

    As is, on the protocol level, you can only set the fees for outbound (routing an HTLC over that channel). The remote party controls the "inbound fees", since their bandwidth is used to carry the HTLC.

    One thing we've discussed is possibly introducing "pair wise" fee schedules. So this would mean you can set different fees for A -> B, and A -> C, where B and C are your channels. We could possibly add some new TLV fields to the ChannelUpdate to make this possible, but no one has attempted to fully specify it yet.

  2. added
    brainstormingLong term ideas/discussion/requests for feedback
    channel managementThe management of the nodes channels
    feesRelated to the fees paid for transactions (both LN and funding/commitment transactions)
    on Apr 27, 2020
  3. Swissnode commented on Apr 28, 2020

    @Swissnode
    Author

    Pairwise fees would be a GREAT option @Roasbeef ! Thanks for taking the time to look at this. I realise the discussion probably belonged on another repo, apologies if I hit the wrong one!!

    Great work, loving Lightning and LND!

  4. Jestopher-BTC commented on Aug 15, 2020

    @Jestopher-BTC

    Either pairwise fees or inbound fees are gravely needed for node management! Inbound liquidity is a scarce resource and it does not have the same value even in different channels; some inbound is worth more in certain channels than others.

  5. grnqrtr commented on Aug 16, 2020

    @grnqrtr

    Just adding that I agree. Having some kind of "pair wise" fees or inbound fees would be really helpful.

  6. Roasbeef commented on Jan 21, 2021

    @Roasbeef
    Member

    This is a spec level thing, so closing here as the discussion needs to be started on the rfc repo and/or the dev mailing list.

  7. AbelLykens commented on Jan 21, 2021

    @AbelLykens
    Contributor

    Opened in RFC repo:
    lightning/bolts#835
    Link added for reference. Mentioned you @Swissnode as original.

  8. joostjager commented on Jul 4, 2022

    @joostjager
    Contributor

    But is this a spec level thing? It seems to me that this can also be a implementation-specific extension when inbound fees are always negative or zero. Ref: https://lists.linuxfoundation.org/pipermail/lightning-dev/2022-July/003643.html

  9. Roasbeef commented on Aug 25, 2022

    @Roasbeef
    Member

    Re-opening since #6703 is now a thing

  10. dstadulis commented on Aug 30, 2022

    @dstadulis

    relevant blip
    lightning/blips#18

  11. added this to the High Priority milestone on Aug 4, 2023
  12. added
    P1MUST be fixed or reviewed
    on Aug 8, 2023
  13. removed this from the High Priority milestone on Aug 8, 2023
  14. moved this to 👀 In review in lnd v0.18on Aug 10, 2023
  15. added this to the v0.18.0 milestone on Aug 10, 2023
  16. moved this from 👀 In review to ✅ Done in lnd v0.18on Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1MUST be fixed or reviewedbrainstormingLong term ideas/discussion/requests for feedbackchannel managementThe management of the nodes channelsfeesRelated to the fees paid for transactions (both LN and funding/commitment transactions)routing

Type

No type

Projects

  • Status
    ✅ Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions