Fwd: Re: Routing & Beacons



Summary:

In a mailing list conversation, Rusty Russell discusses the use of "landmarks" instead of "beacons" in payment channels. When asked if all payments go through selected beacons nodes, Rusty confirms that to a first approximation, it is true, however, if the route goes in and out of the same channel, it can be eliminated. They also discuss the pulse protocol, which is based on beacons and updates routing tables but doesn't require all messages to go through the beacons. The source doesn't know the route beforehand, but it puts less pressure on beacons. When Laurentmt asks about an update strategy for routing tables, Rusty says they haven't decided yet, but thoughts are welcome. When discussing the two variables that determine the best route: capacity of channels at time t and fees charged by nodes, Rusty suggests that payments are generally smaller than channel capacity and that pricing information is dynamic and needs careful thought. Rusty's current idea involves ratelimiting pricing updates and phasing price changes over time. There is also the question of how to handle false advertising, with Rusty suggesting that you should be able to broadcast the response from a node that refuses to route your payment. If one node signs an invalid message, it can be blacklisted temporarily.


Updated on: 2023-05-23T23:26:27.197790+00:00