--- Log opened Mon Aug 26 00:00:52 2019
00:27 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
00:28 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 244 seconds]
00:29 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
00:32 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
00:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
00:45 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds]
00:45 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
00:46 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 268 seconds]
00:55 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:10 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds]
01:12 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 258 seconds]
01:12 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
01:19 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:39 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
01:40 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
01:40 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds]
01:51 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:33 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 272 seconds]
03:48 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
03:48 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
03:48 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
03:50 -!- Kostenko [~Kostenko@195.12.50.233] has quit [Ping timeout: 245 seconds]
04:06 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning
04:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:14 < fiatjaf> is it true that when a route fails because of insufficient fees the erring node returns the channel_update message with its new fee policy in it?
06:14 < fiatjaf> can we get that from a waitsendpay call somehow?
06:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
06:42 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
06:42 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds]
06:51 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
08:02 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds]
08:04 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 246 seconds]
08:04 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
08:17 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
08:26 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning []
08:26 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning
08:45 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
08:59 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: No Ping reply in 180 seconds.]
09:02 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning
09:06 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
09:07 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 248 seconds]
09:14 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds]
09:15 -!- trueptolemy [2d0b004d@45.11.0.77] has joined #c-lightning
09:18 < trueptolemy> cdecker: Hi, I have a question: if we receive error message from remote peer, but now the funding only locks one side, should we broadcasting unilateral close or just forget the channel?
09:27 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
09:41 < trueptolemy> I think if funding locks on only one side or both side, we need broadcast unilateral close. But if funding doesn't lock on any side, we need just forget the channel.
10:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 244 seconds]
10:03 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
10:03 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 248 seconds]
10:07 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
10:08 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 246 seconds]
10:13 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
10:31 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds]
10:33 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
10:33 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 248 seconds]
10:41 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
11:07 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer]
11:07 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Read error: Connection reset by peer]
11:07 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Write error: Connection reset by peer]
11:08 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
11:08 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
11:13 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
11:18 -!- trueptolemy [2d0b004d@45.11.0.77] has quit [Ping timeout: 260 seconds]
11:32 -!- trueptolemy [2d582886@45.88.40.134] has joined #c-lightning
11:36 -!- trueptolemy [2d582886@45.88.40.134] has quit [Remote host closed the connection]
12:03 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
12:03 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 244 seconds]
12:04 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 272 seconds]
12:12 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
12:58 <@niftynei> trueptolemy: the funding failing to lock is because the node hasn't seen it on chain. if it is on chain but the node failed to see it, then you'd want to do a close. you would not want to forget the channel -- you'd lose the funds
12:58 <@niftynei> trueptolemy: the funding failing to lock is because the node hasn't seen it on chain. if it is on chain but the node failed to see it, then you'd want to do a close. you would not want to forget the channel -- you'd lose the funds
12:59 <@niftynei> :s/it/the funding tx/
13:00 <@niftynei> since one node has is 'locked' that's a good indication that it's definitely on-chain
13:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
13:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 260 seconds]
13:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
14:23 -!- Kostenko [~Kostenko@195.12.50.233] has quit [Ping timeout: 248 seconds]
14:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:38 -!- Kostenko [~Kostenko@dsl-155-30.bl26.telepac.pt] has joined #c-lightning
14:44 -!- Kostenko [~Kostenko@dsl-155-30.bl26.telepac.pt] has quit [Ping timeout: 268 seconds]
14:57 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning
15:21 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
15:21 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 268 seconds]
16:27 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds]
16:30 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
16:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:52 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning []
16:53 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning
17:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
18:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:05 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
22:09 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
23:23 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has quit [Remote host closed the connection]
23:36 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zegkwibbopnqyxhp] has joined #c-lightning
--- Log closed Tue Aug 27 00:00:53 2019