Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Draft: BOLT7: The `route_price_update` Message #616
DISCLAIMER: This is not a firm proposal yet, only a draft to hopefully receive some feedback. If this is not the right place for such a thing I can close it and open it as a PR to my own repo instead until it is more mature to actually be considered to be merged.
A few weeks ago I was discussing on IRC with alexbosworth and others about being able as a hop to charge specific fees for routing through different channel pair combinations.
My main use case was to be able to allow routing through channels with different chain_hash, so it's not really a fee, but a price, a multiplier.
But it can be also used to charge specific additional fees for channel combinations.
I'm talking in float numbers here to simplify, but in the draft I avoided them. Not sure if in a nice way or a stupid one.
As said, feedback welcomed.
renepickhardt left a comment
I don't get this proposal. Why are the current routing fees not sufficient? In particular if we have the multichannel case we might need an exchange rate anyway (which could include the fees for the exchange and which should not be propagated over gossip anyway as exchange rates are probably needed in real time)
How do you satisfy my examples with the current routing fees?
Well, I was assuming this "route_price_update" could be updated relatively often but not more often than that. I guess if people want more regular updates they can receive them from the connecting node in some other protocol other than the gossip one. Note the hop can always reject to route a payment when if the offered rate is not to his liking anymore, even if it had announce that rate would be fine before.