--- Log opened Fri Jun 12 00:00:47 2020
00:05 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
00:36 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Read error: Connection reset by peer]
01:41 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
01:42 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
01:50 -!- pretyflaco [~k3m@185.213.155.170] has joined #c-lightning
03:14 <@cdecker> It's worth noting that even with the DB they couldn't have moved the funds, since they lack the hsm_secret. But giving them the DB is a major privacy leak
03:16 <@cdecker> Maybe they were just trying to make sure that the bitcoin address for the refund was from the same person they got the LN invoice from, in which case giving the preimage sounds reasonable, and unless you promised something in exchange (signed invoice with description promising a service or good) you should be ok
03:16 <@cdecker> It's still suboptimal since preimages are bearer proves of payment, i.e., anyone with the preimage can claim to be the payer
04:38 -!- pretyflaco [~k3m@185.213.155.170] has quit [Ping timeout: 264 seconds]
04:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
04:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
04:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:52 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has joined #c-lightning
06:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
06:03 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:16 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has joined #c-lightning
06:23 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
06:25 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has joined #c-lightning
06:28 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
07:29 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
09:16 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
09:19 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
09:23 -!- pretyflaco [~k3m@185.213.155.165] has joined #c-lightning
09:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
09:25 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
09:26 -!- th0th [~th0th@gateway/tor-sasl/th0th] has joined #c-lightning
10:26 < jb55> my node just crashed with: bitcoind has gone backwards from 634391 to 634389 blocks
10:26 < jb55> interesting...
10:31 < harding> jb55: I think that's a deliberate feature, see https://github.com/ElementsProject/lightning//pull/3274 ; the question is why it thinks bicoind went backwards (unless it's just the case that your bitcoind crashed and you restarted it at that point).
10:32 < jb55> my bitcoind got oom killed so might be related...
10:32 < jb55> seems ok now
10:33 < harding> Yeah, that would make sense.  When bitcoind crashes or gets killed, it (obviously) doesn't have a chance to write the latest UTXO state updates to disk, so it rewinds to the last time the cache was written to disk and re-processes the blocks from there.
10:34 < jb55> makes sense
10:42 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 246 seconds]
10:54 <@cdecker> Hm, it could make sense to add a grace period so bitcoind can catch back up
10:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds]
11:11 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 264 seconds]
11:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
11:44 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
11:59 -!- pretyflaco [~k3m@185.213.155.165] has quit [Ping timeout: 246 seconds]
12:48 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Read error: Connection reset by peer]
12:50 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
13:02 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
13:02 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
13:35 -!- kabaum [~kabaum@2001:9b1:efd:9b00:55d3:b22b:b6e1:f9c2] has quit [Ping timeout: 256 seconds]
13:53 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
13:53 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
15:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 264 seconds]
15:53 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
15:55 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
16:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]
16:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
17:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
18:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
19:05 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:07 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has joined #c-lightning
19:35 -!- Letze [sid63391@gateway/web/irccloud.com/x-ztuharucyblzwesl] has quit [Ping timeout: 246 seconds]
20:03 -!- Letze [sid63391@gateway/web/irccloud.com/x-zeyaegvkulroehjt] has joined #c-lightning
20:08 -!- Letze [sid63391@gateway/web/irccloud.com/x-zeyaegvkulroehjt] has quit [Max SendQ exceeded]
20:09 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:16 -!- Letze [sid63391@gateway/web/irccloud.com/x-rryebhfrpnxvkyvb] has joined #c-lightning
20:50 -!- Letze [sid63391@gateway/web/irccloud.com/x-rryebhfrpnxvkyvb] has quit [Ping timeout: 256 seconds]
21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:21 -!- Letze [sid63391@gateway/web/irccloud.com/x-djelvihawnuvoaym] has joined #c-lightning
21:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
21:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
21:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:23 -!- vasild_ is now known as vasild
--- Log closed Sat Jun 13 00:00:48 2020