lnd.xprv/lnrpc/routerrpc
Wilmer Paulino 0fc401de19
routing+routerrpc: take max cltv limit into account within path finding
With the introduction of the max CLTV limit parameter, nodes are able to
reject HTLCs that exceed it. This should also be applied to path
finding, otherwise HTLCs crafted by the same node that exceed it never
left the switch. This wasn't a big deal since the previous max CLTV
limit was ~5000 blocks. Once it was lowered to 1008, the issue became
more apparent. Therefore, all of our path finding attempts now have a
restriction of said limit in in order to properly carry out HTLCs to the
network.
2019-10-11 18:04:49 -04:00
..
config_active.go routing: persist mission control data 2019-07-31 08:44:00 +02:00
config_default.go routing: persist mission control data 2019-07-31 08:44:00 +02:00
config.go routing: persist mission control data 2019-07-31 08:44:00 +02:00
driver.go lnrpc/routerrpc: add config, implement full RouterServer 2019-02-20 16:10:39 -08:00
log.go multi: remove dead code 2019-09-10 17:21:59 +02:00
router_backend_test.go lnrpc+lnrpc/routerrpc: add a new TLV record field to the Hop proto 2019-08-22 18:53:03 -07:00
router_backend.go routing+routerrpc: take max cltv limit into account within path finding 2019-10-11 18:04:49 -04:00
router_server.go routing+routerrpc: take max cltv limit into account within path finding 2019-10-11 18:04:49 -04:00
router.pb.go routing+routerrpc: take max cltv limit into account within path finding 2019-10-11 18:04:49 -04:00
router.proto routing+routerrpc: take max cltv limit into account within path finding 2019-10-11 18:04:49 -04:00