loop/looprpc
Joost Jager 535e964ec9
loopdb: migrate loop in channel to last hop
A database field was already in place to allow channel selection for
loop in. Unfortunately this field, which contains a short channel id,
isn't easily usable for controlling the loop server payment. Because of
non-strict forwarding, it is only possible to constrain a route to a
specific last hop pubkey.

This commit converts the existing field into a pubkey field.
2020-02-17 19:59:05 +01:00
..
client.pb.go loopdb: migrate loop in channel to last hop 2020-02-17 19:59:05 +01:00
client.pb.gw.go loopdb: migrate loop in channel to last hop 2020-02-17 19:59:05 +01:00
client.proto loopdb: migrate loop in channel to last hop 2020-02-17 19:59:05 +01:00
client.swagger.json loopdb: migrate loop in channel to last hop 2020-02-17 19:59:05 +01:00
gen_protos.sh looprpc: generate client REST definitions 2019-03-12 15:34:45 -07:00
server.pb.go looprpc: add updated server proto 2020-01-07 13:28:22 +01:00
server.proto looprpc: add updated server proto 2020-01-07 13:28:22 +01:00