M. Quinn Warnock
M. Quinn Warnock
epochs aren't defined by wall-time; a new epoch begins whenever genuinely new routes are added. We do seem to be lacking a robust mechanism for determining whether a peer has...
Sure; just something that indicates to the connector that it should reset the relevant entry in broadcaster.peerEpochs
This is already what we do.
Here's what we have now: Events initiating a route-broadcast message: 1. startup (send locally-configured routes) 2. at an interval less than the hold-down-time the connector has given to its peers...
liquidity curve changes don't trigger new_routes additions. For the logic surrounding whether a route is considered to be new and trigger a rebroadcast, see routing-tables.js addRoute and the handling of...
Could you explain what is expensive in the current situation, and how hitting an endpoint every 10 seconds is cheaper?
Overall, I'm in favor of this refactor in the short term, but would note the sacrifices it makes. This change would more thoroughly cement the shortest-path-preference heuristic, which I don't...
Indeed, it is a weird (and I hope very temporary) situation. I'm not sure what small steps we can take to greatly improve things; I think a qualitative jump in...
I've been thinking of the curves-in-route-broadcast as a vestigial organ, which would be painful to remove, out of proportion to the gain of removal. Regardless of whether we want to...
> Yes, that's my understanding as well. Ideally, we would fix the routing protocol with minimal changes. Right now I'd give it about a 60% probability that we can make...