--- Log opened Tue Jul 23 00:00:18 2019
00:02 -!- Kostenko [~Kostenko@176.78.154.81] has joined #c-lightning
00:23 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Ping timeout: 245 seconds]
00:26 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #c-lightning
01:11 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds]
01:21 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
01:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
04:24 < blockstream_bot> [Bjørn Olav Jalborg, Blockstream] Does c-lightning accept a HTLC that overpays?
04:31 < e4xit> cdecker: I see a lot of response-time issues from the blocksat API and C-Lightning node, things like `curl -F "bid=10000" -F "message=Hello World" https://api.blockstream.space/testnet/order` taking 10 - 20 seconds to return. I have had to manually adjust a few timeouts to be able to route to your node using LND, as this often takes more than 60 seconds! Just wondering if it's on some super-lightweight
04:31 < e4xit> instance or something? 
04:32 < e4xit> or for the API, perhaps there is some undocumented rate-limiting or something? 
05:33 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
05:46 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:07 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds]
06:22 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 268 seconds]
06:26 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
06:32 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 245 seconds]
06:37 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
06:41 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
06:49 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 244 seconds]
06:57 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
07:14 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
07:20 -!- instagibbs [~instagibb@pool-100-15-121-126.washdc.fios.verizon.net] has quit [Quit: ZNC 1.6.6+deb1ubuntu0.2 - http://znc.in]
07:21 -!- instagibbs [~instagibb@pool-100-15-121-126.washdc.fios.verizon.net] has joined #c-lightning
07:25 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
08:02 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
08:48 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 248 seconds]
09:46 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
09:50 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
09:54 -!- reallll is now known as belcher
10:06 <@cdecker> Uhm, not sure what might be causing those delays, I see you are already on the #satellite slack, but I'll ask the people running it :-)
10:06 <@cdecker> Bjorn: yes, c-lightning will accept overpayments
10:17 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
11:03 <@cdecker> e4xit: we have people investigating the root cause of the latency, I'm confident it'll be fixed soon :_)
11:07 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
11:17 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
11:17 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
11:20 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
12:34 < e4xit> thanks cdecker!
12:38 < e4xit> I have much more luck routing to mainnet node, FWIW. Both of my nodes have about 7 connections on each network, to highly connectd nodes.
12:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:06 < blockstream_bot> [Martin Izdimirski, Blockstream] e4xit: currently looking into the issue
13:11 < blockstream_bot> [Martin Izdimirski, Blockstream] I just tried curl-ing it again and it seems to respond pretty fast
13:11 < blockstream_bot> ```
13:11 < blockstream_bot> $ time curl -F 'bid=1000' -F 'message=1234' https://api.blockstream.space/testnet/order
13:11 < blockstream_bot> {"auth_token":"8eafffebc6f71e0402fde3ec7ac834b8dcede2b6d27be8c2f5106e1eed9d0b39","uuid":"3f24b72f-18ef-499f-8502-7c0400762ba4","lightning_invoice":{"id":"w82yjbsLgZQRW0e3CI5Fq","msatoshi":"1000","description":"Blockstream Satellite Transmission","rhash":"c91f0e9d33c271583bfbf15f4127dbac867e24d2f9b461987c3aecb153f899df","payreq":"lntb10n1pwnw6wspp5ey0sa8fncfc4swlm7905zf7m4jr8ufxjlx6xrxru8tktz5lcn80sdphgfkx7cmtwd68ye
13:11 < blockstream_bot> real	0m0.383s
13:11 < blockstream_bot> user	0m0.015s
13:11 < blockstream_bot> sys	0m0.009s
13:11 < blockstream_bot> ```
13:30 -!- Victor_sueca is now known as Victorsueca
13:55 < e4xit> Martin: yes its certainly intermittent! often i get reasonable responses too... sorry. 
13:59 < e4xit> they are super quick for me now too :)
14:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:15 < e4xit> Martin Izdimirski: I don't know if you changed anything, but i see good performance now on both API and Lightning node on testnet. Thanks
14:30 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 268 seconds]
14:52 < blockstream_bot> [Martin Izdimirski, Blockstream] yep, the Lightning node was eating up a bunch of the CPU, so a simple restart seemed to have done the trick (for now). I’m glad it’s working ok now
14:55 < blockstream_bot> [Martin Izdimirski, Blockstream] will keep a closer eye on it to see what causes it
14:57 -!- arvanaghi [46132bba@gateway/web/cgi-irc/kiwiirc.com/ip.70.19.43.186] has joined #c-lightning
15:16 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:32 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
17:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning []
18:56 -!- arvanaghi [46132bba@gateway/web/cgi-irc/kiwiirc.com/ip.70.19.43.186] has quit [Remote host closed the connection]
19:47 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #c-lightning
19:47 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Quit: Leaving]
20:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:35 -!- Kostenko [~Kostenko@176.78.154.81] has quit [Ping timeout: 268 seconds]
20:49 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning
21:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-vgkmggljhskafqke] has left #c-lightning []
21:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-vgkmggljhskafqke] has joined #c-lightning
21:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-vgkmggljhskafqke] has left #c-lightning []
21:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-vgkmggljhskafqke] has joined #c-lightning
22:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
--- Log closed Wed Jul 24 00:00:19 2019