--- Log opened Thu Feb 28 00:00:02 2019 00:19 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:51 -!- mode/#c-lightning [+o rusty] by ChanServ 01:52 -!- rusty changed the topic of #c-lightning to: Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.7.0rc3 Logs at http://gnusha.org/c-lightning/ 01:52 -!- mode/#c-lightning [-o rusty] by rusty 01:55 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 02:46 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 03:28 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:43 < t0mix> will dev-ignore-htlcs work as "channel not available" flag? I'm thinking about molz points he made. I'd like to be able to restart lightningd in a clean way. without channel closures. 05:33 < molz> t0mix, what point did i make? 05:45 < t0mix> molz "what if someone needs to send a payment during your down time and your node is in their only route?" 05:45 < t0mix> no.. not that one =D 05:50 < t0mix> hm, but you didn't really make any other point. just ignore what I wrote. 05:59 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 06:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 06:12 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 06:14 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 06:38 < molz> right, i don't think you got my point 06:40 < molz> maybe if the system has a way to evaluate nodes and those that have a lot down time have a badge to their nodkey as "instable" so others can see and avoid them then maybe it's better for routing, idk 06:43 < t0mix> https://1ml.com seems to measure "Availability" somehow (Node Rankā„¢). I used that number to search for reliable node to connect. 06:44 < t0mix> if your point was "don't bring your node down, ever", than I get it. 06:49 < molz> "unstable" 06:50 < molz> not sure if 1ML info is correct? 06:51 < t0mix> don't know. I have no better info. 06:53 < t0mix> I can see that Availability number for my node (lower is better) is slowly decreasing over time as my node is up. 06:53 < t0mix> so it works at least. how effeciently, no idea. 08:45 -!- dougsland [~douglas@tchelinux/moderator/dougsland] has joined #c-lightning 09:08 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 10:25 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [] 10:25 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode] 11:06 -!- harding [~quassel@li1258-130.members.linode.com] has quit [Ping timeout: 240 seconds] 11:07 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 11:08 -!- harding [~quassel@li1258-130.members.linode.com] has joined #c-lightning 11:24 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 11:56 -!- kexkey [~kexkey@139.28.218.30] has joined #c-lightning 12:15 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 12:21 < kexkey> Hi! I'd like to know what's the highest amount I can send to a specific node. Is this possible? Can I get a list of possible routes to a node and compare the capacities or something like that? 12:25 < t0mix> kexkey, depends on channel capacity. check "lightning-cli help fundchannel" .. maximum capacity is 16777215 satoshi 12:26 < kexkey> t0mix, I mean with current channels. I don't want to open new channels, I want to know with current topology, how much I can send max to an ID. 12:28 < kexkey> I can check if there's a route for a specific amount (getroute)... but that's not exactly what I'm looking for. I'd like to know the highest capacity route if I may say 12:28 < t0mix> kexkey, "lightning-cli listfunds". then "channel_sat" is maximum value you can send via specific channel 12:29 < kexkey> t0mix, but the max I can send will be lower if the following channels have lower capacity. 12:29 < t0mix> yes 12:31 < t0mix> you can list all channels there are with "lightning-cli listchannels". then you can grep for particual node ID you want to check. but you will only see maximum channel capacity, not the current available capacity. 12:31 < kexkey> It would be a nice feature. Or just being able to get a list of possible routes and then I can do the check on my side by looking at all the channel_sat... 12:32 < t0mix> I'm not sure you can get channel detailed status. I think no. that would deanonymize payments. but I might me not very knowledgable person. 12:32 < kexkey> Oh yeah with the result of listchannels I can build something I guess... 12:33 < kexkey> Well if getroute is able to find a route for an amount, I guess the information is available. 12:33 < t0mix> I think it is try & settle/fail. but I really don't know. 12:35 < kexkey> Yes I wanted to avoid looping getroute with an increasing amount just to test the max. :) 12:35 < t0mix> getroute itself will not guarantee that payment will succeed. sendpay command is used after route is found. then payment might go through or fail. 12:37 < kexkey> True but it would be a good indication for my use case. I can accept the risk of the payment not going through... 12:37 < t0mix> what are you trying to achieve? 12:39 < kexkey> I want to know how much I can send to someone right away (without waiting for a new channel between us to confirm) to set the maximum amount in my application. 12:40 < kexkey> Knowing that before signing the crypto contract is better than having to cancel the order because there's no route for the amount or having to wait for a channel to be confirmed and the invoice expired anyway :) 12:41 < kexkey> UX, you know... 13:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 13:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 14:22 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 245 seconds] 14:28 < m-schmoock> cdecker: can you have another look at PR 2342? I integrated your input. Especially the last commit is a WIP proposal to deal with the global fallback and old db migrations (2394 not merged yet) https://github.com/ElementsProject/lightning/pull/2342/commits/40af7d1910d892d2b7d40349fd52b8efa463c00c 14:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:46 < m-schmoock> rusty: hi, maybe have another look at PR 2342? 14:46 < rusty> m-schmoock: sure! I've been distracted by this release process, sorry! 14:46 < m-schmoock> no worries 14:47 < m-schmoock> and you can merge https://github.com/ElementsProject/lightning/pull/2418 someone found a stupid bug in the docker file 14:49 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:52 < rusty> cdecker: https://github.com/ElementsProject/lightning/pull/2418 ? 14:54 < m-schmoock> rusty: my boss told he met you once at https://linuxbierwanderung.com/ couple of years ago :D 14:55 < rusty> Wow, that was a *long* time ago! Small world! 14:56 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 15:05 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 15:06 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 15:07 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 15:07 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 15:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 15:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds] 15:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:50 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 16:06 -!- ctrlbreak_MAD is now known as ctrlbreak 16:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 250 seconds] 17:05 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 245 seconds] 17:07 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning 18:51 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood] 18:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 18:55 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood] 18:55 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 19:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:00 -!- justinmoon [~manjaro-i@cpe-70-113-80-71.austin.res.rr.com] has joined #c-lightning 20:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 20:32 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Ping timeout: 245 seconds] 21:17 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood] 21:17 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 22:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] --- Log closed Fri Mar 01 00:00:03 2019