--- Log opened Fri Jul 10 00:00:14 2020
00:08 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has joined #c-lightning
00:17 -!- berndj [~berndj@ns2.linksynergy.co.za] has joined #c-lightning
00:27 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
00:40 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has joined #c-lightning
00:40 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has quit [Client Quit]
00:50 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
01:17 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 246 seconds]
01:18 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
01:20 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
01:20 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
01:33 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Quit: WeeChat 2.8]
01:34 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
01:46 -!- shupfel [~Bohphah3@92.117.252.15] has joined #c-lightning
01:48 < shupfel> What does "Already have funding locked in (and ready to announce)" (debug-log-message) exactly mean. It's a channel being in "CHANNELD_SHUTTING_DOWN" state for >24h.
01:48 < zmnscpxj__> you closed the channel just after opening it?
01:48 < zmnscpxj__> I suppose just a leftover debug message
01:49 < zmnscpxj__> hopefully
01:49 < shupfel> the channel was open for quite a long time, several weeks
01:49 < zmnscpxj__> huh
01:49 < zmnscpxj__> that is strange
01:50 < shupfel> oh, the message comes after  Peer has reconnected, state CHANNELD_SHUTTING_DOWN
01:50 < zmnscpxj__> ah
01:51 < shupfel> maybe 'reconnect' is the cause?
01:51 < zmnscpxj__> there may be HTLCs still
01:51 < shupfel> ok. so just waiting a good idea?
01:51 < zmnscpxj__> That is a perfectly normal and expected message on reconnect
01:51 < zmnscpxj__> *are* there HTLCs still?
01:52 < shupfel> how can i find out?
01:52 < zmnscpxj__> listpeers should show the channel with the peer, and should show an "htlcs" field containing any in-flight HTLCs
01:53 < zmnscpxj__> if there are any in-flight, we wait it out
01:53 < zmnscpxj__> if the HTLCs time out, we automatically unilaterally close
01:54 < zmnscpxj__> If "htlcs" is empty it should advance to `CLOSINGD_SIGEXCHANGE`/`CLOSINGD_COMPLETE`
01:58 < shupfel>  "htlcs": []      "status": ["CHANNELD_SHUTTING_DOWN:Sent reestablish, waiting for theirs"]
01:58 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has joined #c-lightning
01:58 < zmnscpxj__> hmmm, peer is not responding yet.........?
01:59 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has joined #c-lightning
01:59 < zmnscpxj__> "connected": true, right?
01:59 < zmnscpxj__> How long ago did you reconnect?
02:01 < shupfel> OMG, 'reconnect' messages every 5 mins
02:01 < zmnscpxj__> huh. problems on the remote
02:01 < shupfel> not the first time with this peers
02:01 < zmnscpxj__> possibly the remote is under DoS
02:01 < shupfel> its bitfinex' lightning node
02:02 < shupfel> already had contact with support recently as i wasn't able to connect at all
02:02 < shupfel> :-(
02:02 < zmnscpxj__> hmmm
02:02 < zmnscpxj__> no other decent routes to them?
02:03 < shupfel> i'll simply try re-opening the support ticket
02:03 < zmnscpxj__> yes, the message is a normal message we print when we reconnect with the peer
02:03 < shupfel> besides that, thank you for your educating support here. really appriciate it! :-)
02:03 < zmnscpxj__> np
02:03 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has quit [Ping timeout: 272 seconds]
02:04 < shupfel> doing this in my spare time - besides my normal IT job - and don't have so much time for this veryvery interessting topic
02:06 < zmnscpxj__> as to your previous address-reuse problem --- I wrote a short test, but your situation "should" not happen, so no idea what happened there
02:06 < zmnscpxj__> according to my test, anyway
02:10 < shupfel> hmm - why is the address not listed in 'dev-listaddrs'? Do i have no control over this address?
02:11 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Quit: WeeChat 2.8]
02:11 < zmnscpxj__> I have no idea how that happened
02:11 < zmnscpxj__> you use c-lightning raw? no zap or anything on top?
02:11 < shupfel> no, raw, on command line with lightning-cli
02:12 < zmnscpxj__> no idea. it is a p2wpkh addr too IIRC?
02:13 < zmnscpxj__> could you try `newaddr` a few times and see if the address comes up?
02:13 < shupfel> yes, it's a 'segwit' address
02:13 < shupfel> bc1q...
02:14 < shupfel> is't this the same as 'dev-listaddrs 500' ?
02:14 < zmnscpxj__> if it was a p2wsh it could have been a to-local
02:14 < zmnscpxj__> yes
02:14 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
02:14 < zmnscpxj__> how long was the addr again? how many chars?
02:15 < shupfel> is c-lightning using multiple deviation paths / wallet accounts?
02:15 < zmnscpxj__> it is using just one for both change and normal receive
02:15 < zmnscpxj__> cdecker knows more of the details though
02:15 < shupfel> . o O (maybe the address is on a different account)
02:16 < zmnscpxj__> yes but why is *that* node tracking it in listfunds?? that is what is strange.....'
02:18 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
02:19 < shupfel> at the moment I try to get contol over this address & funds. already extracted an xprv from hsm-secret, now looking for a wallet that supports importing the xpub or xprv while specifying a custom deriv. path
02:19 < shupfel> (electrum doesn'nt)
02:33 < shupfel> yes, strange, am busy drawing a utxo-tree on paper.... :-] ...
02:34 < shupfel> to find out what action led to this address / utxo
02:38 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
02:44 -!- nixbitcoin [~nixbitcoi@gateway/tor-sasl/nixbitcoin] has joined #c-lightning
02:44 -!- nixbitcoin_ [~nixbitcoi@gateway/tor-sasl/nixbitcoin] has quit [Remote host closed the connection]
03:31 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 265 seconds]
03:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
03:48 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 272 seconds]
03:52 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
03:56 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
04:23 -!- Netsplit *.net <-> *.split quits: alko89, belcher_
04:24 -!- Netsplit *.net <-> *.split quits: sword_smith, t0mix, wraithm
04:27 -!- Netsplit over, joins: belcher_, wraithm, alko89, sword_smith, t0mix
04:39 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 256 seconds]
04:41 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
05:37 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
05:38 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
05:53 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 264 seconds]
05:53 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
06:05 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
06:06 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
06:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:25 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
06:27 -!- bitauger [sid371414@gateway/web/irccloud.com/x-jfcznyaikwkoydlt] has quit [Ping timeout: 256 seconds]
06:28 -!- bitauger [sid371414@gateway/web/irccloud.com/x-vyqzzggolnrkakdq] has joined #c-lightning
06:30 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
07:04 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
07:13 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has quit [Ping timeout: 240 seconds]
07:13 -!- kristapsk_ is now known as kristapsk
07:17 -!- rafalcpp [~racalcppp@185.3.112.131] has joined #c-lightning
07:25 -!- rafalcpp [~racalcppp@185.3.112.131] has quit [Ping timeout: 256 seconds]
07:25 -!- rafalcpp_ [~racalcppp@ip-178-214.ists.pl] has joined #c-lightning
07:28 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
08:30 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
08:34 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
08:34 -!- vasild_ is now known as vasild
08:38 < liberliver> Hey, does anybody know what's happening when I see the error `lightningd: HSM did not give init reply`?
08:43 < shupfel> is there a process 
08:43 < shupfel> -rw-r--r--   1 markus  markus        109 Apr 14 22:59 btc-danya.txt
08:43 < shupfel> is there a process named "lightning_hsmd" running?
08:45 < liberliver> Not sure. Lightningd is a systemd service in that case and I probably have not so much time to track it
08:46 < liberliver> oh. maybe it's something related to acces rights
09:12 < darosior> shupfel: this should not happen, how did you install and start lightningd ? Going afk but with this information others will be able to help.
09:30 < shupfel> darosior: are you refering to liberliver's HSM prob or to my currently inaccessible UTXO problem?
09:30 < liberliver> that was due to access right.
09:31 < liberliver> I moved old client to new VPS
09:36 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
10:23 <@cdecker> fwiw `systemctl status lightningd` will show you a process tree that should include a `lightning_hsmd` if you manage the service with `systemd`
10:38 < darosior> shupfel: sorry, read in a hurry was off subject ^^"
10:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer]
11:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:14 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
11:18 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
11:30 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
11:30 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
11:55 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:56 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
11:59 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 272 seconds]
12:46 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
13:14 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
13:16 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
13:19 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Quit: Leaving]
13:27 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 260 seconds]
13:28 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
14:04 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 246 seconds]
14:06 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
14:26 -!- rafalcpp_ [~racalcppp@ip-178-214.ists.pl] has quit [Ping timeout: 264 seconds]
14:58 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
14:58 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
15:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 264 seconds]
15:09 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:15 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds]
16:07 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
16:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
16:20 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
16:34 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:47 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
17:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds]
17:27 -!- shupfel [~Bohphah3@92.117.252.15] has quit [Ping timeout: 246 seconds]
17:53 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
17:58 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
18:22 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
20:31 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
20:34 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
20:34 -!- vasild_ is now known as vasild
20:55 -!- masterdonx2 [~masterdon@194.150.167.55] has joined #c-lightning
20:56 -!- MasterdonX [~masterdon@192.154.254.136] has quit [Ping timeout: 258 seconds]
21:29 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
21:30 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
22:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
23:16 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 260 seconds]
23:16 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
23:21 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 258 seconds]
23:21 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
23:30 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 256 seconds]
23:32 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
23:44 -!- Amperture [~amp@65.79.129.113] has quit [Quit: Leaving]
23:54 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 272 seconds]
23:55 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
--- Log closed Sat Jul 11 00:00:15 2020