Comment by GibbsSamplePlatter on 12/01/2018 at 18:32 UTC

3 upvotes, 2 direct replies (showing 2)

View submission: ⚡ Lightning Network Megathread ⚡

View parent comment

LN pegging your CPU as a routing node is a champagne problem(you're apparently making plenty of fees), quickly solved by rate limiting or raising your fees.

Replies

Comment by Bobanaut at 12/01/2018 at 19:15 UTC*

3 upvotes, 1 direct replies

but the current specs have no fees on the nodes, only the receiver can have a fee...

so you are basically giving your channels for no fee, you have to compute with your channel partner lots of new contracts/keys and you risk having to go on the main chain if something breaks on a transaction where you are involved in, which means you have to pay normal BTC fees even though you only offer a service for someone else...

edit: it looks like there is actually a fee per (routing)node. but it's mentioned much later in the specs and the place i looked at was/is not up-to-date

Comment by Bobanaut at 12/01/2018 at 19:09 UTC*

2 upvotes, 1 direct replies

a routing node can not take any fee for its service though. and every node is a routing node if there is more than a single channel to the network

edit: it looks like there is actually a fee per (routing)node. but it's mentioned much later in the specs and the place i looked at was/is not up-to-date