--- Log opened Wed Jan 30 00:00:37 2019
01:52 < t0mix> when I use "lightning-cli pay <bolt11>", does c-lightning check for case when I have channel open directly with payee? it takes several seconds to make payment even with channel opened directly. I'm searching for bottleneck. (I run Raspberry Pi 2, 1GB RAM, 5400rpm HDD via USB)
02:03 -!- kexkey [~kexkey@172.98.82.4] has quit [Read error: Connection reset by peer]
02:21 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:25 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:27 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
03:28 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
03:50 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:59 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
05:57 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
06:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:59 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
08:09 < blockstream_bot> [Christian Decker, Blockstream] It used to randomize the route even in those cases. That should no longer be the case at least when compiling from `master`
08:14 < t0mix> compiled from https://github.com/ElementsProject/lightning/archive/v0.6.3.zip
09:13 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
12:08 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
13:22 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
14:13 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:39 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:07 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
16:12 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Ping timeout: 245 seconds]
16:50 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
16:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
17:33 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
17:33 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:56 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
17:57 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:04 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:04 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:12 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
18:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
18:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:36 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
19:21 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:26 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:36 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
19:40 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Ping timeout: 240 seconds]
20:02 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:04 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
20:48 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
20:52 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Ping timeout: 246 seconds]
21:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
23:36 < t0mix> is there any value added by having more peers connected to my node (without necessarily having channel open with each peer)? or may I even consider it not desired state?
--- Log closed Thu Jan 31 00:00:36 2019